Andrew C. Oliver wrote: (...)
I prefer to call it "the monkey house" http://blogs.cocoondev.org/stevenn/archives/000769.html
;-)
Now that I got you back into "the monkey house", even if briefly, we can remove the CC: jakarta
BTW: how in the hell has Stevenn found that I'm here just waiting for a pretty girl to "knock on me"? :-)
(...)
I have facts which back up my belief that we affected this, but I won't go into them as its not relevant. This is my "non-monetary compensation".. . I can't wait to see them on www.f*ckedcompany.com. Sadistic? Maybe. However, I enjoy it.
Let me play "elder brother". This is closer to the "Dark Side of the Force" than I like. But, as Conrad would have said: "A man must work to some end", though the context is fairly different. http://www.online-literature.com/conrad/nostromo/6/
I don't say that I don't take my trips to the dark side. ;-)
(...)
I disagree. The Apache licensing model is oriented towards "club works" or towards use by big companies. I would license a tool if I'm trying
That's the producers. I was talking about the consumers (of Apache Licensed stuff). You see, there are always two sides in a rope. (I've just invented a new English saying)
But it is true: big companies will license them, consultants and integrators (working for/in) big, medium/small companies or independent, will use them. Contributors will come from both ends.
(...)
too dogmatic about this. If you happen to GPL and someone wants to pay for a license so that they can embed it, then taking their money sounds like something good to do.
But you would need a good niche. see below tools/apps.
There are limitations (how to handle contributor requests for the same) but life is a tradeoff. (you give up the restfulness of death ;-) )
vs the soapiness of what? ;-) http://www.google.com/search?q=rest+vs+soap
(...)
And thats why most Apache projects are "tools".. . Not saying this is a bad thing. Just that it TOO has its tradeoffs.
In a networked environment you have no longer tools vs applications, but tools vs services ;-)
Conclusions? not many:Yes I came up with the idea all by myself....actually I stole it from one of the web pages Jon wrote a long time ago ;-)
* Community success is community (user and developer) benefit, not downloads or size. This is what stroke me of Andy's post
I respect him much more now than the first time I saw him falling on uncautious newbies (I think it was on me, actually): http://www.geocrawler.com/mail/thread.php3?subject=i18n+bug+nailed+down%21&list=449
(...)
There are downsides to the Apache model. (As there are to the GPL model).
* Companies start thinking Apache is a great clearinghouse of developers to implement their latest proprietary standards. (JSRs) This is to the detriment of community as some developers are "in the know" and others just do what they say. Projects based on living JSRs cannot truly be community-based as some members of the community make decisions that others cannot play a part of, not by merit but by legal agreement.
* Companies fork Apache projects and start JSRs based on them and then attempt to get Apache to adopt the JSR instead of the free-er codebase. This effectively takes control away from the community.
The two bullets would not be bad (some communities are very closed) if the JSR was more open, more like the W3C standards. Specially if the big companies had to play their cards in public. I'm strongly in favour of this. I mean, they would need not just to win, but to convince.
* Attrition - Because developers often cannot support themselves off of this model (in competition with big companies with brands), You often see attrition at a higher rate than successful GNU projects.
Ricardo Rocha's view on this was like:
I make money as a Consultant. To keep being a good Consultant, I need to experiment and write code. I give the code for free, just like a musician would go to the "tube" to rehearse and make some bucks.
Doing this in Apache brings me additional exposure "for free". The balance was supposed to be good overall.
This was a couple of years ago. I wonder where he is now.
(...)
P.P.S) It's not polished, but I *needed* to express this. It's just what I think, and I *don't* want a licensing flame war.Oh you can't say the word license without starting a flame war. However, we'll just ignore them because I always enjoy talking with you my friend, even if my young age makes me stronger in my opinions than you think appropriate time will tell if this changes with time ;-) :-p
I see that your Spanish lessons are going well ;-)
I'm sure your opinions will stand over time. I wrote this while I was a bit depressed. Now my back is getting better as Spring approaches.
Regards,
Santiago-Andy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
