Wanted: PHP public domain projects

**Maxim Vexler** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:[color=blue]
> Are there many PHP public domain projects out there?
>
> I'm particularly interested in CMS project materials.
>
> So far - outside of my own projects - I've found /very/ little PD
> PHP material out there.
>
> A large proportion of the PHP community seems to have embraced the Gnu
> licenses - complete with all their restrictions on the users of the
> software.
>
> I don't want to copyright my code - or impose restrictions on its users.
>
> So far about the only PD PHP project I have found is:
>
> http://sourceforge.net/projects/promanager/
>
> This is well out of date, relies on REGISTER_GLOBAL S - and (despite
> its /claimed/ license conditions) contains multiple sections of code
> emblazoned with copyright statements with unspecified license conditions -
> a combination which renders it practically useless to me :-(
>
> There must be some other public domain PHP material out there.
>
> Are there /any/ useful PHP libraries in the public domain? What
> sources are there which can be used as genuinely free sources of code?
>
> Thanks in advance for any assistance.[/color]
Just to clarify thing the GNU GPL license is to free your code, not to
limit it, GPL allows anyone to change or use your code, the only thing
it will not allow you to do is to locked it, i.e. close source it
you really should read : http://www.gnu.org/licenses/gpl-faq.html

a side note : if you release your code into the public domain i can take
your code & use it in my closed source program, the GNU GPL comes to
ensure that i will not ever do such a thing, its a "copyleft license"
that comes to give you freedom rather then take it from you.

**Tim Tyler** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

"Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>" <"Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>"> wrote or quoted:[color=blue]
> Tim Tyler wrote:[/color]
[color=blue][color=green]
> > Are there many PHP public domain projects out there?
> >
> > I'm particularly interested in CMS project materials.
> >
> > So far - outside of my own projects - I've found /very/ little PD
> > PHP material out there.
> >
> > A large proportion of the PHP community seems to have embraced the Gnu
> > licenses - complete with all their restrictions on the users of the
> > software.
> >
> > I don't want to copyright my code - or impose restrictions on its users.
> >
> > So far about the only PD PHP project I have found is:
> >
> > http://sourceforge.net/projects/promanager/
> >
> > This is well out of date, relies on REGISTER_GLOBAL S - and (despite
> > its /claimed/ license conditions) contains multiple sections of code
> > emblazoned with copyright statements with unspecified license conditions -
> > a combination which renders it practically useless to me :-(
> >
> > There must be some other public domain PHP material out there.
> >
> > Are there /any/ useful PHP libraries in the public domain? What
> > sources are there which can be used as genuinely free sources of code?
> >
> > Thanks in advance for any assistance.[/color]
>
> Just to clarify thing the GNU GPL license is to free your code, not to
> limit it [...][/color]

To clarify further: it copyrights the code - and then fails to grant full
rights to use it in an unrestricted fashion.
[color=blue]
> GPL allows anyone to change or use your code, the only thing
> it will not allow you to do is to locked it, i.e. close source it [...][/color]

A highly restrictive conditon that places limitations on using GPL code
in a commercial environment.

In particular it becomes practically impossible to deploy the code within
a company which wants to customise the code to include their own secret
business logic - and then deploy that code in a binary format to their
customers.

I *don't* want to erect barriers for others to wishing to interface with
my code.

I want to make the process as simple and painless as possible.
[color=blue]
> you really should read : http://www.gnu.org/licenses/gpl-faq.html[/color]

You really should stop patronising me.
[color=blue]
> a side note : if you release your code into the public domain i can take
> your code & use it in my closed source program [...][/color]

That's fine by me ;-)
[color=blue]
> [...] the GNU GPL comes to ensure that i will not ever do such a thing,[/color]

....so it restricts your users in how they can use your code.
[color=blue]
> its a "copyleft license" that comes to give you freedom rather then
> take it from you.[/color]

It copyrights the code - and then fails to grant full rights to use it
in an unrestricted fashion. That's not what I would describe as freedom.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

**Sebastian Lauwers** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:
[color=blue]
> It copyrights the code - and then fails to grant full rights to use it
> in an unrestricted fashion. That's not what I would describe as freedom.[/color]

Ok well, just make a website, and put all of your code there, anyone
will be free to download it.

Of course it's quite sympathic for your users, but still, are you happy
that most of those who'll leech the code will ever thank you for the
money they'll make with the code you made?

I think that's why so many people use GPL, well, my point of view.

NRN,
S.

--
The most likely way for the world to be destroyed,
most experts agree, is by accident.
That's where we come in; we're computer professionals.
We cause accidents.
--Nathaniel Borenstein

**Tim Tyler** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

Sebastian Lauwers <dacrashanddie@ nospam.9online. fr> wrote or quoted:[color=blue]
> Tim Tyler wrote:[/color]
[color=blue][color=green]
> > It copyrights the code - and then fails to grant full rights to use it
> > in an unrestricted fashion. That's not what I would describe as freedom.[/color]
>
> Ok well, just make a website, and put all of your code there, anyone
> will be free to download it.
>
> Of course it's quite sympathic for your users, but still, are you happy
> that most of those who'll leech the code will ever thank you for the
> money they'll make with the code you made?
>
> I think that's why so many people use GPL, well, my point of view.[/color]

It doesn't seem logical.

If you put your code in the public domain, you won't make much money from
your users - unless you can offer technical support or consulting services.

If you GPL your code, you won't make much money from your users either -
unless you can offer technical support or consulting services.

Not much difference there.

I suspect the appeal of the GPL is that it gives the authors full
ownership and control over their own code under copyright law.

For instance, the GPL /does/ allow is distributing the copyrighted code
under other kinds of restrictive licenses.

That's what the MySQL folk do. They distribute their code as GPL code
"Our software is 100% GPL" - (so that it's practically unusable in a
commercial environment) - and then charge for commercial licenses under
different terms (which also have their restrictions - but happen to allow
redistribution of modified versions without revealing the source code -
something businesses care about, but the GPL forbids.

They can do this because they retain copyright and ownership of their
code - and are not themselves obliged to follow the terms of the GPL -
as most of their users are.

Commercial users can't make much use of the GPL version because of the
restrictions in the license - and the original authors have full rights
over the code - so they can make money by flogging businesses a commercial
version - and none of their users can compete with them in this area -
since their license conditions forbid it.

These days people GPL code just for the sake of inter-operating
with all the other GPL code out there. If your code is not
under the GPL, you can't link with many other people's code -
because the license conditions forbid it.

Whatever the appeal, I don't think it has much to do with freedom.

GPL code is *copyrighted* - and the license restricts numerous
rights to the original authors of the code, which puts them in
a privilidged position to sell their software to businesses
under different licenses.

Authors who want their code to be free tend not impose conditions
and restrictions on their users by copyrighting the code and
retaining full control over it.

One of the irritating things about the GPL is that it *pretends*
to be free.

"When we speak of free software, we are referring to freedom, not price"

GPL software does *not* give users freedom. It *copyrights* the
software and then *restricts* the activities users can perform.

"By contrast, the GNU General Public License is intended to guarantee
your freedom to share and change free software - to make sure the
software is free for all its users."

It fails miserably. The users are not free - as illustrated by the
case of MySQL - where the GPL'd software is sold under a less restrictive
license to businesses who find the restrictions of the GPL too onerous.
So much for free software.

If you want software to be free, the course of action is obvious -
put the software into the public domain so that everyone can use it.

Don't *copyright* the software and then *prohibit* other people from
doing what they like with your code with a *restrictive* license.

The GPL "freedom" hypocrisy is why I refer to such software as
"Fake Free Software". Fortunately, fake free software is easy
to spot - just look for the "copyright" symbol.

Anyway - enough of my "freedom" rant ;-)

Has anyone apart from me got any *genuinely* free PHP software - that
isn't yet "infected" with a Gnu license - or some other bunch of
copyright conditions and restrictions?

I would be particularly interested in CMS components or libraries.

Thanks in advance for any assistance.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

**Maxim Vexler** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:[color=blue]
> "Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>" <"Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>"> wrote or quoted:
>[color=green]
>>Tim Tyler wrote:[/color]
>
>[color=green][color=darkred]
>>>Are there many PHP public domain projects out there?
>>>
>>>I'm particularly interested in CMS project materials.
>>>
>>>So far - outside of my own projects - I've found /very/ little PD
>>>PHP material out there.
>>>
>>>A large proportion of the PHP community seems to have embraced the Gnu
>>>licenses - complete with all their restrictions on the users of the
>>>software.
>>>
>>>I don't want to copyright my code - or impose restrictions on its users.
>>>
>>>So far about the only PD PHP project I have found is:
>>>
>>> http://sourceforge.net/projects/promanager/
>>>
>>>This is well out of date, relies on REGISTER_GLOBAL S - and (despite
>>>its /claimed/ license conditions) contains multiple sections of code
>>>emblazoned with copyright statements with unspecified license conditions -
>>>a combination which renders it practically useless to me :-(
>>>
>>>There must be some other public domain PHP material out there.
>>>
>>>Are there /any/ useful PHP libraries in the public domain? What
>>>sources are there which can be used as genuinely free sources of code?
>>>
>>>Thanks in advance for any assistance.[/color]
>>
>>Just to clarify thing the GNU GPL license is to free your code, not to
>>limit it [...][/color]
>
>
> To clarify further: it copyrights the code - and then fails to grant full
> rights to use it in an unrestricted fashion.
>
>[color=green]
>>GPL allows anyone to change or use your code, the only thing
>>it will not allow you to do is to locked it, i.e. close source it [...][/color]
>
>
> A highly restrictive conditon that places limitations on using GPL code
> in a commercial environment.
>
> In particular it becomes practically impossible to deploy the code within
> a company which wants to customise the code to include their own secret
> business logic - and then deploy that code in a binary format to their
> customers.
>
> I *don't* want to erect barriers for others to wishing to interface with
> my code.
>
> I want to make the process as simple and painless as possible.
>
>[color=green]
>>you really should read : http://www.gnu.org/licenses/gpl-faq.html[/color]
>
>
> You really should stop patronising me.
>
>[color=green]
>>a side note : if you release your code into the public domain i can take
>>your code & use it in my closed source program [...][/color]
>
>
> That's fine by me ;-)
>
>[color=green]
>>[...] the GNU GPL comes to ensure that i will not ever do such a thing,[/color]
>
>
> ...so it restricts your users in how they can use your code.
>
>[color=green]
>>its a "copyleft license" that comes to give you freedom rather then
>>take it from you.[/color]
>
>
> It copyrights the code - and then fails to grant full rights to use it
> in an unrestricted fashion. That's not what I would describe as freedom.[/color]

I'm sorry if you felt like i was patronizing you, i wasn't.

When i release my code for everyone to use, it will be ONLY GPL for the
simple reason that it gives me the power to ensure that everyone who
uses my code will contribute back to the public by including my code in
their software & releasing it GPL'ed too. That way all can profit and
not just the one that "exploited" my code to build his commercial software.

You can claim it isn't true but every programmer seeks recognition. By
releasing my code GPLed I let people know that I wrote that code! if you
give your code in public domain fashion i for example am not even
obligated by law to mention that you are the author of the code, hack i
can even say i wrote that myself, now do you think that's fair ?

in fact the only reason the gpl was invented is to not allow people to
use it in closed source projects, not to limit you in any way, thats why
i wrote you "you really should read :
http://www.gnu.org/licenses/gpl-faq.html" it explained a lot to me & i
thought you could benefit from reading it also, if you are familiar with
the GPL and do not agree with it then :
a. i am sorry you feel this way.
b. it's your freedom! you can do with your code what ever you see fit. i
just try to show why i feel GPL is the right decision for you.

cheers, maxim.

**Gordon Burditt** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

>When i release my code for everyone to use, it will be ONLY GPL for the[color=blue]
>simple reason that it gives me the power to ensure that everyone who
>uses my code will contribute back to the public by including my code in
>their software & releasing it GPL'ed too.[/color]

No, the GPL does *NOT* do that. The GPL gives me the freedom to
not release my modified version *AT ALL*. And since 99% of everything
is crap, it's probably a good thing that my one-off scripts that
don't last more than a day and solve a problem nobody else is likely
to have don't get released. Nobody would want them anyway.
[color=blue]
>in fact the only reason the gpl was invented is to not allow people to
>use it in closed source projects, not to limit you in any way, thats why
>i wrote you "you really should read :
>http://www.gnu.org/licenses/gpl-faq.html" it explained a lot to me & i
>thought you could benefit from reading it also, if you are familiar with
>the GPL and do not agree with it then :[/color]

Clause 3 of the GPL is problematical. It raises the bar for releasing
modified code pretty high. In particular: Clause (3a) does not let
me prohibit separating the source and the binary, and then blaming
ME for doing so. I don't have the finances to withstand a legal
challenge on that point, even if the allegations turn out to be
false or even provably malicious on the part of the person making
the allegations.

Clause (3b) requires me to have some way to distribute the source
code for 3 years, and I don't necessarily have the life span left
(and neither does your average teenager), nor is there any corporation
guaranteed to be around in 3 years that I could prepay for 3 years
for a distribution site. So there's no practical way to be sure
of satisfying it. Oh, yes, when does that three years start? It
restarts every time I distribute binaries, right? Presumably if I
use clause (3b), I have to stop distributing modified code three
years BEFORE my bulletproof distribution site's funding runs out.

Clause (3c) likely doesn't apply because binaries are darned hard
to make changes in, so distributing modified versions when I got
the distribution as binary isn't likely to come up.

So, I take an alternate approach. If I make bug fixes, I attempt
to contribute them, in patch form only, or as a description of the
change I made, back to the original authors. Sometimes they won't
take them. Sometimes they will. Sometimes they come up with a
better but completely different way to address the problem.

Gordon L. Burditt

**Sebastian Lauwers** · Jul 17 '05, 07:55 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:
[color=blue]
> It doesn't seem logical.
>
> If you put your code in the public domain, you won't make much money from
> your users - unless you can offer technical support or consulting services.
>
> If you GPL your code, you won't make much money from your users either -
> unless you can offer technical support or consulting services.
>
> Not much difference there.[/color]

I wasn't talking about making money from my users, i was talking about
the fact that users could use my software that freely they COULD make
money from it, w/o even thanking me, worse, telling me they did.

And btw, yes, you can have a fee payed for downloading the source or
binary of your GPL software, but that only means they pay for the
download, not using or getting your software.

[...]
[color=blue]
> If you want software to be free, the course of action is obvious -
> put the software into the public domain so that everyone can use it.[/color]

This is where our opinion differs.

[...]
[color=blue]
> The GPL "freedom" hypocrisy is why I refer to such software as
> "Fake Free Software". Fortunately, fake free software is easy
> to spot - just look for the "copyright" symbol.[/color]

It's not 'cause you can't see fit of the GPL for your needs that it
turns into horsecrap does it? A lot of people use GPL, and a lot of
people understand it, and still use it. It might change, but
unfortunately, for you, it won't be soon.
[color=blue]
> Anyway - enough of my "freedom" rant ;-)[/color]

Agreed
[color=blue]
> Has anyone apart from me got any *genuinely* free PHP software - that
> isn't yet "infected" with a Gnu license - or some other bunch of
> copyright conditions and restrictions?[/color]

I'm working on an MMORPG game project. We haven't decided yet if we were
going to copyright it or not.
[color=blue]
> I would be particularly interested in CMS components or libraries.[/color]

Sorry, can't help for that at the moment.
[color=blue]
> Thanks in advance for any assistance.[/color]

Sorry i can't be of any help. But on thing is sure, you know how to make
long speeches. Even though i don't agree on most of your standings, i
must say i'm highly impressed by the quality of your argumentation. It
has been great to read you.

Best regards,
Sebastian

--
The most likely way for the world to be destroyed,
most experts agree, is by accident.
That's where we come in; we're computer professionals.
We cause accidents.
--Nathaniel Borenstein

**Tim Tyler** · Jul 17 '05, 07:56 AM

Re: Wanted: PHP public domain projects

"Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>" <"Maxim Vexler <hq4ever (at) 012 (dot) net (dot) il>"> wrote or quoted:
[color=blue]
> You can claim it isn't true but every programmer seeks recognition. By
> releasing my code GPLed I let people know that I wrote that code! if you
> give your code in public domain fashion i for example am not even
> obligated by law to mention that you are the author of the code, hack i
> can even say i wrote that myself, now do you think that's fair ?[/color]

I don't doubt what you say.

I expect one of the reasons programmers copyright their code is to force
all their users to keep their name emblasoned on all the copies for ever
more. It also means that they retain all rights and ownership over it.

That's may be good for the programmers' egos, but it offers no benefit
for the users - rather the failure to give up rights imposed by copyright
law creates many opportunities for incompatible license terms - and thus
hinders collaborative development.

Look at the way you can't use GPL code in LGPL programs. These
licenses are written by the same guy - yet they fail to inter-operate -
because of restrictions inherited from copyright law.

Massaging the programmers egos is all very well - but it doesn't
result in free software. Indeed just the opposite - legally
*forcing* users to print license conditions pointing to copyright
notices whenever they run the program takes a freedom away from
users.
[color=blue]
> in fact the only reason the gpl was invented is to not allow people to
> use it in closed source projects, not to limit you in any way [...],[/color]

People are limited by default because of copyright law. Licenses
give rights - rather than take them away.

The GPL simply fails to grant all the freedoms that were taken away by
invoking copyright law. For example, it fails to give the right to
make binary-only distributions of modified copies.

Copyright law imposes the limitations on users of the code. The GPL
merely fails to grant them back again.
[color=blue]
> i wrote you "you really should read :
> http://www.gnu.org/licenses/gpl-faq.html" it explained a lot to me & i
> thought you could benefit from reading it also [...][/color]

You apparently assumed that I was criticising the GPL without being
familiar with its FAQ. I don't think that that is the case.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

**Tim Tyler** · Jul 17 '05, 07:56 AM

Re: Wanted: PHP public domain projects

Sebastian Lauwers <dacrashanddie@ nospam.9online. fr> wrote or quoted:[color=blue]
> Tim Tyler wrote:
>[color=green]
> > If you GPL your code, you won't make much money from your users either -
> > unless you can offer technical support or consulting services.
> >
> > Not much difference there.[/color]
>
> I wasn't talking about making money from my users, i was talking about
> the fact that users could use my software that freely they COULD make
> money from it, w/o even thanking me, worse, telling me they did.[/color]

By contrast, I *love* the fact that any users of my public domain
software feel free to do whatever they like with it. They don't
ever have to concern themselves with getting sued through violating
the license conditions - since there are none. If they want to try to
make money with my software, then that's *great* - more power to them.

The only reason I can see why should I be *jealous* of them making money
from software I wrote, is if I would rather sell it myself - as I
would be able to do if I had retained copyright over it.

That's fine - but reataining ownership and the privilidged right to
flog modified versions of the software under different license
conditions doesn't seem to have much to do with *free* software.
[color=blue][color=green]
> > The GPL "freedom" hypocrisy is why I refer to such software as
> > "Fake Free Software". Fortunately, fake free software is easy
> > to spot - just look for the "copyright" symbol.[/color]
>
> It's not 'cause you can't see fit of the GPL for your needs that it
> turns into horsecrap does it? A lot of people use GPL, and a lot of
> people understand it, and still use it. It might change, but
> unfortunately, for you, it won't be soon.[/color]

I concur that the GPL's popularity probably won't change soon.

Users have been hoodwinked into thinking that they are getting "Free
sofware" when in fact they are getting "Fake Free Software" - which comes
with copyright statements and license conditions *just* like every other
sort of not-free software.

It will most likely take some time before programmers and users wake
up to the damage these copyright restrictions are still causing
collaborative development - and learn to prefer *genuine* free software
over *fake* free software, by valuing the additional freedoms such
software provides them with.

The Gnu folk should not be allowed to get away with redefining
the term "free" to mean "still burdened with copyright restrictions".
[color=blue]
> Sorry i can't be of any help. But on thing is sure, you know how to make
> long speeches. Even though i don't agree on most of your standings, i
> must say i'm highly impressed by the quality of your argumentation. It
> has been great to read you.[/color]

Thanks ;-)
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

**Daniel Tryba** · Jul 17 '05, 07:57 AM

Re: Wanted: PHP public domain projects

Tim Tyler <tim@tt1lock.or g> wrote:
[mysql][color=blue]
> Commercial users can't make much use of the GPL version because of the
> restrictions in the license[/color]

This is simply not true... in a commercial environment I can do anyhting
to and with GPLed code like I see fit, the _only_ restriction in GPL
activates on redistribution.

I have used many GPLed programs for commercial use. I even modified them
to fit the task. I just will not (and cannot) ever release them to a
third party.
[color=blue]
> GPL code is *copyrighted* - and the license restricts numerous
> rights to the original authors of the code, which puts them in
> a privilidged position to sell their software to businesses
> under different licenses.[/color]

I don't have clue how copyright laws are where you live, but here (NL)
the GPL grants rights to the user, it doesn't take any away (I guess
that will be the same for all EC countries)... No license, no legal use.
A license can transfer anything except ownership.

--

Daniel Tryba

**R. Rajesh Jeba Anbiah** · Jul 17 '05, 07:57 AM

Re: Wanted: PHP public domain projects

Tim Tyler <tim@tt1lock.or g> wrote in message news:<I2JC4M.B8 F@bath.ac.uk>.. .
[..][color=blue]
> Users have been hoodwinked into thinking that they are getting "Free
> sofware" when in fact they are getting "Fake Free Software" - which comes
> with copyright statements and license conditions *just* like every other
> sort of not-free software.[/color]

I think, "freedom" in GPL is for endusers than for other developers.
Your article reminds me phpSt.Manuel Lemo's post couple of months ago.
Personally I too see lot of troubles in using GPLed code; even PHP
guys have deboundled MySQL because of liecencing issue.

--
| Just another PHP saint |
Email: rrjanbiah-at-Y!com

**Keith Bowes** · Jul 17 '05, 07:57 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:[color=blue]
>
> I expect one of the reasons programmers copyright their code is to force
> all their users to keep their name emblasoned on all the copies for ever
> more. It also means that they retain all rights and ownership over it.
>
> That's may be good for the programmers' egos, but it offers no benefit
> for the users - rather the failure to give up rights imposed by copyright
> law creates many opportunities for incompatible license terms - and thus
> hinders collaborative development.
>
> Look at the way you can't use GPL code in LGPL programs. These
> licenses are written by the same guy - yet they fail to inter-operate -
> because of restrictions inherited from copyright law.
>
> Massaging the programmers egos is all very well - but it doesn't
> result in free software. Indeed just the opposite - legally
> *forcing* users to print license conditions pointing to copyright
> notices whenever they run the program takes a freedom away from
> users.
>[/color]

Personally, I agree that the GPL is an overly restrictive license for
all parties (excluding the author). But public domain really isn't the
answer either, for the reason that it gives all freedom to the primary
recipient, but none to the author or secondary recipients. The GPL
seems to be popular by only sheer momentum, but there are FOSS licenses
out there that give more freedom to everyone; I'd suggest using one of
those for your own FOSS projects and making alternate licensing
arrangements with authors of GPL software that you want to use in a
non-GPL-compatible package.

**Zurab Davitiani** · Jul 17 '05, 07:57 AM

Re: Wanted: PHP public domain projects

Tim Tyler wrote:
[color=blue]
> I expect one of the reasons programmers copyright their code is to force
> all their users to keep their name emblasoned on all the copies for ever
> more. It also means that they retain all rights and ownership over it.[/color]

And there's nothing wrong with that. A lot of people want not only
recognition, but also ability to track their projects and contributions for
their personal and professional reasons.
[color=blue]
> That's may be good for the programmers' egos, but it offers no benefit
> for the users - rather the failure to give up rights imposed by copyright
> law creates many opportunities for incompatible license terms - and thus
> hinders collaborative development.[/color]

It goes both ways. If an author gives up all rights granted by copyright
laws, then many "users" (i.e. developers who redistribute) may not, and
likely will not feel compelled to contribute to the public domain, but
rather take from it, claim it as their own, and redistribute in closed or
another fashion. This also hinders collaboration. The challenge is to
provide a fair "playground " somewhere in the middle.
[color=blue]
> Look at the way you can't use GPL code in LGPL programs. These
> licenses are written by the same guy - yet they fail to inter-operate -
> because of restrictions inherited from copyright law.[/color]

LGPL is for libraries which are not programs of their own but are used as
parts of others. It places no restrictions on what license of the parent
program may be. For example, Yahoo messenger uses GtkHTML library.

If you have 2 similar libraries (and you are not their author) A - under
GPL, and B - under LGPL, and you wish to improve either one by adding code
from the other, you can always do so and offer the resulting library under
GPL.
[color=blue]
> Massaging the programmers egos is all very well - but it doesn't
> result in free software. Indeed just the opposite - legally
> *forcing* users to print license conditions pointing to copyright
> notices whenever they run the program takes a freedom away from
> users.[/color]

I am not sure what license you are referring to here, but many licenses like
GPL, BSD, etc. require that you do not remove the copyright notices or
falsely claim that you wrote the software when you didn't. Copyright
notices have nothing to do with egos, but fairness of giving credit where
credit is due.

If you are referring to the copyright notices that many PHP CMSes require
you to print on the front page, I am not sure about those. Supposedly,
copyright and license also applies to the themes they distribute; but what
if I write my own theme? IANAL, I simply don't know.
[color=blue]
> People are limited by default because of copyright law. Licenses
> give rights - rather than take them away.
>
> The GPL simply fails to grant all the freedoms that were taken away by
> invoking copyright law. For example, it fails to give the right to
> make binary-only distributions of modified copies.[/color]

It was not the intention of GPL to undo copyright law. If that's what you
think, then you are wrong. GPL relies on copyright law itself. If you want
to redistribute binary code without the source, use libraries or programs
available under BSD, LGPL, and many other licenses. If you are looking for
a PHP CMS there are some under BSD or BSD-type licenses available. But I'm
not sure how you can distribute them in an object form for PHP.
[color=blue]
> Copyright law imposes the limitations on users of the code. The GPL
> merely fails to grant them back again.[/color]

It cannot fail in something it didn't attempt to accomplish in the first
place.

**Tim Tyler** · Jul 17 '05, 07:58 AM

Re: Wanted: PHP public domain projects

Keith Bowes <do.not@spam.me > wrote or quoted:
[color=blue]
> Personally, I agree that the GPL is an overly restrictive license for
> all parties (excluding the author). But public domain really isn't the
> answer either, for the reason that it gives all freedom to the primary
> recipient, but none to the author or secondary recipients.[/color]

It gives those parties *exactly* the same rights. That's practically
the definition of public domain - everyone has equal privilidges -
and nobody is more restricted than anyone else.
--
__________
|im |yler http://timtyler.org/ tim@tt1lock.org Remove lock to reply.

Wanted: PHP public domain projects

Wanted: PHP public domain projects

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment