Agenda:

• Announcements
• Proposed members/developers
• Proposed Topics
  1. Membership renewals
  2. Toolchain update
  3. FITS and workflow
  4. Tasks and roles
  5. Reschedule Council meetings
  6. Set up ISO mirrors
  7. Empathy vs Pidgin
  8. Infrastructure overview
• Next weeks agenda

Announcements:

• (Og Maciel) pscott has fixed the web frontend for our Mercurial repositories which can now be accessed via hg.foresightlinux.org as well as the secondary www.foresightlinux.org/hg address.
  - pscott noted that he is keeping an eye out for 404 errors in the logs.
• (Og Maciel) Hostmasks for all approved developers and members have been created.
• (Og Maciel) The new website based on Word Press is now published! I stumbled on a few permission issues initially due to the fact that (apparently) pages created by an admin cannot be edited by anyone else. I ended up creating an editor role account for me and assigned all but one existing pages to this user. I have created editor and admin accounts for the following users:
  • Admins: OgMaciel, doniphon, pcutler and pscott
  • Editors: afranke, ermo and TForsman

  Everyone is encouraged to lend a hand with getting the new site vetted

• (Og Maciel) Minutes for last week’s Council meeting were published to the new web site as a blog post instead of placed in the wiki. This is the first time we do it this way and I’d be very interested in what people thing. I feel that people can send their comments or any corrections as a comment and we can edit. Also, as only people with accounts in the web site can edit posts, it will help us mantain the validity of official announcements.
• (Og Maciel) The process of getting the new web site up and running involved the migration (as in conary migrate) of the existing server to the Lamp Appliance repository, all blessed by doniphon who was around to advise me.
  - Og Maciel had to setup MySQL with a password for the root user, which he will make available to the council later.

Proposed Topics:

1. Membership renewals (TForsman)
   • TForsman renewed as developer by quorum. (pcutler, doniphon, OgMaciel)
   • (OgMaciel) Don’t we need a paragraph on renewal on either of:

     http://wiki.foresightlinux.org/display/community/Home

     http://wiki.foresightlinux.org/display/community/Becoming+a+Member

     http://wiki.foresightlinux.org/display/community/Becoming+a+Developer

   • Links from website to wiki on membership needs to be checked
   • The onus is on the Council to send out membership expiration notices
   • Any (well behaved member/developer who re-applies on their own is automatically accepted?
2. Toolchain progress (doniphon)
   • doniphon was happy to report that the latest toolchain build completed with no errors.
   • Testing of the new toolchain still remains.
   • Discuss toolchain and in particular the issue of how to build the x86 flavour (sse vs. sse2 re. Athlon XP) on list – see FL-1437
3. FITS and workflow
   • Ongoing, draft by doniphon sent to pscott
   • Recommend that a draft be circulated on the -devel list for transparency?
4. Tasks and roles
   • Not started yet. The Council will get this going.
   • pscott and doniphon suggested that this meshes with FITS and workflow
5. Reschedule meetings (MarkT)
   • MarkT cannot attend Council meetings on Fridays, which is inconvenient considering that he is a member of the Council
   • The Council will work on finding a more suitable time for the meeting
   • Next meeting is tentatively scheduled for July 14th
6. Set up ISO mirrors (Ken)
   • The monkey was thrown around and no resolution was made
   • This needs to be done, preferrably yesterday. Any takers?
7. Empathy vs. Pidgin (Ken)
   • Ken will announce it on -devel when he’s got Empathy ready for testing
8. Infrastructure documentation (ermo, IT-83)
   • ermo has documented MLs and examined DNS records. He will update http://wiki.foresightlinux.org/display/teams/Foresight+Infrastructure as appropriate
   • Discussion deferred to next meeting

Agenda:

• Announcements
• Last meeting overview
• Proposed topics
  1. Future foresight version
  2. Current Foresight version (2.1.x series)
  3. Promote WP site to official site location
  4. Need to update Confluence
  5. FITS system accounts and organization
  6. Derive our Identity
  7. Who manages access to infrastructure?
  8. Who do you talk to about getting issues on the council agenda?
  9. Deferred agenda points
• Proposed members/developers
• Next Week’s Agenda

Announcements

• New hostmaks (cloaks) have been created for all new members and developers.. (OgMaciel)
• Paul and I had a nice chat yesterday via Skype and have agreed on several topics related to how to organize and steer the community. More to come. (OgMaciel)

Proposed members/developers

• None.

Proposed Topics

1. Future foresight version
   • doniphon is not yet ready to announce 3.x – the ideas for workflow and creation of herds/teams for redundancy and parallel development need more time to coalesce. For now, the ball is in doniphon’s court.
   • doniphon is still wrestling with the new gcc-4.4.0. It crossbuilds (x86 -> x86_64 and x86_64 -> x86) but it does not build ‘natively’ (x86 -> x86 or x86_64 -> x86_64).
   • If anyone wants to try their hand at fixing the toolchain, they can get in touch with doniphon, who mentioned that the new toolchain is in a (non-public) repo at http://www.rpath.org/web/project/foreplay/. Access and rMake contexts will be granted to anyone willing to actually try to build and understand it. Recipes are well commented for a change.
2. Current Foresight version (2.1.x series)
   • doniphon proposed that we focus on feature freeze and testing packages for the 2.1.2 release.
   • doniphon needs volunteers to help clean up old/dead/broken packages and cross reference with groups so that packages move to -qa properly.
   • Og Maciel and doniphon will work on a plan for how to cut this and announce sprints as appropriate.
   • doniphon added that we should do our best to support current users, but that main efforts should go into enriching the developer base.  This in particular includes developing documentation, so that new developers can jump in and get started in relatively short order.
3. Promote WP site to official site location
   • It was agreed to promote the new WP site to the official site location. Og Maciel will handle this.
   • The council will have admin rights to the site.
   • Og Maciel volunteered to be editor and pcutler will assist him as time permits.
   • ermo, afranke, TForsman and perhaps Stephanie ‘stef’ Watson (we need to ask her) will help move content over.
4. Need to update Confluence
   • Og Maciel talked to gxti in private about the benefits we will see by upgrading the Confluence wiki to a newer version and gxti will look at this over the weekend. We have two issues filed against the wiki – one by pcutler (IT-60) that involves a bug where pasting content drops the formatting and one (IT-77) where Confluence doesn’t handle Chinese characters.
   • From the release notes alone, it appears that upgrading Confluence will both fix security issues, affect performance positively, improve the user experience and allow editing directly in OpenOffice via the office connector.
5. FITS system accounts and organization
   • pscott, doniphon and ermo will work on this (IT-29). Additionally, ermo will be granted admin permissions in FITS.
   • During the discussion, pcutler proposed a team lead type for QA work and that everyone should be responsible for triaging bugs. He also suggested regularly scheduled QA sessions. pscott mentioned that it could be helpful to have a group of users who had triage rights. Doniphon mentioned that he’d like to work on the group/workflow issue as well as it ties into his new workflow and metadata plans for 3.x.
   • In particular, pcutler proposed that the above process should be given a fixed amount of time (on the order of 3-6 months) in terms of putting down a roadmap on how to grow the developer base of foresight.
   • Og has talked to gxti in private, who has promised to look into updating JIRA (the FITS platform) to the newest version. ermo will help Og Maciel drive this.
6. Derive our Identity
   • There was general consensus in the meeting that we need a little more time for this. pcutler suggested that we let it simmer on the ML for a little while yet, until around June 30th (setting a deadline primarily to drive it forward)
7. Who manages access to infrastructure?
   • Currently, it’s been mostly the council (doniphon, ken, pcutler).
   • Og Maciel would like to see a definition of roles – what is a member? A developer?
   • doniphon would like to avoid too much red tape, but would still like to work on workflow tuning. It is clear that this needs some careful thought if on one hand we are to avoid bottlenecks and on the other avoid too many chefs in the kitchen.
   • Discussion ensued, with pcutler noting that we need to figure out what we have, before we figure out what we want. He suggested that we need to document the infrastructure that Foresight currently has as well as who has access to it.
   • ermo will drive the effort to document the current infrastructure. This will be documented in the open on the wiki to encourage accountability per doniphon’s sentiment.
   • pcutler, doniphon and Og Maciel will have a chat about how to define tasks and roles. It should be noted that this ties into the FITS workflow issue discussed above. It will also be discussed who can grant access to resources.
8. Who do you talk to about getting issues on the council agenda?
   • Current practice is for Og Maciel or Paul to send out an announcement on the ML and have a wiki page with the agenda and time+date for meeting.
9. Deferred agenda points
   • The deferred agenda points from last weeks meeting primarily concern workflow improvements, which are adressed implicitly above.
   • TForsman will drive a cleanup of current/retired Foresight developers and present his findings next week.