Difference between revisions of "Activity Team/Meetings"

From Sugar Labs
Jump to navigation Jump to search
 
(42 intermediate revisions by 10 users not shown)
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}
+
<noinclude>{{TeamHeader|Activity Team}}</noinclude>
{{TeamHeader|ActivityTeam}}</noinclude>
 
 
__NOTOC__
 
__NOTOC__
<div style="font-size: 1.3em; background: #edfdd7; padding: 10px; border: 1px solid #cde7a8">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.
+
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Activity team will be holding regular bi-weekly meetings on Monday at 15:00 UTC on irc.freenode.net (channel: #sugar-meeting). Please add to the agenda below and please join in with your ideas. See [[IRC]] for information on getting there.
  
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back.
+
Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]
 +
 
 +
To convert UTC to your local time, use [http://www.timeanddate.com/worldclock/converter.html?hour=11&min=30&sec=0&p1=0&p2=43 this converter] or run:
 +
:{{Code|date -d '[current date] [time] UTC'}}
 +
:{{Code|date -d '2008-06-03 14:00 UTC'}}
 +
 
 +
The Sugar Labs Meetings calendar is available in a variety of formats at these links: <span class="plainlinks"> [http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic {{filepath:XML.gif}}] [http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics {{filepath:ICal.gif}}] [http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York {{filepath:HTML.gif}}].</span>
 
</div>
 
</div>
  
See [[IRC]] for information on getting there.
+
===Monday October 24th 2011 - 15:00 UTC===
 +
====Agenda====
 +
* Review short term Team [http://lists.sugarlabs.org/archive/iaep/2011-September/014077.html goals]
 +
* Reminder to try and reuse upstream strings where possible to improve and ease i18n/L10n ([http://lists.sugarlabs.org/archive/sugar-devel/2011-October/033817.html see cjl's email])
 +
* Resurrect 'sugar-love' tickets (Gonzalo)
 +
* ''add agenda items here''
 +
 
 +
===Monday October 10th 2011 - 15:00 UTC===
 +
====Agenda====
 +
* Identifying Activities in ASLO that require i18n and L10n setup.
 +
** Diff between ASLO and Pootle Honey / Fructose hosted activities.  [[User:Cjl|Cjl]] 19:26, 6 October 2011 (EDT)
 +
* Call for Activity maintainers to draft text on notable updates for 11.3.0 release notes  http://wiki.laptop.org/go/Release_notes/11.3.0 [[User:Cjl|Cjl]] 22:15, 6 October 2011 (EDT)
 +
* Review our Report (and plans) http://lists.sugarlabs.org/archive/iaep/2011-September/014077.html
 +
* Who is in the team? We need do plans according to who can work in it.
 +
 
 +
====Log====
 +
http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-10T15:16:32
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-10T15:16:32.html minutes]
 +
 
 +
===Friday June 26th 2009 - 17:00 UTC===
 +
====Agenda====
 +
* How to move forward with updating Activities via ASLO. Should at least be on roadmap to synchronise work and expectations.
 +
* Reduce redundant information on w.sl.o, w.lt.o and ASLO.  Factors to consider:
 +
** Expectations of existing user base.
 +
** Update mechanism at existing deployments.
 +
** Reduce overall confusion.
 +
** Reduce workload on Activity developers.
 +
** Scalability of solution.
 +
 
 +
====Log====
 +
http://meeting.sugarlabs.org/sugar-meeting.log.20090626_1305.html
 +
[http://meeting.sugarlabs.org/sugar-meeting.minutes.20090626_1305.html minutes]
  
==Next Meeting==
+
===Friday March 13th 2009 - 17:00 UTC===
 
====Agenda====
 
====Agenda====
*Adopt activities.sugarlabs.org  
+
* Activity Team coordinator announcement.
** Ask permission of activity authors to allow AT members to make releases.
+
* activities.sugarlabs.org
*** 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
+
** Take ownership of activities.sugarlabs.org.  The Activity Team will create a team of editors and admins to review and manage activity submissions.
*** Renovate idea of ActivityTeam Stamp of Approval and take care of these activities
+
** Ask permission of activity authors to allow AT members to make releases. Without the ability of AT members to make releases, we will have fewer working & up to date activities on ASLO compared with distributions like SoaS (since it's common for distributions to package "trunk" activities).  It's in everyone's interest to have the activities on ASLO be as up to date as possible.
*** [[ActivityTeam#.22Activity_Team.22_user_on_addons.sugarlabs.org|"Activity Team" user on aslo]]
+
** Reintroduce idea of Activity Team Stamp of Approval and take care of these activities.
*** Create a special activityteam user on Gitorious?
+
** Discuss activity categories.
**** maybe RO(anonymous) access is sufficient; in that case TA should test trunk code patch it(gitorous fork/merge-request) and release it(maybe from forked repo)
+
*** Introduce age range categories?  Which ranges?
** [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 Sugar Platform]
+
 
*** Use SoaS as a test platform for aslo activities(treat soas like a model of "Standard Sugar Platform")
+
* Activity Team adoption of orphaned activities.
*** Blobs in activities on aslo
+
** An [[Activity Team#.22Activity_Team.22_user_on_addons.sugarlabs.org|"Activity Team"]] user now exists on ASLO so that we can post activities to ASLO without creating a user account for a possibly unreachable author.
**** some blobs could be included to Sugar Platform
+
** We are considering also creating an activity Team user on Gitorious, which authors could give commit permission to in order to allow new releases to be made.  This user could also be used when forking orphaned activities.
**** what to do with the others
+
*** we shouldn't confuse activities authors by intervening to development process [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)
** aslo internals
+
*** 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 [[User:Alsroot|alsroot]] 18:44, 9 March 2009 (UTC)
*** Form editors/admins groups to support aslo's activities
+
 
*** Discuss aslo activity categories.
+
* [http://sugarlabs.org/wiki/index.php?title=User:Tomeu/Platform_0.84 The Sugar Platform]
 +
** Consdier adopting SoaS as the standard test platform for ASLO activities.  Assume that if SoaS works, other distributions will work as well.
 +
** Blobs in activities on ASLO.
 +
*** Some of these blobs could be packaged and included in the Sugar Platform (gst-pluigns-espeak in Speak).
 +
*** Others are truly activity specific (like C-libraries in Bounce and Colors). 
 +
**** We can oblige authors (by not approving non-conforming activities) to provide a standard set of variants which we determine.  For example, x86/x64 for Linux.  Another possibility is included standardized build scripts in the XO bundles and making a compiler suite part of the Sugar platform.
 +
**** Alternately, we can add architecture choices to the ASLO platform selection.
 +
***** Might be too complicated for kids to pick correctly.
 +
***** Also requires authors to release multiple .xo bundles and set up cross-compilation.
 +
***** 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.)?
 +
 
 +
* GSoC 2009
 +
** SugarLabs is currently not planning to support activity development projects for GSoC 2009.  Does the Activity Team want to encourage them to change this policy, or should we work under OLPC instead?
 +
 
 +
====Log====
 +
http://meeting.laptop.org/sugar-meeting.log.20090313_1301.html
  
 
===Friday Feburary 27 2009 - 12pm EST ===
 
===Friday Feburary 27 2009 - 12pm EST ===
Line 47: Line 98:
 
==Past Meetings==
 
==Past Meetings==
 
===Friday January 30 2009 - 3pm EST - Inaugural Meeting ===
 
===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.
+
'''This is the first Activity Team 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.
 
''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/Contacts#Coordinators|ActivityTeam coordinator]] first.
+
If you would like to add an item to the agenda, please propose it on the talk page or discuss it with an [[Activity Team/Contacts#Coordinators|Activity Team coordinator]] first.
  
 
====Agenda====
 
====Agenda====
Line 58: Line 109:
 
* Discuss the status of activity migration.
 
* Discuss the status of activity migration.
 
* Infrastructure
 
* Infrastructure
** Status of addons.sugarlabs.org Remora port.
+
** Status of activities.sugarlabs.org Remora port.
 
** Can we have a commits list?
 
** Can we have a commits list?
 
* Activity updates ([[User:Bernie]])
 
* Activity updates ([[User:Bernie]])
Line 69: Line 120:
 
* [http://meeting.laptop.org/sugar-meeting.log.20090130_1441.html 30th January, 2009]. Also discussed was [http://sugarlabs.org/go/Activities/Quiz Quiz Activity]
 
* [http://meeting.laptop.org/sugar-meeting.log.20090130_1441.html 30th January, 2009]. Also discussed was [http://sugarlabs.org/go/Activities/Quiz Quiz Activity]
  
[[Category:Activity]]
+
[[Category:Activity Team]]
 
[[Category:Meetings]]
 
[[Category:Meetings]]

Latest revision as of 07:38, 24 October 2011

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

The Activity team will be holding regular bi-weekly meetings on Monday at 15:00 UTC on irc.freenode.net (channel: #sugar-meeting). Please add to the agenda below and please join in with your ideas. See IRC for information on getting there.

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

To convert UTC to your local time, use this converter or run:

date -d '[current date] [time] UTC'
date -d '2008-06-03 14:00 UTC'

The Sugar Labs Meetings calendar is available in a variety of formats at these links: XML.gif ICal.gif HTML.gif.

Monday October 24th 2011 - 15:00 UTC

Agenda

  • Review short term Team goals
  • Reminder to try and reuse upstream strings where possible to improve and ease i18n/L10n (see cjl's email)
  • Resurrect 'sugar-love' tickets (Gonzalo)
  • add agenda items here

Monday October 10th 2011 - 15:00 UTC

Agenda

Log

http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-10-10T15:16:32 minutes

Friday June 26th 2009 - 17:00 UTC

Agenda

  • How to move forward with updating Activities via ASLO. Should at least be on roadmap to synchronise work and expectations.
  • Reduce redundant information on w.sl.o, w.lt.o and ASLO. Factors to consider:
    • Expectations of existing user base.
    • Update mechanism at existing deployments.
    • Reduce overall confusion.
    • Reduce workload on Activity developers.
    • Scalability of solution.

Log

http://meeting.sugarlabs.org/sugar-meeting.log.20090626_1305.html minutes

Friday March 13th 2009 - 17:00 UTC

Agenda

  • Activity Team coordinator announcement.
  • activities.sugarlabs.org
    • Take ownership of activities.sugarlabs.org. The Activity Team will create a team of editors and admins to review and manage activity submissions.
    • Ask permission of activity authors to allow AT members to make releases. Without the ability of AT members to make releases, we will have fewer working & up to date activities on ASLO compared with distributions like SoaS (since it's common for distributions to package "trunk" activities). It's in everyone's interest to have the activities on ASLO be as up to date as possible.
    • Reintroduce idea of Activity Team Stamp of Approval and take care of these activities.
    • Discuss activity categories.
      • Introduce age range categories? Which ranges?
  • Activity Team adoption of orphaned activities.
    • An "Activity Team" user now exists on ASLO so that we can post activities to ASLO without creating a user account for a possibly unreachable author.
    • We are considering also creating an activity Team user on Gitorious, which authors could give commit permission to in order to allow new releases to be made. This user could also be used when forking orphaned activities.
      • 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)
  • The Sugar Platform
    • Consdier adopting SoaS as the standard test platform for ASLO activities. Assume that if SoaS works, other distributions will work as well.
    • Blobs in activities on ASLO.
      • Some of these blobs could be packaged and included in the Sugar Platform (gst-pluigns-espeak in Speak).
      • Others are truly activity specific (like C-libraries in Bounce and Colors).
        • We can oblige authors (by not approving non-conforming activities) to provide a standard set of variants which we determine. For example, x86/x64 for Linux. Another possibility is included standardized build scripts in the XO bundles and making a compiler suite part of the Sugar platform.
        • Alternately, we can add architecture choices to the ASLO platform selection.
          • Might be too complicated for kids to pick correctly.
          • Also requires authors to release multiple .xo bundles and set up cross-compilation.
          • 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.)?
  • GSoC 2009
    • SugarLabs is currently not planning to support activity development projects for GSoC 2009. Does the Activity Team want to encourage them to change this policy, or should we work under OLPC instead?

Log

http://meeting.laptop.org/sugar-meeting.log.20090313_1301.html

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 Activity Team 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 Activity Team 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 activities.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