Difference between revisions of "Development Team/Meetings"

From Sugar Labs
Jump to navigation Jump to search
 
(79 intermediate revisions by 7 users not shown)
Line 5: Line 5:
 
</noinclude>
 
</noinclude>
  
−
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
+
== Development Team Meetings ==
−
* The Development team holds regular, bi-weekly meetings on Mondays at 14 UTC (9:00 EST) on irc://irc.freenode.net#sugar-meeting. Please add to the agenda below, and please join in with your ideas.
 
−
* The Fedora development project for the OLPC XO and a Sugar distribution holds weekly meetings on Thursdays at 17:00 UTC (12:00 EST) on irc://irc.freenode.net#fedora-olpc.
 
−
:(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.)
 
−
The Sugar Labs Meetings calendar is available in a variety of formats at these links: [[File:XML.gif|link=http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic]] [[File:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[File:HTML.gif|link=http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York]]
 
−
</div>
 
  
−
==Upcoming Agenda==
+
=== Who ===
  
−
==About==
+
The meeting is targeted to Sugar core and activity developers, but everyone interested is welcome to join. We try to open the development up a bit, make it more transparent and allow the community to participate easily.
 +
 
 +
=== Default Agenda ===
  
 
* Quick update about what we have been working on and eventually the problems we have run into.
 
* Quick update about what we have been working on and eventually the problems we have run into.
Line 21: Line 18:
 
* Help out new contributors to figure out where to start. Point out the tickets we need help with, discuss with them the implementation.
 
* Help out new contributors to figure out where to start. Point out the tickets we need help with, discuss with them the implementation.
  
−
====Who====
+
=== How to add to the agenda ===
−
 
 
−
The meeting is mainly targeted to Sugar core and activity developers, but everyone interested is welcome to join. It's primary purpose is to try to open the development up a bit, make it more transparent and allow the community to participate more easily. For when to join see 'When and Where'.
 
  
−
====How to add topics====
+
Add the topics that you want to discuss during the week to the upcoming meeting. They will be collected during the week and seny out in the meeting announcement on Tuesday morning.
−
You can add the topics that you want to discuss during the week to the topics section for the meeting. They will be collected during the week and send out in the meeting announcement on Thursday morning.
 
  
 
== Upcoming Meetings ==
 
== Upcoming Meetings ==
  
 +
=== Tuesday 21:00 UTC ===
  
 +
* what we have been working on,
  
 
== Previous Meetings ==
 
== Previous Meetings ==
 +
 +
=== 10th April 2018 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-10T21:00:09.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-10T21:00:09 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055264.html summary]
 +
 +
last planned update of this page, as no feedback was received.
 +
 +
=== 3rd April 2018 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-03T21:01:13.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-04-03T21:01:13 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-April/055259.html summary]
 +
 +
=== 27th March 2018 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-27T21:00:07.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-27T21:00:07 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-March/055249.html summary]
 +
 +
=== 20th March 2018 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-20T21:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-20T21:00:08 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-March/055189.html summary]
 +
 +
=== 13th March 2018 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-13T21:00:13.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-13T21:00:13 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-March/055158.html summary]
 +
 +
relevance canary; are you reading this?  the regular updates here will cease in another four weeks unless there is some feedback; updates will continue on sugar-devel@ mailing list.
 +
 +
=== 6th March 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-06T22:00:07.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-03-06T22:00:07 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-March/055143.html summary]
 +
 +
Topics:
 +
;what we have been working on:Music Blocks release, hosting.  Reviewing patches.  Replacement of Record activity.  Porting to  Six and Python 3.  Porting activities to GTK+ 3 and Sugargame 1.2.
 +
;port to Python 3 and Six:expectations discussed, Q&A session, see summary and log.
 +
;general business:continuous integration, see summary and log.
 +
 +
=== 27th February 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-27T22:00:09.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-27T22:00:09 log]
 +
[http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055112.html summary]
 +
 +
Topics:
 +
;what we have been working on:Bugs in Music Blocks, Speak, Memorize.  Porting activities to GTK+ 3 and Sugargame 1.2.
 +
;port to Python 3 and Six:plans made and discussed, see summary and log.
 +
;general business:see summary and log.
 +
 +
=== 20th February 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-20T22:00:16.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-20T22:00:16 log]
 +
 +
Topics:
 +
;what we have been working on:testing Sugar on Ubuntu 18.04, testing and design of Music Blocks.
 +
 +
=== 14th January 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-13T22:00:09.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-02-13T22:00:09 log]
 +
 +
Topics:
 +
;what we have been working on:quashing Music Blocks bugs, preparing tasks for GSoC, project mining, clean up activity metadata format, moved more of developer.sugarlabs.org over to GitHub.
 +
 +
=== 30th January 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-30T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-30T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:review patches, review activity NumRush, port Letters and Physics to Sugargame 1.2, a contributors page for web site, Music Blocks planet, preparing new release, pitch visualisation, Clock activity user documentation, and creating tasks for GSoC.
 +
 +
=== 16th January 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-16T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-16T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:fix startup delay in Sugargame, add ticking Clock, and a music blocks planet project moderation portal.
 +
;progress of GCI 2017:productive and enriching, last day today, opportunity for new activity maintainers to release contributed work.
 +
 +
=== 9th January 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-09T22:00:07.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-09T22:00:07 log]
 +
 +
Topics:
 +
;what we have been working on:patch reviews, patch tests, measure and clock activities, music blocks in browse, teaching humanitarian free and open source software.
 +
;progress of GCI 2017: GTK+ 3 conversions, documentation updates.
 +
 +
=== 2nd January 2018 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-02T22:33:17.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2018-01-02T22:33:17 log]
 +
 +
Topics:
 +
;what we have been working on:reviewing patches, updating translations,
 +
;progress of GCI 2017: GTK+ 3 conversions,
 +
 +
=== 19th December 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-19T22:00:40.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-19T22:00:40 log]
 +
 +
Topics:
 +
;what we have been working on:testing Sugar 0.112 on Fedora 18 and Ubuntu 18.04, answering questions on Sugar 0.112 release, a lot of bug fixes being reviewed.
 +
;progress of GCI 2017:students are starting to dig deeper, documentation for sugar-live-build has come together, some GTK+ 3 porting tasks coming up.
 +
 +
=== 12th December 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-12T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-12-12T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:Walter has been administering [[Google Code In 2017|GCI 2017]], and working on Music Blocks and Turtle Blocks. James has been reviewing pull requests, checking licensing, testing Sugar on Ubuntu 18.04 beta, releasing Speak-55 and Read-118.1, and fixed a Paint activity empty canvas.
 +
;progress of GCI 2017:Almost 400 students, how to make a pull request, some solid contributions, some new activities.
 +
;cross-platform development:There are broken JavaScript activities that don't run on Sugar desktop.  Contributions are being wasted, and opportunity lost.  We had a Cross-Platform environment.  We have attracted JavaScript Web developers instead of JavaScript Cross-Platform developers.  We need Cross-Platform developers to merge the diverged libraries, and apply Cross-Platform practices to both libraries and activities.
 +
 +
=== 5th December 2017 22:00 UTC ===
 +
 +
Only one developer was available, so the meeting did not happen.
 +
 +
=== 28th November 2017 22:00 UTC ===
 +
 +
Only one developer was available, so the meeting did not happen.
 +
 +
=== 21st November 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-21T22:00:17.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-21T22:00:17 log]
 +
 +
Topics:
 +
;what we have been working on:Abdul has been working on an activity for Sugarizer.  Walter has been working on Google Code-in preparation and released Music Blocks 2.2.  James has been testing Ubuntu 18.04 Bionic in a VM, Fedora 27 SoaS on Raspberry Pi, and plans to write guidance for pull requests by GCI contestants.
 +
 +
=== 14th November 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-14T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-14T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:About 308 GCI tasks have been defined privately by the mentors, Music Blocks source code has been prepared for GCI, Sugar Software Update has been tested; a rogue Browse-157.4 bundle was found, several GitHub issues cleaned in preparation for GCI.
 +
 +
=== 7th November 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-07T22:00:15.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-11-07T22:00:15 log]
 +
 +
Topics:
 +
;what we have been working on:preparing for GCI, merged several translation pull requests, began looking into why Sugar POT file is generated differently, released and tested Browse 201.3 native, reviewed Paraguay's build of sugar, reviewed Arch Linux packaging of Sugar, thinking of updating a beginners guide, merging www-sugar, and Music Blocks.
 +
 +
=== 31st October 2017 21:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-31T20:59:07.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-31T20:59:07 log]
 +
 +
Topics:
 +
;what we have been working on:nothing in particular.
 +
;how to encourage testing of Fedora packagers' work:Thomas and Frederick found fail-to-start problems in Fedora 27, as the Sugar and Browse packages had not been tested at all, so we all need to test the work of our downstream packagers, and help them where possible.
 +
 +
=== 24th October 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-24T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-24T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:updating [https://github.com/walterbender/musicblocks/tree/master/examples examples] and testing of Music Blocks, testing new WebKit GTK+ with Browse, looking for source code commits for the FindWords-3.1 activity, and releasing [https://github.com/godiard/music-keyboard-activity/commit/67b879d5a3f5b24ba1098086570e7bdb84d7a0da MusicKeyboard-11].
 +
 +
=== 17th October 2017 22:00 UTC ===
 +
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-17T22:00:08.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-10-17T22:00:08 log]
 +
 +
Topics:
 +
;what we have been working on:features in Music Blocks, assessing GTK+ 3 porting, preparing for and merging translations,
 +
;impact of GTK+ 2 removal in Fedora and Debian:GTK+ is a library, see [https://www.gtk.org/ GTK+] and [https://en.wikipedia.org/wiki/GTK%2B GTK+], GTK+ 3 is incompatible with GTK+ 2, many activities for Sugar depend on GTK+ 2, GTK+ 2 is scheduled for removal in Fedora 28 and in Debian Buster, removal already starting in Debian, bad user experience with Browse and activities.sugarlabs.org is non-starting activities, all Fructose activities are converted, Labyrinth is of interest to OLPC and has an upstream port, Record is of interest to OLPC and has an in-progress port at https://github.com/quozl/record-activity/tree/gtk3, Moon is of interest to OLPC and has a JavaScript port, GCI will have porting tasks.
 +
 +
=== 10th October 2017 22:00 UTC ===
 +
 +
Only one developer was available, so the meeting did not happen.
 +
 +
Topics:
 +
;post-release [[0.112]] review:no test reports received.
 +
;what we have been working on:new gst-plugins-espeak, contributors list, releasing, testing [[0.112]], font size in Terminal, bugs in gst-plugins-espeak.
 +
 +
Report was made [http://lists.sugarlabs.org/archive/sugar-devel/2017-October/054837.html by mail].
 +
 +
=== 3rd October 2017 22:00 UTC ===
 +
 +
Only one developer was available, so the meeting did not happen.
 +
 +
Topics:
 +
;progress of testing 0.111:going well, and a bootable build is available.
 +
;merging any translations:no new translations, so no need for merge.
 +
;readiness for 0.112:release notes are complete, nothing is blocking release on 9th October.
 +
;what we have been working on:Memorize and Speak activities do fail to start on Ubuntu 17.04 Artful due to default voice missing from espeak, since fixed in gst-plugins-espeak.  sugar-docs has been updated for using sugar-live-build as a development environment, and remove sugar-build.  The AbiWord fix for #4915 Write activity flicker has been accepted by Ubuntu and Debian, and has tested fine in those distributions.  Also on GitHub have been commits in embedded Music Blocks, embedded Turtle Blocks, Help, and ImageViewer.
 +
 +
Report was made [http://lists.sugarlabs.org/archive/sugar-devel/2017-October/054829.html by mail].
 +
 +
=== 26 September 2017 22:00 UTC ===
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-26T22:00:07.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-26T22:00:07 log]
 +
 +
Topics:
 +
;progress of testing 0.111:some testing is being done, but more testing would be helpful, see [[0.112#Testing|testing 0.111]],
 +
;merging latest translations:asked translators mailing list, no new translations made, strings for save-as feature are new, some Music Blocks strings changed too,
 +
;readiness for 0.112:some time before translations must be in per [[0.112/Roadmap|schedule]], release process well understood and should not take long, possibility of a test image,
 +
;what we have been working on: bug [https://bugs.sugarlabs.org/ticket/4915 #4915 ("Write redraws excessively - heats my lap")] the AbiWord flicker, a fix is available, but upstream wants it also fixed on Wayland, though Ubuntu [https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1574278 has taken it], applying the fix is straightfoward; release notes are to include Turtle Blocks porting, and therefore other activities (done, see [[0.112#Notes]]), Turtle Blocks 216 for upload (done), and a test image is nearly complete, which can be a replacement for sugar-build, see [[0.112#Testing|Sugar Live Build]].
 +
 +
=== 19 September 2017 21:00 UTC ===
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-19T21:01:38.html minutes]
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-19T21:01:38 log]
 +
 +
Topics:
 +
 +
;Release Manager: We ack'd James Cameron in his role as release manager for 0.112.
 +
;Community Standards: We reiterated the importance of civil behavior and the necessity to work with the community, not unilaterally. We also reviewed the mechanisms we use for pull requests, reviews, and merging.
 +
;0.112 release testing: We discussed [[0.112/Testing]]
 +
;Version numbering: We agreed to investigate the possibility of switching to 113 for the next release (a monotonic numbering system).
 +
;ALSOv3: We agreed to work with SCG to do the ground work necessary to get ALSOv3 launched.
 +
 +
=== 30 October 2010 22:00 UTC ===
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-30T22:06:36.html minutes],
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-10-30T22:06:36 log]
 +
 +
Not discussed:
 +
 +
* Settle down patch submitting workflow:
 +
** email based workflow as a primarily model (check other FOSS projects to gather all existed experience) [[User:Alsroot|alsroot]] 07:35, 27 October 2010 (EDT)
 +
** write an email-bot/trac-plugin to make an email<->trac sync. Will be useful, e.g., for non-developers who track bugs status and to let people know the current status in most convenient way. All emails, w/ ticket set, will be posted to bugs.sl.o and any comments(and patches) to bugs.sl.o, to tickets w/ previously sent patches, will be emailed. [[User:Alsroot|alsroot]] 07:35, 27 October 2010 (EDT)
 +
 +
* Requirement to use pylint/pep8 in git pre-commit:
 +
** [[Platform_Team/Sugar_Lint|sugar-lint]], because it is a standalone project and can be used as-is also, e.g., for activities (i.e., as unified lint tool within sugar doers) [[User:Alsroot|alsroot]] 07:39, 27 October 2010 (EDT)
 +
 +
* Increase a level of trust within core team, make patch reviewing workflow more clear:
 +
** Any committer, to a particular core project, might be a reviewer (we either should trust all these people or drop them from committer list) [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 +
** To accept ''regular'' (reviewer decides whether patches are regular or not, of course, better to discuss it with other committers if there are doubts) patches, only one reviewer is needed [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 +
** Non-regular patches should be formed in [[Features]]. These patches might take several tens of K. This is by design; that it is hard not only to develop, but also to review and it should involve several committers for a reasonable amount of time. [[User:Alsroot|alsroot]] 09:28, 25 October 2010 (EDT)
 +
** Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied [[User:Alsroot|alsroot]] 09:33, 25 October 2010 (EDT)
 +
** Purism is good but there is no need to achieve it by single patch, it might be changed in post-commit patches if second reviewer (e.g., looking to the patch thread on mailing list) found an issue in already commited code. [[User:Alsroot|alsroot]] 13:39, 25 October 2010 (EDT)
 +
 +
* officially dropping support for 0.86? (e.g. {{bug|1838}})
 +
** do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT)
 +
 +
* big (and small) ideas for 0.92  --[[User:Walter|Walter]] 13:17, 25 October 2010 (EDT)
 +
 +
* Support [[Platform_Team/Guide/Core_development|isolated]] start of glucose components. In that case, merge sugar-base to sugar-toolkit ([http://lists.sugarlabs.org/archive/sugar-devel/2010-October/028196.html patches] [yet] don't implement it but import sugar-base from sugar-toolkit) to have API that will be used as a single access point to sugar core functionality for activities. [[User:Alsroot|alsroot]] 08:12, 30 October 2010 (EDT)
 +
 +
=== Wednesday 30 June 2010 13:00 UTC===
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-06-30T09:01:00.html minutes],
 +
[http://meeting.sugarlabs.org/sugar-meeting/meetings/2010-06-30 log]
 +
* Introduction: the release cycle approach
 +
* Define the overall goal for 0.90
 +
* Review processes (review, Feature)
 +
* Open positions (development team, design team, testing team)
 +
 +
=== Monday 22 March 2010 14:00 UTC ===
 +
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100322_1010.html minutes], [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100322_1010.html log].
 +
* Welcome newcomers
 +
* 0.88 Release: hard code freeze, final release, 0.88.1
 +
 
=== Monday 8 March 2010 14:00 UTC ===
 
=== Monday 8 March 2010 14:00 UTC ===
 
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100308_0915.html minutes], [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100308_0915.html log].
 
[http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100308_0915.html minutes], [http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100308_0915.html log].
Line 54: Line 319:
 
* State of 0.88 release
 
* State of 0.88 release
  
 +
<div class="NavFrame collapsed"><div class="NavHead">
 +
 +
== 2009 Meetings ==
 +
</div><div class="NavContent">
 
=== Thursday 10 September 2009 14:00 UTC ===
 
=== Thursday 10 September 2009 14:00 UTC ===
  
Line 182: Line 451:
  
 
c) How long to support "old" versions of Sugar (Debian lenny might ship 0.82)
 
c) How long to support "old" versions of Sugar (Debian lenny might ship 0.82)
 +
</div></div>
 +
 +
<div class="NavFrame collapsed"><div class="NavHead">
  
 +
==2008 Meetings==
 +
</div><div class="NavContent">
 
===Thursday December 11 2008 - 14.00 (UTC) ===
 
===Thursday December 11 2008 - 14.00 (UTC) ===
 
====Logs ====
 
====Logs ====
Line 201: Line 475:
 
e) trac (add the needed milestones...)
 
e) trac (add the needed milestones...)
  
−
<div class="NavFrame collapsed"><div class="NavHead">
 
−
 
−
==2008 Meetings==
 
−
</div><div class="NavContent">
 
 
===Thursday November 13 2008 - 14.00 (UTC) ===
 
===Thursday November 13 2008 - 14.00 (UTC) ===
 
====Logs ====
 
====Logs ====

Latest revision as of 16:29, 10 April 2018

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


Development Team Meetings

Who

The meeting is targeted to Sugar core and activity developers, but everyone interested is welcome to join. We try to open the development up a bit, make it more transparent and allow the community to participate easily.

Default Agenda

  • Quick update about what we have been working on and eventually the problems we have run into.
  • Discussion about the implementation details of tickets we are planning to work on. Figure out how to split up the work and who should be owning the various parts.
  • Questions from activity authors about specific aspects of the platform and more in general on how to better integrate their activity in Sugar. Report about problems they run into.
  • Help out new contributors to figure out where to start. Point out the tickets we need help with, discuss with them the implementation.

How to add to the agenda

Add the topics that you want to discuss during the week to the upcoming meeting. They will be collected during the week and seny out in the meeting announcement on Tuesday morning.

Upcoming Meetings

Tuesday 21:00 UTC

  • what we have been working on,

Previous Meetings

10th April 2018 21:00 UTC

minutes log summary

last planned update of this page, as no feedback was received.

3rd April 2018 21:00 UTC

minutes log summary

27th March 2018 21:00 UTC

minutes log summary

20th March 2018 21:00 UTC

minutes log summary

13th March 2018 21:00 UTC

minutes log summary

relevance canary; are you reading this? the regular updates here will cease in another four weeks unless there is some feedback; updates will continue on sugar-devel@ mailing list.

6th March 2018 22:00 UTC

minutes log summary

Topics:

what we have been working on
Music Blocks release, hosting. Reviewing patches. Replacement of Record activity. Porting to Six and Python 3. Porting activities to GTK+ 3 and Sugargame 1.2.
port to Python 3 and Six
expectations discussed, Q&A session, see summary and log.
general business
continuous integration, see summary and log.

27th February 2018 22:00 UTC

minutes log summary

Topics:

what we have been working on
Bugs in Music Blocks, Speak, Memorize. Porting activities to GTK+ 3 and Sugargame 1.2.
port to Python 3 and Six
plans made and discussed, see summary and log.
general business
see summary and log.

20th February 2018 22:00 UTC

minutes log

Topics:

what we have been working on
testing Sugar on Ubuntu 18.04, testing and design of Music Blocks.

14th January 2018 22:00 UTC

minutes log

Topics:

what we have been working on
quashing Music Blocks bugs, preparing tasks for GSoC, project mining, clean up activity metadata format, moved more of developer.sugarlabs.org over to GitHub.

30th January 2018 22:00 UTC

minutes log

Topics:

what we have been working on
review patches, review activity NumRush, port Letters and Physics to Sugargame 1.2, a contributors page for web site, Music Blocks planet, preparing new release, pitch visualisation, Clock activity user documentation, and creating tasks for GSoC.

16th January 2018 22:00 UTC

minutes log

Topics:

what we have been working on
fix startup delay in Sugargame, add ticking Clock, and a music blocks planet project moderation portal.
progress of GCI 2017
productive and enriching, last day today, opportunity for new activity maintainers to release contributed work.

9th January 2018 22:00 UTC

minutes log

Topics:

what we have been working on
patch reviews, patch tests, measure and clock activities, music blocks in browse, teaching humanitarian free and open source software.
progress of GCI 2017
GTK+ 3 conversions, documentation updates.

2nd January 2018 22:00 UTC

minutes log

Topics:

what we have been working on
reviewing patches, updating translations,
progress of GCI 2017
GTK+ 3 conversions,

19th December 2017 22:00 UTC

minutes log

Topics:

what we have been working on
testing Sugar 0.112 on Fedora 18 and Ubuntu 18.04, answering questions on Sugar 0.112 release, a lot of bug fixes being reviewed.
progress of GCI 2017
students are starting to dig deeper, documentation for sugar-live-build has come together, some GTK+ 3 porting tasks coming up.

12th December 2017 22:00 UTC

minutes log

Topics:

what we have been working on
Walter has been administering GCI 2017, and working on Music Blocks and Turtle Blocks. James has been reviewing pull requests, checking licensing, testing Sugar on Ubuntu 18.04 beta, releasing Speak-55 and Read-118.1, and fixed a Paint activity empty canvas.
progress of GCI 2017
Almost 400 students, how to make a pull request, some solid contributions, some new activities.
cross-platform development
There are broken JavaScript activities that don't run on Sugar desktop. Contributions are being wasted, and opportunity lost. We had a Cross-Platform environment. We have attracted JavaScript Web developers instead of JavaScript Cross-Platform developers. We need Cross-Platform developers to merge the diverged libraries, and apply Cross-Platform practices to both libraries and activities.

5th December 2017 22:00 UTC

Only one developer was available, so the meeting did not happen.

28th November 2017 22:00 UTC

Only one developer was available, so the meeting did not happen.

21st November 2017 22:00 UTC

minutes log

Topics:

what we have been working on
Abdul has been working on an activity for Sugarizer. Walter has been working on Google Code-in preparation and released Music Blocks 2.2. James has been testing Ubuntu 18.04 Bionic in a VM, Fedora 27 SoaS on Raspberry Pi, and plans to write guidance for pull requests by GCI contestants.

14th November 2017 22:00 UTC

minutes log

Topics:

what we have been working on
About 308 GCI tasks have been defined privately by the mentors, Music Blocks source code has been prepared for GCI, Sugar Software Update has been tested; a rogue Browse-157.4 bundle was found, several GitHub issues cleaned in preparation for GCI.

7th November 2017 22:00 UTC

minutes log

Topics:

what we have been working on
preparing for GCI, merged several translation pull requests, began looking into why Sugar POT file is generated differently, released and tested Browse 201.3 native, reviewed Paraguay's build of sugar, reviewed Arch Linux packaging of Sugar, thinking of updating a beginners guide, merging www-sugar, and Music Blocks.

31st October 2017 21:00 UTC

minutes log

Topics:

what we have been working on
nothing in particular.
how to encourage testing of Fedora packagers' work
Thomas and Frederick found fail-to-start problems in Fedora 27, as the Sugar and Browse packages had not been tested at all, so we all need to test the work of our downstream packagers, and help them where possible.

24th October 2017 22:00 UTC

minutes log

Topics:

what we have been working on
updating examples and testing of Music Blocks, testing new WebKit GTK+ with Browse, looking for source code commits for the FindWords-3.1 activity, and releasing MusicKeyboard-11.

17th October 2017 22:00 UTC

minutes log

Topics:

what we have been working on
features in Music Blocks, assessing GTK+ 3 porting, preparing for and merging translations,
impact of GTK+ 2 removal in Fedora and Debian
GTK+ is a library, see GTK+ and GTK+, GTK+ 3 is incompatible with GTK+ 2, many activities for Sugar depend on GTK+ 2, GTK+ 2 is scheduled for removal in Fedora 28 and in Debian Buster, removal already starting in Debian, bad user experience with Browse and activities.sugarlabs.org is non-starting activities, all Fructose activities are converted, Labyrinth is of interest to OLPC and has an upstream port, Record is of interest to OLPC and has an in-progress port at https://github.com/quozl/record-activity/tree/gtk3, Moon is of interest to OLPC and has a JavaScript port, GCI will have porting tasks.

10th October 2017 22:00 UTC

Only one developer was available, so the meeting did not happen.

Topics:

post-release 0.112 review
no test reports received.
what we have been working on
new gst-plugins-espeak, contributors list, releasing, testing 0.112, font size in Terminal, bugs in gst-plugins-espeak.

Report was made by mail.

3rd October 2017 22:00 UTC

Only one developer was available, so the meeting did not happen.

Topics:

progress of testing 0.111
going well, and a bootable build is available.
merging any translations
no new translations, so no need for merge.
readiness for 0.112
release notes are complete, nothing is blocking release on 9th October.
what we have been working on
Memorize and Speak activities do fail to start on Ubuntu 17.04 Artful due to default voice missing from espeak, since fixed in gst-plugins-espeak. sugar-docs has been updated for using sugar-live-build as a development environment, and remove sugar-build. The AbiWord fix for #4915 Write activity flicker has been accepted by Ubuntu and Debian, and has tested fine in those distributions. Also on GitHub have been commits in embedded Music Blocks, embedded Turtle Blocks, Help, and ImageViewer.

Report was made by mail.

26 September 2017 22:00 UTC

minutes log

Topics:

progress of testing 0.111
some testing is being done, but more testing would be helpful, see testing 0.111,
merging latest translations
asked translators mailing list, no new translations made, strings for save-as feature are new, some Music Blocks strings changed too,
readiness for 0.112
some time before translations must be in per schedule, release process well understood and should not take long, possibility of a test image,
what we have been working on
bug #4915 ("Write redraws excessively - heats my lap") the AbiWord flicker, a fix is available, but upstream wants it also fixed on Wayland, though Ubuntu has taken it, applying the fix is straightfoward; release notes are to include Turtle Blocks porting, and therefore other activities (done, see 0.112#Notes), Turtle Blocks 216 for upload (done), and a test image is nearly complete, which can be a replacement for sugar-build, see Sugar Live Build.

19 September 2017 21:00 UTC

minutes log

Topics:

Release Manager
We ack'd James Cameron in his role as release manager for 0.112.
Community Standards
We reiterated the importance of civil behavior and the necessity to work with the community, not unilaterally. We also reviewed the mechanisms we use for pull requests, reviews, and merging.
0.112 release testing
We discussed 0.112/Testing
Version numbering
We agreed to investigate the possibility of switching to 113 for the next release (a monotonic numbering system).
ALSOv3
We agreed to work with SCG to do the ground work necessary to get ALSOv3 launched.

30 October 2010 22:00 UTC

minutes, log

Not discussed:

  • Settle down patch submitting workflow:
    • email based workflow as a primarily model (check other FOSS projects to gather all existed experience) alsroot 07:35, 27 October 2010 (EDT)
    • write an email-bot/trac-plugin to make an email<->trac sync. Will be useful, e.g., for non-developers who track bugs status and to let people know the current status in most convenient way. All emails, w/ ticket set, will be posted to bugs.sl.o and any comments(and patches) to bugs.sl.o, to tickets w/ previously sent patches, will be emailed. alsroot 07:35, 27 October 2010 (EDT)
  • Requirement to use pylint/pep8 in git pre-commit:
    • sugar-lint, because it is a standalone project and can be used as-is also, e.g., for activities (i.e., as unified lint tool within sugar doers) alsroot 07:39, 27 October 2010 (EDT)
  • Increase a level of trust within core team, make patch reviewing workflow more clear:
    • Any committer, to a particular core project, might be a reviewer (we either should trust all these people or drop them from committer list) alsroot 07:59, 25 October 2010 (EDT)
    • To accept regular (reviewer decides whether patches are regular or not, of course, better to discuss it with other committers if there are doubts) patches, only one reviewer is needed alsroot 07:59, 25 October 2010 (EDT)
    • Non-regular patches should be formed in Features. These patches might take several tens of K. This is by design; that it is hard not only to develop, but also to review and it should involve several committers for a reasonable amount of time. alsroot 09:28, 25 October 2010 (EDT)
    • Review process should not include debates about coding style, if coding style conforms to lint checks and Hacking Policy (if it has unequivocal statements, needs to be rechecked), it should be applied alsroot 09:33, 25 October 2010 (EDT)
    • Purism is good but there is no need to achieve it by single patch, it might be changed in post-commit patches if second reviewer (e.g., looking to the patch thread on mailing list) found an issue in already commited code. alsroot 13:39, 25 October 2010 (EDT)
  • officially dropping support for 0.86? (e.g. #1838)
    • do we need to discuss thing like that on Development Team meeting, is it a more appropriate task for Deployment and Platform teams? alsroot 07:59, 25 October 2010 (EDT)
  • big (and small) ideas for 0.92 --Walter 13:17, 25 October 2010 (EDT)
  • Support isolated start of glucose components. In that case, merge sugar-base to sugar-toolkit (patches [yet] don't implement it but import sugar-base from sugar-toolkit) to have API that will be used as a single access point to sugar core functionality for activities. alsroot 08:12, 30 October 2010 (EDT)

Wednesday 30 June 2010 13:00 UTC

minutes, log

  • Introduction: the release cycle approach
  • Define the overall goal for 0.90
  • Review processes (review, Feature)
  • Open positions (development team, design team, testing team)

Monday 22 March 2010 14:00 UTC

minutes, log.

  • Welcome newcomers
  • 0.88 Release: hard code freeze, final release, 0.88.1

Monday 8 March 2010 14:00 UTC

minutes, log.

  • backport SL#1787 to 0.86, push out + announce new release
  • 0.88 Release: bug database cleanup, code review, stabilization, etc

Monday 22 February 2010 14:00 UTC

minutes, log.

  • 0.88 Release: bug database cleanup, fix bugs, etc
  • Activity Team: Move to new toolbar

Monday 8 February 2010 14:00 UTC

Logs

logs

minutes

Topics

  • State of 0.88 release
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Development_Team/Meetings&oldid=101690"