Brett Porter wrote:
Jason van Zyl wrote:
It's not supplanting the mailing list, it's providing a clear location
for the actions taken by the project.
I totally agree with the need to track stuff properly as I am generally
the one chasing things up, my point was just ot give John a chance to
finish what he's started.
Sure, we think in different ways (which is good) and I don't track
things on a daily basis whereas you generally do. I comtemplate my navel
for days at a time and then step back into the list. I generally just
start answering questions as I see them but I'd much rather go to MPA to
get a summary. I generally don't go back and read the mailing lists when
I've been in navel land. I trust the list has been dealth with. I don't
want to and shouldn't have to look at the mailing list to figure out
that a new repository is going to be created or whatever.
How do you see this working - create an issue before sending any ideas
to the list?
No, no. You/John and whomever else decided that you were going to create
a place for the shared plugin tools. Once that was decided it should be
recorded in MPA as a plan of action.
Seems like unnecessary overhead to me, but given we generally agree it
probably isn't much different. I just think things take shape on the
list first, then you file an issue when you've decided what you want to
do. The person starting the thread follows it up. If nobody cares enough
to do that, let it die.
Absolutely, things happen on this list but must be captured before
passing out of the current frame of reference. A group of people may be
active in forming a decision and some may not. My attention span and
focus doesn't lend itself toward daily dilligence, but I still want to
know what's going on when I have a spot of time.
I have a system for dealing with mail, and I like using the mailing
list. I'm sure I'm not alone. I skip over JIRA stuff much more quickly
and its a whole lot slower to operate with while in the discussion
phase. I do not want to use JIRA for discussion. As long as we're just
tracking and its easy, I'm all for it.
Discussing thing is JIRA, I agree, is pointless. Just the capture of the
decisions and plan of action after the decisions have been made. I
actually don't care about looking at the discussion as I trust it's been
dealt with appropriately. I just want to know that "we decided to create
a module for shared plugin goop".
For the purposes you are talking about, like a/c creation, it sounds
great. You might also look into the (STATUS) mails that other projects
get from a certain file - maybe we can easily maintain a little list in
SVN that can be used for these issues if it is more convenient. Just
tossing out ideas
Ideally there should be many ways to push information into the system
and get it out. I, for example, setup a JIRA project for me and I mail
stuff into JIRA using some ruby junk. We should be able to extract stuff
from JIRA/Confluence and create reports, or take stuff from SVN and push
things into JIRA/Confluence. My current pet project is the board report.
For most of the things I've always reported on I think I can automated:
new commiters, new projects, releases. Being the lazy ass I am I'm
positive I can find a way to do this while i'm sitting on the beach
staring at my navel. And when I come back from the beach look at MPA and
see everything interesting that has happened.
- Brett
---------------------------------------------------------------------
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
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
