tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Kuhnert" <jkuhn...@gmail.com>
Subject Re: Anyone ready for 5.0.14?
Date Thu, 03 Jul 2008 03:09:04 GMT
I'm not sure what words of wisdom I could share but I do sort of see
both sides of this,

I think my best experience with a similar situation was when I spent a
few weeks mulling over
some ideas for some jini stuff and shared them with what is probably
my first big software mentor
and was told that "I'm free to implement them,  just don't get mad if
you have to throw it all out".

I didn't have to throw ~all~ of it out,  but I certainly was corrected
in a number of things.

At the end of the day,  despite his project management warts and all
the typical framework
competitive posturing bullshit that everyone goes through - Howard
really is one of the most
gifted software designers I've had the pleasure to work with.  So,  be
prepared to be
shot down but also know that the knowledge you gain from the
explanations of why what you are doing
won't work isn't something you are very likely to come across in your
day to day development activities.

You won't find many opportunities to flex these kinds of designs
muscles that will impact more than
a couple people on your development group for however long the product
incarnation you are working
on lasts.  This stuff lasts much longer and has a much bigger impact
on people and your general understanding
of how/why API development works.  Start small and work your way out.
There's nothing lost in being wrong,  just
in not learning something new.

On Wed, Jul 2, 2008 at 6:30 PM, Howard Lewis Ship <hlship@gmail.com> wrote:
> Its a problem for me.  If Tapestry were a project at Formos, not at
> Apache, I would have a team, we would agree on dates and deliverables,
> etc.  People would be responsible for what they are assigned, or take
> on.
> What pains me is that many people have ideas about what needs to be
> done, sometimes very vocal ideas, but that's as far as it goes.
> The structure of the code (components and IoC services) should make it
> reasonable for people to "set up shop" in a specific area, as you
> describe.  It just isn't happening.
> For every trivial bug that I end up fixing, it's one less critical bug
> I can take on.  And when, like now, I'm client focused (preparing for
> several days of training), not much is going to happen.
> On Wed, Jul 2, 2008 at 3:11 PM, Ben Dotte <ben.dotte@gmail.com> wrote:
>> Perhaps I am just naive to the way open source software is supposed to
>> be written, but it has always struck me as odd that particular areas
>> of the framework aren't divvied out to specific committers, or maybe
>> even groups of committers, to work on. I like to feel responsible for
>> a particular segment of a codebase, it encourages me to fix bugs in
>> that area and I feel like I have some level of control over the
>> general design of that area.
>> I'm not saying I in particular want to be assigned an area--a new baby
>> and my job keep me plenty busy these days :) Not much time for
>> Tapestry, unfortunately.
>> Something like that probably really needs to happen earlier in the
>> project though, when there is still enough of the core architecture
>> available to be designed.
>> Just my 2 cents.. I'm not trying to be critical of Tapestry, it is and
>> has been a wonderful framework. But I think it is something worth
>> discussing if you are wondering why people aren't as interested in
>> contributing as you would like.
>> "I hate to be a nag, but I haven't been seeing a lot of commit activity
>> from everyone else. That's very troublesome, and I'm concerned it
>> reflects on my management style of the project.  If you have any
>> criticism, feel free to respond here or privately to me.  I won't be
>> offended --- I already recognize that project management is by far my
>> weakest skill!"
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
> --
> Howard M. Lewis Ship
> Creator Apache Tapestry and Apache HiveMind
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org

Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message