On Mon, 2005-10-31 at 08:53 +1100, Brett Porter wrote: > Sounds fine to me (there is a design component that can be used).
I think it would be more then design as the first one I can think of that is more task oriented is starting a campaign to find a lot more mirrors on the scale of CPAN for perl. > Let's leave responsibility of the original poster to follow an issue > through to conclusion. I still have the dev process flagged, for > example. I could just as easily file that to start with. That's exactly what I would like to try and distribute a little better. For example if Vincent is the one to originally champion the J2EE best practices effort, and then eases off a bit and Jesse sees that he interested in this issue, has time and runs with it. Not that you can't go scan through the mailing list, but what is on the table could be more immediate and transparent then that's better. > The main thing I want to avoid is using JIRA for design discussions. > That is always problematic when it happens. List posting works best, > possibly with summaries on the wiki. I agree that JIRA is not the place for design. I really just want this as a sign post to anyone who's eased off for a while and is coming back in or people who are coming into the project for the first time. > Cheers, > Brett > > Jason van Zyl wrote: > > Hi, > > > > I wanted to field ideas on how to track development/project > > issues/discussions. Lately with the volume of mail I myself have found > > it difficult to keep track of things we have been discussing. A couple > > topics I remember are: > > > > - standard j2ee layout > > - our own development process > > > > But sifting through mail can get difficult and there is generally no > > easy indicator associated with documents as to whether something has > > actually been resolved or not. > > > > I was thinking that a simple solution would be to have a component in > > the MNG JIRA projects for items like the two mentioned above. Then you > > could see what discussions where started and still in progress and > > historically you could see what major issues were resolved. > > > > Vincent, Brett, Carlos, and myself are trying to gather content for a > > book and I know that things I'm supposed to write about I can't write > > about because there are some issues with our practices that need to be > > resolved like: > > > > - best practices for multi project setups > > > > And there are general architectural issues like: > > > > - how are we going to make additions to the POM and guarantee > > backward/forward compatibility when we do (for example I want to add > > site staging elements and categories for indexing projects). > > > > I figure that a JIRA component would be the simplest and easiest thing > > to do and it could reference wiki pages or mailing list discussions. > > > > Any thoughts? > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
