Re: [e4-dev] Do We Need a Book?
I totally understand your situation and agree. The core developers should concentrate on stabilizing the framework to make it a success in June this year.
But why not forming a small team of 3-4 guys who are willing to write this book aswell? This team mustn't consist of core e4 developers only so why not creating a separate authoring team? For sure this team must have people who know the framework deeply but are NOT involved into coding AND this authoring-team should be able to ask or discuss questions with the core developers at any time. Direct. Without Maillinglist. Maybe one of the core e4 developers is wiling to act as a mentor?
2012/1/9 Eric Moffatt <emoffatt@xxxxxxxxxx>
Mike, I had to think about this over
the weekend in order to get my story / concerns straight...
1) I really do think that Eclipse 4
/ EAP deserve a book and I also think that the eclipse community would
get true value from it
2) I'd be quite happy to work with others
on making this happen
- but -
We are currently focused on ensuring
that Eclipse 4 Juno is all that it can be so any time spent on the book
will have to be balanced against the Juno work. All indications from those
I've talked to warn me that it'll take more time that it would appear to
need at first blush.
I have no idea how the book writing
process goes as far as getting a publisher / editor...can you clue me in
The timing is such that (for me) it
would be best to get started on this now (content gathering, structure...)
but as a background task, leaving the bulk of the editing work until after
the Juno release (this would also ensure that we can cover off any late
My 2 cents...I'd love to hear from others
that may be interested in making this happen...
With Eclipse 4 going mainstream in June,
it occurs to us that there could very much be a need for some sort of book.
I certainly defer to the much greater wisdom of the people here, but something
along the lines of the following would be of great value:
Is there any group of people on this list
that would be interested in working on such a book? Calling Lars Vogel,
Tom Schindl, Kai Toetder, Eric Moffat, Remy Suen, and I am sure many other
Office: +1.613.224.9461 x228
- What is the Eclipse 4 platform? Its motivation,
and its benefits.
- Why Eclipse 4 is a better RCP
- Backwards compatibility
- A migration guide on how to move your Eclipse
3.x RCP application or plug-in to native Eclipse 4.
e4-dev mailing list