62
Quote:
Where did you search? Skalpa, phppp, pemen, rowd are working on the core -when they have the time.
Quote:
Most team members banned, right. You might be confused by the active poster and member whose alias is 'banned', but isn't really banned from posting at all...
And like vaughan said, if people are banned, they deserved it.
Quote:
You mean you are withholding information about known security risks from the community? Is that transparency and an open community and development oriented attitude? If you have information about security vulnerabilities, let the core developers know. You can e-mail them, PM them, or even send an e-mail to security@xoops.org.
If you don't there is no proof that the XOOPS core is insecure.
And I haven't even touched the subject of secure vs. stable. You're mixing up things just for the fun of it.
Quote:
True. Many eyeballs make all bugs shallow, as Eric Raymond's famous quote goes. But has it occurred to you at all that there aren't many bug reports because the XOOPS core is stable and secure? Often the simple answers are the best.
Quote:
Where on earth did you get those two ideas?
1. If they don't get paid, it means that other things (like working for a living) take priority over the XOOPS development. Demanding 'the XOOPS project team' do more work will not change those priorities.
2. Please browse to the website www.gnu.org. I bet you know this one already, but here's the central idea to their philosophy:
What is Free Software?
Quote:
If professionals work on an open source project, shouldn't they get paid? What about businesses who provide value added services based on open source products? Are they wrong? No, they're not. There's no reason whatsoever that open source cannot be paid jobs.
That doesn't mean the community should pay those members of the community who provide free-of-charge services. But paying professionals for a job isn't ruled out at all!
Quote:
Sick? I see no sickness other then false and silly notions. I didn't ask you to find new core developers, so don't be sorry that you're not the solution to a self-invented problem.
If you want to help, do so. If not, then don't. It's about that freedom. You can choose all by yourself
If you want and are up to it, you can show the XOOPS community what you're worth with Javascript. This is not a challenge, but the way open source development works. Show your pers what you're worth, and get credited accordingly.
So far, we haven't seen much that's worth a lot...
Herko
xguide wrote:
I did not found developers working on a new core or documentation.
Where did you search? Skalpa, phppp, pemen, rowd are working on the core -when they have the time.
Quote:
But i check permissions and i see most team members banned.
Most team members banned, right. You might be confused by the active poster and member whose alias is 'banned', but isn't really banned from posting at all...
And like vaughan said, if people are banned, they deserved it.
Quote:
You say it is stable but the true it is not secure.
You mean you are withholding information about known security risks from the community? Is that transparency and an open community and development oriented attitude? If you have information about security vulnerabilities, let the core developers know. You can e-mail them, PM them, or even send an e-mail to security@xoops.org.
If you don't there is no proof that the XOOPS core is insecure.
And I haven't even touched the subject of secure vs. stable. You're mixing up things just for the fun of it.
Quote:
And because there is not new code, developers and users can not contribute, work on improvements, test or report bugs.
True. Many eyeballs make all bugs shallow, as Eric Raymond's famous quote goes. But has it occurred to you at all that there aren't many bug reports because the XOOPS core is stable and secure? Often the simple answers are the best.
Quote:
Sorry, i did not know the project team expects to be paid or other incentives. Usual open source it is not a paid-job?
Where on earth did you get those two ideas?
1. If they don't get paid, it means that other things (like working for a living) take priority over the XOOPS development. Demanding 'the XOOPS project team' do more work will not change those priorities.
2. Please browse to the website www.gnu.org. I bet you know this one already, but here's the central idea to their philosophy:
What is Free Software?
Quote:
www.gnu.org:
“Free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech”, not as in “free beer”.
If professionals work on an open source project, shouldn't they get paid? What about businesses who provide value added services based on open source products? Are they wrong? No, they're not. There's no reason whatsoever that open source cannot be paid jobs.
That doesn't mean the community should pay those members of the community who provide free-of-charge services. But paying professionals for a job isn't ruled out at all!
Quote:
The project is sick, i can understand you do not have a developer to code a new core. I can only help users on java scripts for free. But i can not help you to find core developers. Maybe you can pay with adds revenues? I have no solution to your problem. Sorry.
Sick? I see no sickness other then false and silly notions. I didn't ask you to find new core developers, so don't be sorry that you're not the solution to a self-invented problem.
If you want to help, do so. If not, then don't. It's about that freedom. You can choose all by yourself
If you want and are up to it, you can show the XOOPS community what you're worth with Javascript. This is not a challenge, but the way open source development works. Show your pers what you're worth, and get credited accordingly.So far, we haven't seen much that's worth a lot...
Herko
63
Quote:lets see if it is the right answer first. If not, he can always use your solution
Herko
BlueStocking wrote:
by Herko on 2007/3/25 12:19:03
Herko,
THANKS....
BS
Herko
64
Quote:
Better yet, why don't you just upload the smartobject files back to the server, and you'll see everything should work again. This because you only removed the files when deinstalling (I am assuming), and not the database tables.
In het nederlands:
Nog beter: waarom upload je niet de smartobject bestanden weer op de server, en alles zou weer moeten werken. Dit omdat je waarschijnlijk alleen de bestanden hebt verwijderd tijden het deinstalleren, en niet de database tabellen (ik neem aan dat je niet via systeem admin -> modules de module eerst gededactiveerd hebt, en daarna hebt verwijderd uit de database en pas dan de bestanden van de server hebt verwijderd).
Herko
straaten wrote:
I've installed smartobjects 0,9 on XOOPS 2.0.16. But it dit not do what i wanted it to do, so i deinstalled it, now i need it for smartprofile for php4, i wanted to reinstall it but i get this error Table 'xxxx_smartobject_meta' already exists
How do i get this quirry out of my databate.
Jan.
Exuse me for the poor english but i am from holland
Better yet, why don't you just upload the smartobject files back to the server, and you'll see everything should work again. This because you only removed the files when deinstalling (I am assuming), and not the database tables.
In het nederlands:
Nog beter: waarom upload je niet de smartobject bestanden weer op de server, en alles zou weer moeten werken. Dit omdat je waarschijnlijk alleen de bestanden hebt verwijderd tijden het deinstalleren, en niet de database tabellen (ik neem aan dat je niet via systeem admin -> modules de module eerst gededactiveerd hebt, en daarna hebt verwijderd uit de database en pas dan de bestanden van de server hebt verwijderd).
Herko
66
Quote:
1. Nobody is saying it is the community's fault. My post was stating the motivation for those members of the community that develop, and the consequence of the treatment they get from some of the community.
2. You quickly switch from community to users who are not the developers. Then who creates XOOPS? Who writes the new codes, who tests new codes, who writes developer documentation, who creates the new architecture, who creates the roadmaps, who writes the classes, who backports the code to earlier versions? All in their free time, in their own time, without pay or -as stated in my earlier post- other incentives?
The developers *are* part of the community. And the community steps up and provides high quality developers.
Xguide, you seem to have a decent knowledge of javascript, why not *show* the core development group what *you* want to do with that knowledge for the XOOPS 2.3 core? Discuss your ideas on the sf.net core development forums, submit code examples, and if they are good, I'm sure your work will be recognised as such and be treated accordingly.
Herko
xguide wrote:
Each time a XOOPS user, or developer ask about XOOPS development, the managers team say it is community fault. But the users are not developers.
1. Nobody is saying it is the community's fault. My post was stating the motivation for those members of the community that develop, and the consequence of the treatment they get from some of the community.
2. You quickly switch from community to users who are not the developers. Then who creates XOOPS? Who writes the new codes, who tests new codes, who writes developer documentation, who creates the new architecture, who creates the roadmaps, who writes the classes, who backports the code to earlier versions? All in their free time, in their own time, without pay or -as stated in my earlier post- other incentives?
The developers *are* part of the community. And the community steps up and provides high quality developers.
Xguide, you seem to have a decent knowledge of javascript, why not *show* the core development group what *you* want to do with that knowledge for the XOOPS 2.3 core? Discuss your ideas on the sf.net core development forums, submit code examples, and if they are good, I'm sure your work will be recognised as such and be treated accordingly.
Herko
67
Quote:
bluestocking: that is the GPL lisence under which the code is released.
Themes fall into a different kind of category, mainly because of the images that are used. Images are copyrighted as creative work from the designer, and its use can be kimited. HTML code can't be copyrighted, as it is a standardised interpreted language, and therefore not your creative work... This is stll grey area tho...
to answer FeraTechInc's questions:
1. You always credit the people that have helped you make what you have. Credit is all they get, and it is east to give. If they don't look like the original, are they totally new? Not if you used someone elses work as a basis.
2. you can touch the credits and remove them from the theme, as long as you credit them in the files you release. In other words: you don't have to put the name and credits of the original creator in the footer of every page. A credits.txt file in a theme package releasing your own version of the theme is enough. However, courtesy likes to see the name and kink of the original creator in the theme comments for example, so it is only visible when viewing the page source.
herko
FeraTechInc wrote:
Ok, so I like to take themes and modify them instead of starting from scratch. Now I have the following questions:
1. At what point does a redesigned theme become mine? Do I always have to credit the person I took the idea from? Many times customized themes look nowhere near the original design but is it still necessary to credit the original author?
2. Formatting credit on themes. In many themes original authors like to use several lines one for their credit. Is it OK to merge this onto one line? Or is it completely forbidden to touch the credit by the original author?
bluestocking: that is the GPL lisence under which the code is released.
Themes fall into a different kind of category, mainly because of the images that are used. Images are copyrighted as creative work from the designer, and its use can be kimited. HTML code can't be copyrighted, as it is a standardised interpreted language, and therefore not your creative work... This is stll grey area tho...
to answer FeraTechInc's questions:
1. You always credit the people that have helped you make what you have. Credit is all they get, and it is east to give. If they don't look like the original, are they totally new? Not if you used someone elses work as a basis.
2. you can touch the credits and remove them from the theme, as long as you credit them in the files you release. In other words: you don't have to put the name and credits of the original creator in the footer of every page. A credits.txt file in a theme package releasing your own version of the theme is enough. However, courtesy likes to see the name and kink of the original creator in the theme comments for example, so it is only visible when viewing the page source.
herko
68
Quote:
Ehm, I assume you mean that you want anon users to see as little as possible.
The best way to do this is to close your site (system admin -> general preferences -> settings), and edit the siteclosed.html template to show what you want to tell your anonymous visitors. That way only registered users can see any content.
Herko
Tyson0317 wrote:
I do not want annonoumous users to see as little as possible.
Ehm, I assume you mean that you want anon users to see as little as possible.
The best way to do this is to close your site (system admin -> general preferences -> settings), and edit the siteclosed.html template to show what you want to tell your anonymous visitors. That way only registered users can see any content.
Herko
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|