Brett Porter wrote:
Jason van Zyl wrote:
Brett Porter wrote:
No, its for plugin shared library space: see
<[EMAIL PROTECTED]>
Can you guys please put stuff that is planned for the project in MPA.
The vote was only on the 22nd. We can't have other tools supplant the
mailing list as far fewer people follow it. Now that we've all discussed
it, the action items should go in there, sure.
It's not supplanting the mailing list, it's providing a clear location
for the actions taken by the project. Trying to sift though the mailing
list is tedious and discussions can always occur on the mailing lists
but someone needs to capture the discussion. The mailing list does
nothing to capture the salient points of a conversation. It's not the
overriding of the mailing list for the conversion, I'm just saying
distill the conversation and push it into JIRA. N people should not have
to sift though the mailing list to figure out what's going on with the
project at a given point in time whether that be people internal or
external to the project. They should go to MPA (or the equivalent) and
see it clearly. And MPA should be pointed at when we're discussing
things like creating new repositories or any infrastructural change.
Why I see this as important as it provides some audit trail for the
project. There is no way you're going to be able to pick off all these
salient points from the mailing list once they have passed out of the
current frame of reference. Absolutely no chance. What I want to use if
for is to provide key points in the report to the board. If the
information is captured at the point of discussion it will work.
If I happen to not follow the mailing list for a week I should still be
able to see what's currently slated for the project, and that should be
visible over a span of time. Not only important for us but for
interested parties like the board or people stepping into the project
looking at what's going on.
As a matter of practice in the hopes of providing more visibility I
would like to see the salient points of these types of discussions go
into MPA. I've been trying to track new commiters, and infrastructural
changes and hope to be able to point the board at the issues. I would
actually like to setup JIRA (or Foo issue tracker) and Confluence (or
Bar wiki) in a standard way (a la Maven) so that I can extract this
information for a report to the board and, possibly the community in
general actually. The information passes by all of us so lets try to
capture it and make it accessible. The mailing list is not accessible as
it requires the duplication of human effort to find everything all over
again.
If someone else is running with something I don't want to have to track
them in order to know what's going on, but it would be nice to see that
somewhere. Everyone is going to have some interest in something and
naturally be more involved in some issue or another and that's great.
But if I or anyone else is not watching and the information isn't
captured sifting through mailing lists isn't efficient, appealing or useful.
No, I created a converter component in /components/trunk like I said I
was going to (And had planned to last week but got side tracked).
Well, I don't realy know any more. I've been working off the assumption
anything not bundled in Maven goes there, but again this is pretty
closely tied to the maven-model release so maybe its better off staying
in /components.
Right, this is why I think recording things like this in MPA is
important as I have no idea what's what at the moment insofar as new
project setup. We capture everything else in JIRA. I think our process
is just as important to capture. Mailing lists just aren't enough by
themselves.
- 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
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
