1,285
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − + − + − + − − * Settle down patch submitting workflow [[User:Alsroot|alsroot]] 07:59, 25 October 2010 (EDT) − * Requirement to use [[Activity_Team/Sugar_Lint|sugar-lint]] (or so) in git pre-commit. [[User:Alsroot|alsroot]] 07:59, 25 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) Line 41:
Line 29: − + − * http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg17762.html+ − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Development Team/Meetings (view source)
Revision as of 18:40, 17 October 2017
, 18:40, 17 October 2017no edit summary
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>
* 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 Development team once held regular, bi-weekly meetings on Mondays at 14 UTC (9:00 EST) on irc://irc.freenode.net#sugar-meeting. See [http://lists.sugarlabs.org/listinfo/sugar-devel Sugar-devel], the Sugar and Activity developers' email list for current development discussions.
* 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.
* The Fedora development project for the OLPC XO and a Sugar distribution once held weekly meetings on Thursdays at 17:00 UTC (12:00 EST) on irc://irc.freenode.net#fedora-olpc. See [http://lists.laptop.org/listinfo/devel devel], The OLPC system hardware and software developers' email list for current discussions.
:(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.)
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]]
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>
</div>
==Upcoming Agenda==
== Upcoming Agenda ==
==About==
==About==
== Upcoming Meetings ==
== Upcoming Meetings ==
=== Possibly 30 October 2010 22:00 UTC ===
=== 24th October 2017 22:00 UTC ===
* irc://irc.freenode.net#sugar-meeting
* what we have been working on.
== Previous Meetings ==
== Previous Meetings ==
=== 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===
=== Wednesday 30 June 2010 13:00 UTC===