Two comments of a highly random and semi-unrelated nature:
Firstly, while I think the new transparency is a very good thing for
everyone, you probably want to avoid too much of a mob rule lest nothing get
done. I know FL has an awesome community (that's on reason why I'm still
here), but there still needs to be order and structure and someone "in
charge". I'm not saying there's anything wrong with everything said above -
I happen to like it very much (as a user and packager) - but be careful ;)
Secondly: AFAIK package contest people still have JIRA access... is that
supposed to be the case? Or perhaps am I the only person left from the
contest who never applied for membership?
Speaking of which, what were the results of the package contest? I never
heard them.
Jack Doerner
There are worse crimes than burning books
One of them is not reading them.
-Joseph Brodsky
On Thu, Nov 13, 2008 at 1:17 AM, zodman <[EMAIL PROTECTED]> wrote:
>
>
> Ken VanDine escribió:
> > Foresight Linux release planning
> >
> > The road to Foresight 2.5 includes you! Historically we have not
> > provided the level of transparency needed to enable more people to
> > participate in Foresight's core development. I am very excited about
> > the packagers that have joined in to help, but I suspect them and
> > others have trouble figuring out what is needed. They have done a
> > great job of packaging new applications and helping to grow our
> > repositories, and we appreciate that. However, Antonio (doniphon) and
> > I do most of the distro work, and that is our fault. We tend to have
> > a good understanding of what needs to be done, and we just do it.
> > This leaves others either not knowing what they can help with, or
> > feeling like they might step on our toes.
>
>
> Yes i want to help to release foresight but only ken and don can do
> this... that because i dont know where needs help only can update from
> 2-qa label an check the bugs/errors. and report on jira.
>
>
> > So what do we need to do? Log all issues we are working on, or plan
> > to work on in FITS (Foresight Issue Tracking System) and continually
> > log our progress on tasks. Not only does this provides us a high
> > level view of where we are, and what needs to be done, but it also
> > provides a wider audience a list of tasks they can step up and
> > accomplish.
>
> Yes this can be a solution.
>
> > We are going with short 1-2 month sprints instead of long 6 month
> > development cycles. During these sprints we will continually push
> > features into mainline, continually delivering innovation.
> >
> > * Sprint Kick off/planning cycle
> > o A larger meeting to discuss major objectives for the sprint
> > + Break it down into the top level objectives and
> > create issues for them in FITS
> > + Hopefully find a driver for each top level objective
> > o Organize smaller planning discussions, ideally done via FITS
> > + Break down the top level objective into smaller issues
> in FITS
> > + Document requirements of success for each objective
> > + Assign a mentor
> > + Assign a due date.
> > + Create Use Cases for testing
> >
> > * Tracking and status reporting
> > o Each assignee will continue to update the progress of tasks
> via FITS
> > o Regular blogging of your progress on your piece of the
> > road map, lets make this fun!
> > o Weekly status reports
> >
> > * Mentoring
> > o We should have some more experienced people available to
> > act as mentors.
> > o Sounding board for ideas
> > o Contribute to and approve designs
> > o Help define measurement for success
> > o Review/approve completed tasks before pushing to mainline
>
>
> agreed with all!
>
> > The key for success is maximum transparency, this means using FITS and
> > the foresight-devel mailing list as much as possible. If you would
> > like to participate, please send an email to our development mailing
> > list. You can find information on the lists at
> > http://www.foresightlinux.org/contribute.html
> >
> > For a list of objectives we are already thinking of for Foresight 2.5,
> > check out this list
> >
> https://issues.foresightlinux.org/secure/IssueNavigator.jspa?reset=true&&pid=10000&resolution=-1&fixfor=10053&sorter/field=priority&sorter/order=DESC
> >
> >
>
> _______________________________________________
> Foresight-devel mailing list
> Foresight-devel@lists.rpath.org
> http://lists.rpath.org/mailman/listinfo/foresight-devel
>
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel
