On Aug 15, 2006, at 1:04 PM, [EMAIL PROTECTED] wrote:
I don't completely agree here. Obviously we have no say in the
direction of the product; Apple is going to serve their internal
needs first and there probably won't be any cycles left over for
anything else. But I do think there is value to us in promoting WO
however we can. For our own personal business reasons, the more
buzz there is about WO the more likely clients are to be
enthusiastic about using it instead of needing to be convinced.
Seems very strange strategy. "Advertise it" T-shirts make a nice
statement, but it is a dead-end for all practical reasons when done
by anyone outside Apple. "Open Source It" maybe.
I am more in favor of the approach taken by the companies behind
projects like Apache Geronimo (an open source spec-compliant J2EE
server) - if you are to invest money in certain technology that you
do not control, change the rules and take control! That's exactly
what WOLips is doing. Otherwise don't bother to get too attached to
it and be prepared to jump ship when it goes down. (Note that I am
not flaming Apple here - they are doing what makes sense for them)
Invest in the existing open source WO community instead! If you
have something to offer as far as WO future direction, this is the
place to do it and make a difference. Wonder has 41 committers,
WOProject/WOLips has 11. How many actually commit code on a
regular basis? 3-4 people at the most. Not enough to start a
foundation, but if you come and participate, this may change one
year from now.
The best advice I can give here is that it needs to be as easy as
possible for people to contribute. Lessons from the past once
again; in my old life documentation had to be in Docbook format
and basically ready to publish, so very few people wrote any unless
they were being paid to do so.
Main doc system for WOLips/WOProject is Confluence Wiki - can't be
easier than that - just log in and create content. I can set up one
for Wonder or any other WO open source project out there as long as
somebody requests it. Same goes for Jira issue tracker.
Likewise they keep trying to require test cases with every patch,
so fewer and fewer of those are coming in.
Not the case here, but I agree with your bigger point that the
barrier to entry should be lower. Since this is a volunteer effort
just as much as coding, don't be afraid to chime in and work on it.
Andrus
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
