On Sun, 2005-10-30 at 10:57 -0500, Jesse McConnell wrote: > great idea, I am finding it a pain to keep up on things too.. > > although the lionshare of [email protected] emails that I think I have > seen are related to automated processes and jira issues themselves...so > perhaps all that automatically generated email should be shifted to another > email list...keep this mailing list for _human only_ traffic..
I generally filter out JIRA issues into a separate folder so that what shows up for me is the human traffic. But even if the volume of the traffic was lessened it more doing several things at once and wanting to come back to the important issues on the list and finding them easily. I just figured a JIRA project that throws the outstanding issues back at the list with a subscription could keep issues from slipping and allow more involvement from the passers by. > jesse > > On 10/30/05, Jason van Zyl <[EMAIL PROTECTED]> 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? > > > > -- > > jvz. > > > > Jason van Zyl > > jason at maven.org <http://maven.org> > > http://maven.apache.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > jesse mcconnell > jesseDOTmcconnellATgmailDOTcom -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
