Activity Team/Meetings

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

The Activities team will be holding regular bi-weekly meetings on Fridays at 17:00 UTC on irc.freenode.net (channel: #sugar-meeting). Please add to the agenda below and please join in with your ideas.

Hint: You can use an online time calculator to convert from UTC to your local time zone or back.

See IRC for information on getting there.

Next Meeting

Agenda

• Adopt activities.sugarlabs.org
  • Ask permission of activity authors to allow AT members to make releases.
    • the major concern is: w/o that we have less accessible/uptodate activities on aslo in comparing with soas, since packaging "trunk" activities for distros is a common practice, and in common, GNU/Linux distribution is separated from upstream in comparing with addons.mozilla.org (IMHO) which is more like an exhibition of authors' activities
    • Renovate idea of ActivityTeam Stamp of Approval and take care of these activities
    • "Activity Team" user on aslo
    • Create a special activityteam user on Gitorious?
      • we shouldn't confuse activities authors by intervening to development process alsroot 18:44, 9 March 2009 (UTC)
      • common(RO to trunk, but fork/merge) access and ask authors only for releasing permissions - incrementing versions(do not confuse users), releasing(maybe) from cloned repos alsroot 18:44, 9 March 2009 (UTC)
  • Sugar Platform
    • Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")
    • Blobs in activities on aslo
      • some blobs could be included to Sugar Platform
      • what to do with the others
        • if these blobs are activity specific(like C-library in Bounce, not like gst-pluigns-espeak in Speak) oblige authors(we couldn't admit activities that are not runnable on declared platforms) take care about all possible variants on chosen platform(like x86/x86_64 on Linux platform)?
        • add architecture to aslo platforms?
          • how it will look like if a kid decided download activity from aslo and had to choose the right choice between Applications(0.82, 0.84), Platforms(Linux, BSD, Mac), Architectures(x86, x86_64, ppc, etc.)?
  • aslo internals
    • Form editors/admins groups to support aslo's activities
    • Discuss aslo activity categories.

Friday Feburary 27 2009 - 12pm EST

Agenda

• Catch up on the past month's progress
• activities.sugarlabs.org discussion
  • Identify major issues that block usage by all activity maintainers and/or consumers.
  • Make a clear HOWTO about uploading a bundle, nominating it, etc. Could be a guide with screenshots or a screencast, etc (I think that David Farning is looking at this)
  • Set up a team of administrators and a team of editors. I guess a couple of people in each could be a good start.
• Status of activity migration + author outreach
• Review of the TODO list
• Distribution discussion
  • Minimum resolution supported by Sugar
  • Help system
• News from Tuesday's OLPC Deployment meeting.

Log

http://meeting.laptop.org/sugar-meeting.log.20090227_1200.html

I forgot to use #endmeeting, so this log contains quite a bit of additional unrelated discussion.

Past Meetings

Friday January 30 2009 - 3pm EST - Inaugural Meeting

This is the first ActivityTeam meeting, and all are welcome! Here's hoping for a big turnout and a productive discussion.

Please join the channel 15 minutes prior to the start of the meeting. The meeting will last about an hour.

If you would like to add an item to the agenda, please propose it on the talk page or discuss it with an ActivityTeam coordinator first.

Agenda

• Introduce members, discuss purpose and role of the team.
• Detail our progress thus far.
• Discuss the status of activity migration.
• Infrastructure
  • Status of addons.sugarlabs.org Remora port.
  • Can we have a commits list?
• Activity updates (User:Bernie)
• Propose activities to be featured & promoted to deployments.
• Overview of the TODO list. Try and get some tasks picked up.
• Discuss the possibility of an activity sprint February 7-8, 2009.
• Discuss time and frequency of future meetings & status update emails.

Log

• 30th January, 2009. Also discussed was Quiz Activity