On Thu, Nov 13, 2008 at 11:56 AM, Kevin Harriss <[EMAIL PROTECTED]> wrote: > > > On Wed, Nov 12, 2008 at 1:32 PM, Ken VanDine <[EMAIL PROTECTED]> wrote: >> >> 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. > > I completely agree and this is one reason why most of my contributions have > been with marketing and packaging. I was unaware of what needed to be > worked on and who was working on what tasks. > >> >> 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. > > I think this a great idea and we will finally be taking full advantage of > FITS. I will start to do the same with the marketing section of FITS so > that we can have this nice level of transparency through out the project. > >> >> 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. > > Will features be introduced as they are completed or at the end of the > sprint?
As they are completed, I do want to stick with the our rolling nature. > >> >> * 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 > > When do we want to have this larger meeting and how will this be held. Are > the top level drivers the same as the mentors? > >> >> 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 > > I request that if you do any planning discussion outside of FITS (email, > irc, in person, etc) you translate it as a comment in the FITS Issue. This > would allow more people to help add insight into an issue. > >> >> * 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 > > If you are getting busy with real life (work, family, friends, etc) please > let someone know. It is completely understandable for those things to come > up and by you report this it lets other people step up and help out while > you are busy. > >> >> * 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 > > I am willing to help mentor anyone that wants to work on task regarding > marketing, artwork or the website. > >> >> 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 >> >> >> -- >> Ken VanDine >> http://ken.vandine.org >> _______________________________________________ >> Foresight-devel mailing list >> Foresight-devel@lists.rpath.org >> http://lists.rpath.org/mailman/listinfo/foresight-devel > > > > -- > specialKevin > Kevin Harriss > http://www.foresightlinux.org > -- Ken VanDine http://ken.vandine.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
