The Joomla! Forum ™

This post probably doesn't really belong here but I simply do not want to drag this issue back into the regular discussion forums to make a new free for all thread....

We are wasting our time here without any solution to the problem!

We should not be focusing on fixing the problems Proprietary 3PDs have with writing extentions for a GPL program.
Top of the list should be making J!1.5 stable!
What we should be doing is moving Joomla forward towards V2.0 and while that is being done, take a look at what needs to be replaced to ease this issue for all concerned. That means:

1 - rewriting borrowed GPL code so that Joomla can be the sole owner and arbitor of license for these codes.
2 - relicensing GPL code from the authors so that Joomla has the power to give exceptions for proprietary use. That would entail making contracts with developers who agree to allow J! at some point to allow proprietary derivatives to use that code or relicense it under an LGPL license. If any developer of borrowed code does not agree to do this then see #1
3 - improving those codes so that they can accomodate what is needed for a future V2.0 either as part of task #1 or as a modification during task #2
4 - Finish the job of seperating the API so it is a seperate work from the CMS and can be relicensed to allow use of the API without distribution. This could be LGPL but I would suggest a new license JEL (Joomla Extentions License) be created that allowed proprietary work to use the API but disallowed encryption, required Access to Source, gave users modification rights and limited re-distribution of source without modification. This would allow Prorietary extentions to be open source but only those whoi could develop the code and add features would be allowed to re-distribute that code. that would leave proprietary developers some exclusivity to their version but allow enhancements which would spur developers to stay on top of their product to maintain marketshare. It would also make it easy for users to provide bug fixes and security patches on projects where the P3PD is slow to respond. the seperation of the API is a goal for V2.0 so it's not like doing this will take the project off it's current track.
5 - P3PDs should stop complaining and help to meet these goals and tasks. It is not fair to expect someone who is not making a cent to accomodate you if you are unwilling to accomodate yourself.

Bottom line is we could argue this from now until J! 5.0 comes out.
Talk is cheap and solutions are expensive not monetarily but in time!
there is so much work to be done to get to V2.0 and this raging debate is not doing anything to get us there!
We need to start throwing the code around instead of accusations and whining.
Cause I have yet to see a website or feature run on accusations and whining!
They all run on code!

Last night I rewatched the great, great "How Open Source Projects Survive Poison People (and You Can Too)"

http://video.google.com/videoplay?docid ... &plindex=0

It made me realize, a. how wise most of the core team has been for staying away from the forums for the most part and sticking to the code  (and documentation and event planning etc) instead  and b. why the rest of us need to stop responding in such depth to some (not all) of the posters. 

Anyway, I'd recommend the video to everyone.

In the meantime, lets all go do something productive.

_________________
So we must fix our vision not merely on the negative expulsion of war, but upon the positive affirmation of peace. MLK 1964.
http://officialjoomlabook.com Get it at http://www.joomla.org/joomla-press-official-books.html Buy a book, support Joomla!.

Unfortunatly the folks who are doing the most complaining aren't interested in Open Source...

One of my personal heroes is Andy Grove...

Two things he said (one of which relates to the video you mentioned):

(Paraphrasing)

Second Quote which is where I was coming from in my original post...
I am proposing that this issue has a technological answer. If people would stop looking for the social or legal, and work towards that technological answer this problem would not only be solved now but most likely forever!

Lets stop focusing on the CAN'T do and get working on the CAN DO attitude that got us this far.

I think the Devs, OSM, and the mods, have done a good job in bringing the issue that has always existed out into the open. An issue that truth be told is not really of their making but merely a deficiency in the way the GPL itself was written.
the GPL seems to me to be more concerned with the growth of GPL than it is concerned with the growth of any idea protected by that GPL. It says they are talking about Free ideas not Free beer but the truth of the matter is that in order to be compatible with a GPL license it must also be free beer! Sure you can charge for your idea but after the first charge that idea turns to free beer!
All due to the requirement and specified right of COPY (verbatim) distribution...
Verbatim distribution is not really needed to diseminate those ideas. What is needed it the right to modify and distrubute those modifications so that these ideas can be put to use without restriction. I'm sure many P3PDs would have less of a problem if they knew that their version of the program was going to be their version until they changed it. And if they knew their competition was going to be only people who could add to their original idea then they might not have as many problems GPLing under those conditions.

But no one from Joomla or OSM can solve this issue for them in a legal or social way.
If anyone wants to solve it this way they should petition FSF to create a new license that allows free distributions for modified ideas not verbatim. Waste of time trying to get that changed here.

If they are interested in the technological solution then roll up your sleeves and help the Teams to create one. It will be more long lasting for sure and would solve the problem not just now but 50 years from now!
It will also serve to accelerate the push towards V2.0 of Joomla since the more coders working to make the seperation of API with the CMS will free up the core Developers to work on other more pressing needs like a more finely tuned ACL, a much better CMS to complement the API such as Multi Cat content and Standards based output.

United we stand and grow...
Divided we fall and get nowhere!

I have to think the P3PDs if they stopped and thought about this without the self centered emotions they would see that they have just as much ability to change the Project known as Joomla as anyone does.
All it requires is creating code you won't make a buck off of now but lots of bucks off later when the project is finally able to allow proprietary work to be combined with this free idea.