Added by Paul Cutler, last edited by Paul Cutler on Oct 05, 2007  (view change)

Labels:

release2 release2 Delete
development development Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Foresight Linux Developer Meeting Minutes and Notes, Oct. 3rd 2007

In attendance:
  • Paul Cutler
  • pscott (Paul Scott-Wilson)
  • Thilo Pfennig
  • doniphon (Antonio Meireles)
  • ogmaciel (Og Maciel)
  • kenvandine (Ken Vandine)
  • specialkevin (Kevin Harriss)
  • elliot (Elliot Peele)
  • mkj (Michael K. Johson)
  • stefw (Stephanie Watson)
  • gxti
  • jtate
  • int
Foresight Linux 2 Status

Doniphon:  FL2 is moving at full speed.  592 troves mook in a single rMake job against the current rpl:devel toolchain including groups.  GNOME has been bumped to latest 2.20 and will be committed tonight, with xorg following.

All packages need to be reviewed by hand to make sure functionality is not lost from FL:1 or rpl:devel.  Packages could lose functionality when built inside rMake due to insufficient buildReqs.  r.Configure arguments need to be reviewed as well.

Doniphon's goal is to have an "installable" 2-development (Alpha 1?) available by mid to end of next week.

Anaconda templates are conflicting with Conary, leading to a blocker.

Ken and Doniphon discuss creating groups (KDE & GNOME) before spinning ISOs.  One group = one single point of failure, but doniphon will focus on a GNOME group first.  Issue to be resolved at a later date.  This is a blocker to spin ISOs.

Fl:2 x86 / x86_64 needs tweaking, including web browsers, multimedia, Java (Iced tea).  Need to make a decision on 32 bit or 64 bit Firefox for inclusion in x86_64

Foresight Linux 2 Testing

FL:2 package testing process.  We need to form a QA sub-team to make a recommendation.  Currently it is fl2:devel -> fl2:qa -> fl:2.  We need one more final review of the QA and testing procedure for FL2.0.

mkj:  rpl creates a wiki of things to test and testers mark in progress or finished as they go.  Issues opened in JIRA when things are found broken

Discussion on testing:  use cases vs. having complete use at the recipe level.  FL:2 should not decrease any functionality from FL:1.  Need to make a list of what "should" work vs. what "must" work for Alpha / Beta testing.

Ken VanDine volunteers to create a wiki page and collecting use cases and how they apply in FL:1.

Team Structure

Agreed to focus on forming sub-teams for building and shipping Foresight Linux 2.0.  We will revisit teams after launch to determine what teams we need for maintaining FL 2.0.

Finalized Teams (* = Team lead)

Team Name Members Comment
QA / Bugs doniphon, SpecialKevin, pcutler, pscott, kenvandine *
Marketing / PR Specialkevin, pcutler *, stefw
Infrastructure doniphon, elliot, pscott (SMF forum), tpfennig (only helps with confluence, jira), pcutler
Documentation and HOWTOs pcutler *, stefw
Security smithj *, pcutler
 needs more helpers!
Release (Doniphon - PT, Kenvandine *, Elliot)
Development Doniphon *, Kenvandine, Ellio)
Internationalization & Licalization tpfennig, ogmaciel
Note:

Not discussed until after the meeting, but we will be adding three additional teams to focus on each desktop environment:

  • GNOME:  Ken VanDine
  • XFCE: Mark T (TBD)
  • KDE: Jtate or Int (TBD)
Infrastructure

Web infrastructure:  Agreed on Venus appliance for Planet functionality, SMF to create a forum, static website managed in Mercurial.  Wordpress-MU was agreed on, but in the short term for news / newsletter functionality.  Offering devs blogs will be post 2.0 release when things are a bit more settled.

Stefw and Pscott will partner on creating the SMF forum / appliance.

Theming & Marketing:  Biggest challenge facing the teams above to have a unified look and feel.  Need a web designer of sorts.

Sprints:

A sprint is a short term goal with a short term date.

Pick a given topic, managed in JIRA with an assigned task, and work on it for a week.  Wed-Tues.  JIRA needs to be used more, not just as a bug tracker, but for managing tasks as well.

Sprints will be assigned in JIRA, and (hopefully) agreed to the weekend before it starts.  We can then update JIRA and add to blogs / newsletter to solicit additional help.

Unresolved items from today's meeting:
  1. Finalize groups for FL2.0 vs. one big group before creating images
  2. QA / Testing process for packages need to be agreed and finalized post 2.0 launch
  3. Infrastructure team:  LDAP authentication for JIRA?
  4. Need a unified theme / design / branding for the different web applications such as SMF, website, WP-MU, etc
Other action items:
  1. Confluence / Wiki will be updated this weekend by doniphon
  2. Wiki pages will be need to be created for each team off the Developer space, including volunteers and tasks
  3. Ken will create wiki pages to start building out use cases