On 27 Jun 07, at 6:15 AM 27 Jun 07, Mark Hobson wrote:
Looks good in general. I found it a little confusing how the info was
split across the two pages (Home and All Proposals). How about
changing the All Proposals page to encapsulate all proposal
information in one table? It would look similar to the
work-in-progress table on Home, but it could have a status column for
draft, pending, approved, work-in-progress and implemented.
You want to just try re-arranging it so we can see?
Mark
On 27/06/07, Eric Redmond <[EMAIL PROTECTED]> wrote:
Not that this is really the thread for it, but +1 on trying out
xwiki!
Namely because Vincent is an insider (always nice to have) and I
never
really liked Confluence much anyway.
Eric
Not an XWiki Developer ;-)
On 6/26/07, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> Hi Jason,
>
> Sounds very good to me. You're right that making things surface
is a
> good thing. It requires more discipline but Maven being so
successful
> and so many people relying on it now makes it a necessity I
think to
> better control its evolution.
>
> Now all you need is a good wiki that allows you easier
implementation/
> follow up of that process... ;-)
>
> It would be real easy with xwiki to have a template for
proposals and
> have a status combo box on each proposal that you could use to
move a
> proposal between states. That would then allow you to query the
> proposals and list them on the dashboard page in the right category
> and do other nice things... (like, automatically send an email
when a
> proposal in the draft state hasn't been touched for the past 6
> months, or whatever comes to mind).
>
> -Vincent
> XWiki Developer (just to show that I'm probably biased... ;))
>
> On Jun 26, 2007, at 1:02 AM, Jason van Zyl wrote:
>
> > Hi,
> >
> > As part of trying to make the whole process of making changes and
> > adding new features transparent to everyone involved I've whipped
> > up a little sketch for perusal:
> >
> > http://people.apache.org/~jvanzyl/DevProcess.png
> >
> > Basically it revolves around making sure things are documented in
> > the Wiki and providing a clear record of the evolution of the
> > project that anyone can follow at any point in time. So far from
> > perfect but I think a good starting point and I would like to
field
> > feedback so I can improve it. It basically revolves around the
> > dashboard where I've tried to collect all relevant information
> > about the project:
> >
> > http://docs.codehaus.org/display/MAVEN/Home
> >
> > And process is based around making proposals that eventually will
> > serve as the record of evolution of the project. The goal is
not to
> > have anything that's heavy, and that we might eventually be
able to
> > automate some data gathering but for the meantime it's not overly
> > onerous and provides some visibility we have not yet had to date.
> >
> > The proposals are all here:
> >
> > http://docs.codehaus.org/display/MAVEN/All+Proposals
> >
> > And they basically move from draft -> pending -> approved.
I've put
> > some notes in the diagram and I figured we could start with a
> > simple proposal to see how it works and iron the kinks as we go.
> > This is experimental but I see it as the best way forward for
> > getting a clear view of what's going on
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder and PMC Chair, Apache Maven
> > jason at sonatype dot com
> > ----------------------------------------------------------
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Eric Redmond
http://www.sonatype.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
