Being a coworker of Bens (as well as a simple lurker to this mailing list) gives any vote I would cast less weight than most, however I do feel that I could share a bit about Ben to help the voters make up their own minds.
In a development team with over 20 years combined experience working with Tapestry, Ben has proven to be one the most resourceful and knowledgeable developers we have in the less than two years he's been with us. He is always on top of the latest changes and developments in the Tapestry tree and is a frequent contributor to the users mailing list as well as to Tapestry JIRA =). Jesses impression of Ben could not be more spot-on. His interests lie in keeping Tapestry 4.x a stable and reliable project because that helps him get his job done. He often digs deep into Tapestry internals to understand why bugs are surfacing and works with the Tapestry team to report, reproduce, and (when possible) provide resolution to problems. And, yes, he's about the right level of "anal retentive". =) I know that as a Tapestry committer, Ben would bring the same qualities to the project that he has brought to our company: a genuine interest in developing useful software and the attitude and skills to do so effectively. I hope this email wasn't too inappropriate for this list, but it can sometimes be difficult to get the measure of a person on the Internet and I wanted to share what I've learned about Ben from having worked with him these last couple of years. Regards, Bryan Dotzour On 5/14/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > I'd like to start what I think is the first ever dual vote for two new > Tapestry developers. > > These are the shared attributes I think makes both of them a valuable > addition to our team: > > -) Have been developing with Tapestry for a long time, active on the > mailing > lists. > -) Are currently using the latest 4.1.2 versions in their respective > employers products on a daily basis, providing valuable feedback in > private > / JIRA / as well as patches. Ben especially has been invaluable in > helping > get ognl 2.7 out the door. > -) Have given me the general feeling of being fairly anal retentive when > it > comes to their code. A quality I personally value and think will mesh > well > with the standards Howard has already set up. > -) Both have a long term vested interest in seeing Tapestry 4 come to > maturation in real world large scale products / projects. > -) Both have also been doing ajax related development for a long time > already - starting with Tacos and now with the more recent features in the > 4.1 series of Tapestry. > > Like most of the recent incoming committers (including myself) - Marcus > also > hosts his own Tapestry based open source project at > http://honeycomb.javaforge.com/. This is a tapestry/hivemind based > library > for integrating hibernate. > > Though Ben isn't currently hosting any outside projects (that I know of) - > he and his co-workers have been consistently and diligently providing tons > of invaluable feedback / JIRA issues / patches for a long time. > > Even more importantly to me - I'd like one day to be able to contribute > something to Tapestry 5 but don't see that happening until Tapestry 4 gets > finished up. I've not had any feeling that either developer has a lot of > radical ideas for changing things but more just that they'd like to see > the > existing functionality mature and stabilize, which is exactly the kind of > development support we need to see Tapestry 4 come to a happy end. > > The vote will run for 1 week at which point I'll tally up the results and > post them back to the list. > > Marcus Shulte: +1 Jesse Kuhnert (binding) > Ben Dotte: +1 Jesse Kuhnert (binding) > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
