You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2005/10/30 16:37:27 UTC
tracking development/project discussions/issues
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.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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: tracking development/project discussions/issues
Posted by Jesse McConnell <je...@gmail.com>.
true enough, and with the trackback features of jira and confluence issues
and pages can be linked up very easily..
On 10/30/05, Jason van Zyl <ja...@maven.org> wrote:
>
> 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 dev@maven.apache.org 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 <ja...@maven.org> 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.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: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > jesse mcconnell
> > jesseDOTmcconnellATgmailDOTcom
> --
> jvz.
>
> Jason van Zyl
> jason at maven.org <http://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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom
Re: tracking development/project discussions/issues
Posted by Jason van Zyl <ja...@maven.org>.
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 dev@maven.apache.org 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 <ja...@maven.org> 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: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: tracking development/project discussions/issues
Posted by Jesse McConnell <je...@gmail.com>.
great idea, I am finding it a pain to keep up on things too..
although the lionshare of dev@maven.apache.org 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..
jesse
On 10/30/05, Jason van Zyl <ja...@maven.org> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jesse mcconnell
jesseDOTmcconnellATgmailDOTcom
Re: tracking development/project discussions/issues
Posted by Jason van Zyl <ja...@maven.org>.
On Mon, 2005-10-31 at 15:08 +1100, Brett Porter wrote:
> Jason van Zyl wrote:
> > 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.
>
> Doesn't this belong in the long neglected MPA project?
Yes, and I think the point in the previous email of the the subscription
throwing back issues to the list would prevent this from happening. As
I'm the only one who put stuff there and I was occupied with other
things so it falls into disuse and so no one even knows the issue was
raised.
> > 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.
>
> Sure. I wonder if the wiki isn't a better way to track it though?
I think that's where the content will land but the simple fact that JIRA
can toss back the items up for discussion back to list periodically will
keep things on the radar. JIRA would purely handle the management of the
issues and the issues themselves would most like point at the wiki. But
the road map could be aligned with releases and serve to show what
design and organization issues were dealt with for that release apart
from the pure technical issues dealt with.
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: tracking development/project discussions/issues
Posted by Brett Porter <br...@apache.org>.
Jason van Zyl wrote:
> 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.
Doesn't this belong in the long neglected MPA project?
> 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.
Sure. I wonder if the wiki isn't a better way to track it though?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: tracking development/project discussions/issues
Posted by Jason van Zyl <ja...@maven.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: tracking development/project discussions/issues
Posted by Brett Porter <br...@apache.org>.
Sounds fine to me (there is a design component that can be used).
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.
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.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org