To achieve success with this initiative, it needs to be more organized. As a contributing author for an "Open Source" book for O'Reilly, I'll be the first to underline the importance of proper editorial and content controls in place.
I really liked the way they did it - here's the portal all the authors and editors used: http://97-things.near-time.net/wiki/97-things-every-software-architect-should-know-the-book This was done really smartly, and we went from concept to print in less than 6 months. We don't have to use "near-time" as the portal, we can always go ahead and use an open source platform like: http://moodle.org/ Cheers, Zubin. On Fri, Jan 30, 2009 at 1:09 PM, manish kumar <[email protected]> wrote: > If idea is for the book to keep evolving, wiki would be a good idea. > All twincling registered users can be given edit access to it. > > On Sat, Jan 31, 2009 at 1:07 AM, Saifi Khan > <[email protected]<saifi.khan%40twincling.org> > >wrote: > > > On Fri, 30 Jan 2009, roshan jose wrote: > > > > > so how do we start with the contribution. explain in detail how after > > selecting a particular unit we are are supposed to produce..... > > > > > > > Inside every unit, there is a list of topics that the unit > > should cover. A contributor can pick any one topic item and > > write about that. > > > > The idea is that as the content of the book evolves, it can be > > refined, redefined and streamlined to make the flow more smooth. > > > > Please refrain from adding links to blogs, personal opinions. > > > > thanks > > Saifi. > > > > > > > [Non-text portions of this message have been removed]
