Re: [Announce] WebObjects Community Steering Committee
Re: [Announce] WebObjects Community Steering Committee
- Subject: Re: [Announce] WebObjects Community Steering Committee
- From: Kieran Kelleher <email@hidden>
- Date: Fri, 26 Oct 2007 12:12:40 -0400
Hey David ,
Have you not noticed my enthusiastic contributions to the wiki?! ....
I am already signed up! ;-) While there is a much-appreciated core
group of advanced developers adding tools and source code to WOLips
and Wonder ...... I think it is only fair that those, whose
circumstances allow of course, try to add to the WebObjects wiki
documentation, so that the newbies don't have such a hard hill to
climb at the start and so that the non-newbies have a place to search
for clarification of stuff that has been forgotten. I love the fact
that we can search the whole confluence (all spaces) so easily to
find solutions.
Sure .... count me in ..... I'll be happy to hack away at the
WebObjects confluence space wiki docs .... what is there is quite
*excellent* content ..... it just needs refactoring to bring up to
date since the tools have changed and advanced so much and maybe
reorganization and or additional topics to make it easier for a
beginner to start at the beginning and learn WebObjects from that
wiki just like he/she would have if they bought a WebObjects beginner
and intermediate book.
We need to be careful not to put stuff here that is already in or
should be in javadocs for example ...... so we could link to those in
the online Wonder API or WebObjects API.
For example Wonder is such a huge topic ... IMHO it should remain in
its own confluence space and we need to keep adding to the Wonder
wiki docs so everyone can benefit from the wealth of resources in
Wonder. IMHO, we should be encouraging people to download and get
familiar with Wonder source too ..... it is an excellent source of
learning.
WOLips should obviously continue with its own space ...... perhaps
adding/refactoring the docs/tutorials there so that we have a WOLips
Tools wikibook with sections for ComponentEditor and EntityModeler.
This whole wiki book for WebObjects is a great concept IMHO.... gives
us a opportunity to document the collective community experience and
expertize..... I especially like that our stuff is hosted by the
community (thanks Andrus, Mike, ,etc.) rather than public wikipedia.
I don't remember who started the original WebObjects wikibook
brainchild on wikipedia ... that was a turning point for centralized
online WebObjects docs. Now we need to build on that in the
objectstyle wiki.
Regards, Kieran
On Oct 26, 2007, at 10:40 AM, David LeBer wrote:
On 26-Oct-07, at 10:16 AM, Kieran Kelleher wrote:
A task for the list might be:
* Bring wiki up to date .... eliminate all references to obsolete
WOBuilder, EOModeler, etc.
http://wiki.objectstyle.org/confluence/display/WO/Home
What might be nice is to structure this WebObjects wiki like a
book (with a TOC like the one that Chuck had planned to publish,
but didn't)
Hey Kieran,
We are looking for volunteers for the documentation working group.
Wanna sign up?
:-)
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden