Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
Sure I've done. The roadmap seems compatible with the current status of the project. Plus, this feature has a very small impact on the Sugar source code (mainly in apisocket.py). Lionel. 2014-07-25 15:41 GMT+02:00 Martin Abente : > Thanks Lionel and Puneet! > > BTW, have you checked the latest draft for the roadmap [1]? > > Refs: > 1. http://wiki.sugarlabs.org/go/0.104/Roadmap > > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
Thanks Lionel and Puneet! BTW, have you checked the latest draft for the roadmap [1]? Refs: 1. http://wiki.sugarlabs.org/go/0.104/Roadmap On Fri, Jul 25, 2014 at 6:54 AM, Lionel Laské wrote: > Hi all, > > As decided to the meeting, Puneet has wrote a new page for the Cordova > container Feature that we could include in 0.104. > You could find this new page it here: > http://wiki.sugarlabs.org/go/Features/Cordova_Container_for_Sugar > Thanks to Puneet for the job. > > Lionel > > > > 2014-07-24 13:36 GMT+02:00 Gonzalo Odiard : > > >> On Thu, Jul 24, 2014 at 12:59 AM, Ignacio Rodríguez >> wrote: >> >>> Just thinking, we need to choice the backgrounds from the contest and >>> package it for new sugar. >>> >>> >> Yes. We are waiting for the judges to select the images. >> Manuel Quiñones (manuq) is who coordinate that. >> >> >> >>> btw, would be good if we can have animated backgrounds, like gifs. >>> >>> >> That would increase the battery consumption a lot :( >> >> Gonzalo >> >> >> >>> >>> Ignacio Rodríguez >>> +598 91 686 835 >>> nachoe...@gmail.com >>> >>> >>> 2014-07-22 16:04 GMT-05:00 Martin Abente >> >: >>> Hello everyone, Some updates: On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < martin.abente.lah...@gmail.com> wrote: > Hello everyone, > > This is a summary of the topics we discussed in our first development > meeting. Logs can be found here [1]. > > *Topic #1: What should we do for 0.104?* > >- Focus on core ideas: >- Fix or re-work collaboration? Cover web activities integration. > - Make Sugar more customizable? Get rid of control panel by > converting sections into applications. Make sugar itself modifiable > like > activities. > - Make student assessment part of the sugar experience? Think > of ways in which all these statistics gathering efforts can become > part of > this. > > >- Performance enhancements: >- Make Sugar more responsive? Starting by the journal. > - Make activities launch time faster? Moving common bits to > sugar-toolkit, ie., text-to-speech. > > >- Cover other classroom needs: >- Printing in Sugar? > - Integrate screen sharing in Sugar? > > These are initial suggestions, we all agreed that collaboration and > performance should be prioritized. > > > *Topic #2: How do we do it?* > >- Keep the current structure for phases and deadlines, ie., [2]. >- Keep the 6 months release schedules. >- Find a way to re-sync with Gnome [3] and Fedora [4], so we can >achieve the previous item. > > This is a tentative Roadmap for 0.104: http://wiki.sugarlabs.org/go/0.104/Roadmap . Please read it, think about it, and sent me your feedback. > >- >- Have regular development meetings. Each 2 weeks? Each month? >- Have at least one code sprint for each release, ie., SF meeting >in Oct/14, and UY youth summit in Sept/14. >- Request for former Sugar developers guidance. >- Share design team responsibilities among all of us. >- Document maintainers and responsibilities. > > *Topic #3: What are the Infrastructure needs?* > >- *Bring Pootle back to life*! Call for a special meeting >regarding this. > > Today (22 /04/2014), we had a meeting between gonzalo, cjl, icarito, bernie and me. Summary: (a) bernie is going to update newpootle machine, and (b) I am going to research a bit about setting a new Pootle instance from scratch, to understand what would be best path to follow. > >- >- Move activities repositories to github? > > Gonzalo is going to make an inventory on activities and repositories. > >- Set up a discourse instance (GSoC project)? > > > Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit > for joining and contributing to the meeting! > > Saludos, > tch. > > *Refs:* > >1. > > http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html >2. http://wiki.sugarlabs.org/go/0.100/Roadmap >3. https://wiki.gnome.org/ThreePointThirteen >4. http://fedoraproject.org/wiki/Releases/21/Schedule > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel >>> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Software for children learning >> > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
Hi all, As decided to the meeting, Puneet has wrote a new page for the Cordova container Feature that we could include in 0.104. You could find this new page it here: http://wiki.sugarlabs.org/go/Features/Cordova_Container_for_Sugar Thanks to Puneet for the job. Lionel 2014-07-24 13:36 GMT+02:00 Gonzalo Odiard : > > On Thu, Jul 24, 2014 at 12:59 AM, Ignacio Rodríguez > wrote: > >> Just thinking, we need to choice the backgrounds from the contest and >> package it for new sugar. >> >> > Yes. We are waiting for the judges to select the images. > Manuel Quiñones (manuq) is who coordinate that. > > > >> btw, would be good if we can have animated backgrounds, like gifs. >> >> > That would increase the battery consumption a lot :( > > Gonzalo > > > >> >> Ignacio Rodríguez >> +598 91 686 835 >> nachoe...@gmail.com >> >> >> 2014-07-22 16:04 GMT-05:00 Martin Abente >> : >> >>> Hello everyone, >>> >>> Some updates: >>> >>> On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < >>> martin.abente.lah...@gmail.com> wrote: >>> Hello everyone, This is a summary of the topics we discussed in our first development meeting. Logs can be found here [1]. *Topic #1: What should we do for 0.104?* - Focus on core ideas: - Fix or re-work collaboration? Cover web activities integration. - Make Sugar more customizable? Get rid of control panel by converting sections into applications. Make sugar itself modifiable like activities. - Make student assessment part of the sugar experience? Think of ways in which all these statistics gathering efforts can become part of this. - Performance enhancements: - Make Sugar more responsive? Starting by the journal. - Make activities launch time faster? Moving common bits to sugar-toolkit, ie., text-to-speech. - Cover other classroom needs: - Printing in Sugar? - Integrate screen sharing in Sugar? These are initial suggestions, we all agreed that collaboration and performance should be prioritized. *Topic #2: How do we do it?* - Keep the current structure for phases and deadlines, ie., [2]. - Keep the 6 months release schedules. - Find a way to re-sync with Gnome [3] and Fedora [4], so we can achieve the previous item. >>> This is a tentative Roadmap for 0.104: >>> http://wiki.sugarlabs.org/go/0.104/Roadmap . Please read it, think >>> about it, and sent me your feedback. >>> >>> - - Have regular development meetings. Each 2 weeks? Each month? - Have at least one code sprint for each release, ie., SF meeting in Oct/14, and UY youth summit in Sept/14. - Request for former Sugar developers guidance. - Share design team responsibilities among all of us. - Document maintainers and responsibilities. *Topic #3: What are the Infrastructure needs?* - *Bring Pootle back to life*! Call for a special meeting regarding this. >>> Today (22 /04/2014), we had a meeting between gonzalo, cjl, icarito, >>> bernie and me. Summary: (a) bernie is going to update newpootle machine, >>> and (b) I am going to research a bit about setting a new Pootle instance >>> from scratch, to understand what would be best path to follow. >>> >>> - - Move activities repositories to github? >>> Gonzalo is going to make an inventory on activities and repositories. >>> - Set up a discourse instance (GSoC project)? Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for joining and contributing to the meeting! Saludos, tch. *Refs:* 1. http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html 2. http://wiki.sugarlabs.org/go/0.100/Roadmap 3. https://wiki.gnome.org/ThreePointThirteen 4. http://fedoraproject.org/wiki/Releases/21/Schedule >>> >>> ___ >>> Sugar-devel mailing list >>> Sugar-devel@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/sugar-devel >>> >>> >> > > > -- > Gonzalo Odiard > > SugarLabs - Software for children learning > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
On Thu, Jul 24, 2014 at 12:59 AM, Ignacio Rodríguez wrote: > Just thinking, we need to choice the backgrounds from the contest and > package it for new sugar. > > Yes. We are waiting for the judges to select the images. Manuel Quiñones (manuq) is who coordinate that. > btw, would be good if we can have animated backgrounds, like gifs. > > That would increase the battery consumption a lot :( Gonzalo > > Ignacio Rodríguez > +598 91 686 835 > nachoe...@gmail.com > > > 2014-07-22 16:04 GMT-05:00 Martin Abente : > >> Hello everyone, >> >> Some updates: >> >> On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < >> martin.abente.lah...@gmail.com> wrote: >> >>> Hello everyone, >>> >>> This is a summary of the topics we discussed in our first development >>> meeting. Logs can be found here [1]. >>> >>> *Topic #1: What should we do for 0.104?* >>> >>>- Focus on core ideas: >>>- Fix or re-work collaboration? Cover web activities integration. >>> - Make Sugar more customizable? Get rid of control panel by >>> converting sections into applications. Make sugar itself modifiable >>> like >>> activities. >>> - Make student assessment part of the sugar experience? Think of >>> ways in which all these statistics gathering efforts can become part >>> of >>> this. >>> >>> >>>- Performance enhancements: >>>- Make Sugar more responsive? Starting by the journal. >>> - Make activities launch time faster? Moving common bits to >>> sugar-toolkit, ie., text-to-speech. >>> >>> >>>- Cover other classroom needs: >>>- Printing in Sugar? >>> - Integrate screen sharing in Sugar? >>> >>> These are initial suggestions, we all agreed that collaboration and >>> performance should be prioritized. >>> >>> >>> *Topic #2: How do we do it?* >>> >>>- Keep the current structure for phases and deadlines, ie., [2]. >>>- Keep the 6 months release schedules. >>>- Find a way to re-sync with Gnome [3] and Fedora [4], so we can >>>achieve the previous item. >>> >>> >> This is a tentative Roadmap for 0.104: >> http://wiki.sugarlabs.org/go/0.104/Roadmap . Please read it, think about >> it, and sent me your feedback. >> >> >>> >>>- >>>- Have regular development meetings. Each 2 weeks? Each month? >>>- Have at least one code sprint for each release, ie., SF meeting >>>in Oct/14, and UY youth summit in Sept/14. >>>- Request for former Sugar developers guidance. >>>- Share design team responsibilities among all of us. >>>- Document maintainers and responsibilities. >>> >>> *Topic #3: What are the Infrastructure needs?* >>> >>>- *Bring Pootle back to life*! Call for a special meeting regarding >>>this. >>> >>> >> Today (22 /04/2014), we had a meeting between gonzalo, cjl, icarito, >> bernie and me. Summary: (a) bernie is going to update newpootle machine, >> and (b) I am going to research a bit about setting a new Pootle instance >> from scratch, to understand what would be best path to follow. >> >> >>> >>>- >>>- Move activities repositories to github? >>> >>> >> Gonzalo is going to make an inventory on activities and repositories. >> >>> >>>- Set up a discourse instance (GSoC project)? >>> >>> >>> Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit >>> for joining and contributing to the meeting! >>> >>> Saludos, >>> tch. >>> >>> *Refs:* >>> >>>1. >>> >>> http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html >>>2. http://wiki.sugarlabs.org/go/0.100/Roadmap >>>3. https://wiki.gnome.org/ThreePointThirteen >>>4. http://fedoraproject.org/wiki/Releases/21/Schedule >>> >>> >>> >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > -- Gonzalo Odiard SugarLabs - Software for children learning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
On Wed, Jul 23, 2014 at 10:59:13PM -0500, Ignacio Rodríguez wrote: > Just thinking, we need to choice the backgrounds from the contest > and package it for new sugar. That would be good. > btw, would be good if we can have animated backgrounds, like gifs. I can see that would be good for coal miners and other sources of electrical energy production. ;-) -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
Just thinking, we need to choice the backgrounds from the contest and package it for new sugar. btw, would be good if we can have animated backgrounds, like gifs. Ignacio Rodríguez +598 91 686 835 nachoe...@gmail.com 2014-07-22 16:04 GMT-05:00 Martin Abente : > Hello everyone, > > Some updates: > > On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < > martin.abente.lah...@gmail.com> wrote: > >> Hello everyone, >> >> This is a summary of the topics we discussed in our first development >> meeting. Logs can be found here [1]. >> >> *Topic #1: What should we do for 0.104?* >> >>- Focus on core ideas: >>- Fix or re-work collaboration? Cover web activities integration. >> - Make Sugar more customizable? Get rid of control panel by >> converting sections into applications. Make sugar itself modifiable >> like >> activities. >> - Make student assessment part of the sugar experience? Think of >> ways in which all these statistics gathering efforts can become part of >> this. >> >> >>- Performance enhancements: >>- Make Sugar more responsive? Starting by the journal. >> - Make activities launch time faster? Moving common bits to >> sugar-toolkit, ie., text-to-speech. >> >> >>- Cover other classroom needs: >>- Printing in Sugar? >> - Integrate screen sharing in Sugar? >> >> These are initial suggestions, we all agreed that collaboration and >> performance should be prioritized. >> >> >> *Topic #2: How do we do it?* >> >>- Keep the current structure for phases and deadlines, ie., [2]. >>- Keep the 6 months release schedules. >>- Find a way to re-sync with Gnome [3] and Fedora [4], so we can >>achieve the previous item. >> >> > This is a tentative Roadmap for 0.104: > http://wiki.sugarlabs.org/go/0.104/Roadmap . Please read it, think about > it, and sent me your feedback. > > >> >>- >>- Have regular development meetings. Each 2 weeks? Each month? >>- Have at least one code sprint for each release, ie., SF meeting in >>Oct/14, and UY youth summit in Sept/14. >>- Request for former Sugar developers guidance. >>- Share design team responsibilities among all of us. >>- Document maintainers and responsibilities. >> >> *Topic #3: What are the Infrastructure needs?* >> >>- *Bring Pootle back to life*! Call for a special meeting regarding >>this. >> >> > Today (22 /04/2014), we had a meeting between gonzalo, cjl, icarito, > bernie and me. Summary: (a) bernie is going to update newpootle machine, > and (b) I am going to research a bit about setting a new Pootle instance > from scratch, to understand what would be best path to follow. > > >> >>- >>- Move activities repositories to github? >> >> > Gonzalo is going to make an inventory on activities and repositories. > >> >>- Set up a discourse instance (GSoC project)? >> >> >> Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for >> joining and contributing to the meeting! >> >> Saludos, >> tch. >> >> *Refs:* >> >>1. >> >> http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html >>2. http://wiki.sugarlabs.org/go/0.100/Roadmap >>3. https://wiki.gnome.org/ThreePointThirteen >>4. http://fedoraproject.org/wiki/Releases/21/Schedule >> >> >> > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
Hello everyone, Some updates: On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < martin.abente.lah...@gmail.com> wrote: > Hello everyone, > > This is a summary of the topics we discussed in our first development > meeting. Logs can be found here [1]. > > *Topic #1: What should we do for 0.104?* > >- Focus on core ideas: >- Fix or re-work collaboration? Cover web activities integration. > - Make Sugar more customizable? Get rid of control panel by > converting sections into applications. Make sugar itself modifiable like > activities. > - Make student assessment part of the sugar experience? Think of > ways in which all these statistics gathering efforts can become part of > this. > > >- Performance enhancements: >- Make Sugar more responsive? Starting by the journal. > - Make activities launch time faster? Moving common bits to > sugar-toolkit, ie., text-to-speech. > > >- Cover other classroom needs: >- Printing in Sugar? > - Integrate screen sharing in Sugar? > > These are initial suggestions, we all agreed that collaboration and > performance should be prioritized. > > > *Topic #2: How do we do it?* > >- Keep the current structure for phases and deadlines, ie., [2]. >- Keep the 6 months release schedules. >- Find a way to re-sync with Gnome [3] and Fedora [4], so we can >achieve the previous item. > > This is a tentative Roadmap for 0.104: http://wiki.sugarlabs.org/go/0.104/Roadmap . Please read it, think about it, and sent me your feedback. > >- >- Have regular development meetings. Each 2 weeks? Each month? >- Have at least one code sprint for each release, ie., SF meeting in >Oct/14, and UY youth summit in Sept/14. >- Request for former Sugar developers guidance. >- Share design team responsibilities among all of us. >- Document maintainers and responsibilities. > > *Topic #3: What are the Infrastructure needs?* > >- *Bring Pootle back to life*! Call for a special meeting regarding >this. > > Today (22 /04/2014), we had a meeting between gonzalo, cjl, icarito, bernie and me. Summary: (a) bernie is going to update newpootle machine, and (b) I am going to research a bit about setting a new Pootle instance from scratch, to understand what would be best path to follow. > >- >- Move activities repositories to github? > > Gonzalo is going to make an inventory on activities and repositories. > >- Set up a discourse instance (GSoC project)? > > > Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for > joining and contributing to the meeting! > > Saludos, > tch. > > *Refs:* > >1. > > http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html >2. http://wiki.sugarlabs.org/go/0.100/Roadmap >3. https://wiki.gnome.org/ThreePointThirteen >4. http://fedoraproject.org/wiki/Releases/21/Schedule > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
> This is a summary of the topics we discussed in our first development > meeting. Logs can be found here [1]. > > Topic #1: What should we do for 0.104? > > Focus on core ideas: > > Fix or re-work collaboration? Cover web activities integration. > Make Sugar more customizable? Get rid of control panel by converting > sections into applications. Make sugar itself modifiable like activities. > Make student assessment part of the sugar experience? Think of ways in which > all these statistics gathering efforts can become part of this. > > Performance enhancements: > > Make Sugar more responsive? Starting by the journal. > Make activities launch time faster? Moving common bits to sugar-toolkit, > ie., text-to-speech. > > Cover other classroom needs: > > Printing in Sugar? > Integrate screen sharing in Sugar? > > These are initial suggestions, we all agreed that collaboration and > performance should be prioritized. > > > Topic #2: How do we do it? > > Keep the current structure for phases and deadlines, ie., [2]. > Keep the 6 months release schedules. > Find a way to re-sync with Gnome [3] and Fedora [4], so we can achieve the > previous item. Let me know how I can assist with the Fedora side of things. At the moment I don't have a huge amount of cycles free at the moment but that should improve to some extend mid to late August. F-21 will have the latest 102 stable release, are there plans for bug fix dot releases? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
On 07/18/2014 12:46 PM, Martin Abente wrote: > Hello everyone, > > This is a summary of the topics we discussed in our first development > meeting. Logs can be found here [1]. > > *Topic #1: What should we do for 0.104?* > > * Focus on core ideas: > o Fix or re-work collaboration? Cover web activities integration. > o Make Sugar more customizable? Get rid of control panel by > converting sections into applications. Make sugar itself > modifiable like activities. > o Make student assessment part of the sugar experience? Think of > ways in which all these statistics gathering efforts can become > part of this. > > * Performance enhancements: > o Make Sugar more responsive? Starting by the journal. > o Make activities launch time faster? Moving common bits to > sugar-toolkit, ie., text-to-speech. > > * Cover other classroom needs: > o Printing in Sugar? > o Integrate screen sharing in Sugar? > > These are initial suggestions, we all agreed that collaboration and > performance should be prioritized. > > > *Topic #2: How do we do it?* > > * Keep the current structure for phases and deadlines, ie., [2]. > * Keep the 6 months release schedules. > * Find a way to re-sync with Gnome [3] and Fedora [4], so we can > achieve the previous item. > * Have regular development meetings. Each 2 weeks? Each month? > * Have at least one code sprint for each release, ie., SF meeting in > Oct/14, and UY youth summit in Sept/14. > * Request for former Sugar developers guidance. > * Share design team responsibilities among all of us. > * Document maintainers and responsibilities. > > *Topic #3: What are the Infrastructure needs?* > > * _Bring Pootle back to life_! Call for a special meeting regarding this. Let me know when this is happening. I can't volunteer to maintain Pootle, but I can support whoever steps up to do it. > * Move activities repositories to github? > * Set up a discourse instance (GSoC project)? > > > Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit > for joining and contributing to the meeting! > > Saludos, > tch. > > _Refs:_ > > 1. > http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html > 2. http://wiki.sugarlabs.org/go/0.100/Roadmap > 3. https://wiki.gnome.org/ThreePointThirteen > 4. http://fedoraproject.org/wiki/Releases/21/Schedule > > -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SUMMARY] development meeting 18/07/14
On Fri, Jul 18, 2014 at 12:46 PM, Martin Abente < martin.abente.lah...@gmail.com> wrote: > Hello everyone, > > This is a summary of the topics we discussed in our first development > meeting. Logs can be found here [1]. > > *Topic #1: What should we do for 0.104?* > >- Focus on core ideas: >- Fix or re-work collaboration? Cover web activities integration. > - Make Sugar more customizable? Get rid of control panel by > converting sections into applications. Make sugar itself modifiable like > activities. > - Make student assessment part of the sugar experience? Think of > ways in which all these statistics gathering efforts can become part of > this. > > For the record, I am not convinced that statistics gathering is the key to assessing the Sugar experience. This is perhaps more of a research project than a deployment topic at this point in time. -walter > >- Performance enhancements: >- Make Sugar more responsive? Starting by the journal. > - Make activities launch time faster? Moving common bits to > sugar-toolkit, ie., text-to-speech. > > >- Cover other classroom needs: >- Printing in Sugar? > - Integrate screen sharing in Sugar? > > These are initial suggestions, we all agreed that collaboration and > performance should be prioritized. > > > *Topic #2: How do we do it?* > >- Keep the current structure for phases and deadlines, ie., [2]. >- Keep the 6 months release schedules. >- Find a way to re-sync with Gnome [3] and Fedora [4], so we can >achieve the previous item. >- Have regular development meetings. Each 2 weeks? Each month? >- Have at least one code sprint for each release, ie., SF meeting in >Oct/14, and UY youth summit in Sept/14. >- Request for former Sugar developers guidance. >- Share design team responsibilities among all of us. >- Document maintainers and responsibilities. > > *Topic #3: What are the Infrastructure needs?* > >- *Bring Pootle back to life*! Call for a special meeting regarding >this. >- Move activities repositories to github? >- Set up a discourse instance (GSoC project)? > > > Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for > joining and contributing to the meeting! > > Saludos, > tch. > > *Refs:* > >1. > > http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html >2. http://wiki.sugarlabs.org/go/0.100/Roadmap >3. https://wiki.gnome.org/ThreePointThirteen >4. http://fedoraproject.org/wiki/Releases/21/Schedule > > > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [SUMMARY] development meeting 18/07/14
Hello everyone, This is a summary of the topics we discussed in our first development meeting. Logs can be found here [1]. *Topic #1: What should we do for 0.104?* - Focus on core ideas: - Fix or re-work collaboration? Cover web activities integration. - Make Sugar more customizable? Get rid of control panel by converting sections into applications. Make sugar itself modifiable like activities. - Make student assessment part of the sugar experience? Think of ways in which all these statistics gathering efforts can become part of this. - Performance enhancements: - Make Sugar more responsive? Starting by the journal. - Make activities launch time faster? Moving common bits to sugar-toolkit, ie., text-to-speech. - Cover other classroom needs: - Printing in Sugar? - Integrate screen sharing in Sugar? These are initial suggestions, we all agreed that collaboration and performance should be prioritized. *Topic #2: How do we do it?* - Keep the current structure for phases and deadlines, ie., [2]. - Keep the 6 months release schedules. - Find a way to re-sync with Gnome [3] and Fedora [4], so we can achieve the previous item. - Have regular development meetings. Each 2 weeks? Each month? - Have at least one code sprint for each release, ie., SF meeting in Oct/14, and UY youth summit in Sept/14. - Request for former Sugar developers guidance. - Share design team responsibilities among all of us. - Document maintainers and responsibilities. *Topic #3: What are the Infrastructure needs?* - *Bring Pootle back to life*! Call for a special meeting regarding this. - Move activities repositories to github? - Set up a discourse instance (GSoC project)? Many thanks to gonzalo, walterbender, llaske, bashintosh and satellit for joining and contributing to the meeting! Saludos, tch. *Refs:* 1. http://meeting.sugarlabs.org/sugar-meeting/meetings/2014-07-18T13:29:08.html 2. http://wiki.sugarlabs.org/go/0.100/Roadmap 3. https://wiki.gnome.org/ThreePointThirteen 4. http://fedoraproject.org/wiki/Releases/21/Schedule ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
