Regarding Wiki, here's my thoughts:

A lot of the old stuff is probably not worth updating, and should probably be put into 
some 
"obsolete" area.

As far as team planning goes, I'd like to encourage people to be aggressive and 
fearless in 
pursuing changes.  With some caveats:

1. Things that are possible now should remain possible unless the team agrees 
otherwise in a 
more formal decision making format.
2. Long term things you're working on should be described on a wiki page - I think a 
page per 
developer would be the best way to organize it.  That way, if I want to work on X, I 
can check 
everyone's page to find out if anyone else has already started working on it.
3. Make an effort to write unit tests.  I've started making PackageTest classes to 
collect all 
unit tests from a package together, and I think it is a better option than the inner 
classes I've 
been using.
4. If you pick a large area/idea to work on, start with some refactoring as it helps 
you learn the 
code and pick up on something of the more subtle aspects of what's going on before you 
dive 
in.

I think that attitude will result in the best combination of a)getting stuff done, and 
b)getting stuff 
done right.  If someone starts going off the deep end, someone should notice it from 
the wiki 
page and draw the team's attention to it.

So, I suggest everyone make a wiki page for themselves (see: 
http://nagoya.apache.org/wiki/apachewiki.cgi?JMeterDevelopment) and make some notes 
about what you're thinking about doing, and what you are actually doing.  

And, even for projects that several people will want input on, there should still be a 
project 
leader on who's development page the information would go (ie, everyone should feel 
free to 
edit everyone else' wiki pages).

======================================

On another note, I think I'd like to make a release branch of 1.9 so that simple bug 
fix releases 
can be made without impacting new development.  I would very much like anyone who does 
bug fixes to make their fixes to BOTH branches, so that no merge ever needs to be done.

-Mike



On 12 Aug 2003 at 17:48, Jordi Salvat i Alabart wrote:

> 
> 
> BAZLEY, Sebastian wrote:
> > Aside: some of these e-mail trails are getting quite long - how about using
> > the Wiki to collate the information?
> > 
> 
> Not at this stage -- we did that in the past and was fun, but not very 
> successful. It looks like a good place to create documentation, but not 
> quite a good one for discussion.
> 
> When time comes to transform discussion into a plan, the Wiki may help.
> 
> BTW, would be nice if we went there and did some cleanup of obsolete 
> information and discussions.
> 
> -- 
> Salut,
> 
> Jordi.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 




--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to