I think you should write the book, but only if there's going to be a T5.1.1.x set of releases with bugfixes - this is long overdue in my opinion. (we have too many 'temporary' tapestry fixes - it's annoying & embarrassing) I don't think there's any pressing need for T5.2 yet (IMHO) but there are a lot of bugs in JIRA and some of them are quite serious. You have a few good committers and a community who often submit patches when they enter bugs. What's missing is getting some momentum and getting the results out there in official releases!
Doing this would allow you to carry on your consulting, write the book (very important, although just having an English language version of Igor's might be enough, especially if you rounded out any areas you felt needed expanding - maybe a joint effort?) and spend a little time here & there on any bugfixes you feel need your personal attention. (if there are any) Whether or not you're involved in the releases is up to you, but at the moment nothing's happening which is not good. Cheers, Andy Blower. > -----Original Message----- > From: Howard [mailto:hls...@gmail.com] > Sent: 07 November 2009 18:11 > To: users@tapestry.apache.org > Subject: [Tapestry Central] Next Steps for Tapestry > > I've been consciously letting Tapestry 5.1 sit and stabilize for a > while ... a time that's stretched a few months longer than I initially > intended. > This is due to a number of factors: my return to independent > consulting, my desire to write a definitive Tapestry 5 book, and > preparations for many trips and speaking engagements. > All of these factors have worked on each other: I've been improving and > extending my Tapestry Workshop training materials which can be quite > time consuming. I've also (over the last several months) been on the > road several times, talking about Tapestry or doing Tapestry training. > I do want to write a book on Tapestry but if I start writing 5.2 code, > I know I'll be sucked right in ... lots of code (that darn Spring Web > Flow integration for sure this time) and bug fixes. > In addition, I've had an embarassment of riches: two main clients, one > regular part time, and the other requesting (but not always getting) > all my remaining time. I also have additional clients and training > engagements waiting in the wings. I simply have a lot of draws on my > time. > As usual, working on real-world projects lets me experience the "rough > edges" of Tapestry and fills me with ideas on how to address those in > the next release ... often by splitting up Tapestry services into > smaller, more easily overridden chunks and carefully moving internal > services out into the public APIs. > Finally, I've been very pleased by the fact that as I've stepped back > temporarily from my normal stream of commits, the other Tapestry > developers have stepped in and filled the gap. There's been quite a bit > of activity especially from Igor that I've barely had a chance to keep > up on. > So the question is: do I wait and see if time opens up in Q1 to > actually start on a T5 book ... or do I jump into 5.2 coding and leave > books to others? It's much, much easier to write code than to write a > book ... a book is a large amount of concentrated effort. It's very > hard to accomplish anything on a book using an hour here or an evening > there ... whereas Tapestry's code base lends itself to that kind of > effort quite nicely. > > -- > Posted By Howard to Tapestry Central at 11/07/2009 10:11:00 AM --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
