Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On 18 January 2011 22:46, Bernie Innocenti ber...@codewiz.org wrote: Originally, there was no way to pin particular versions in collections. One would always get the latest version flagged to work on your browser. Which is exactly what you're asking for. I'm not sure what's currently missing server-side, but it shouldn't be hard to do. We already have that, in a different format, which works fine: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 And it sounds like this (plus pestering of activity authors and/or use of admin power to correct compatibility info) is the best thing we have right now, even though both you and Aleksey don't fully see it as within the role of activities.sugarlabs.org (which I can understand too, but am left without somewhere else to turn). Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
Daniel, Why not use the wiki like in http://wiki.laptop.org/go/Activities/G1G1/10.1.3 ? I know is more work maintain the version for every activity, but we can help with this. Gonzalo On Wed, Jan 19, 2011 at 9:52 AM, Daniel Drake d...@laptop.org wrote: On 18 January 2011 22:46, Bernie Innocenti ber...@codewiz.org wrote: Originally, there was no way to pin particular versions in collections. One would always get the latest version flagged to work on your browser. Which is exactly what you're asking for. I'm not sure what's currently missing server-side, but it shouldn't be hard to do. We already have that, in a different format, which works fine: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 And it sounds like this (plus pestering of activity authors and/or use of admin power to correct compatibility info) is the best thing we have right now, even though both you and Aleksey don't fully see it as within the role of activities.sugarlabs.org (which I can understand too, but am left without somewhere else to turn). Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Wed, Jan 19, 2011 at 7:56 AM, Gonzalo Odiard gonz...@laptop.org wrote: Daniel, Why not use the wiki like in http://wiki.laptop.org/go/Activities/G1G1/10.1.3 ? I know is more work maintain the version for every activity, but we can help with this. This is not the best way to go, due to various reasons, one of them is that actvities.sugarlabs.org has filters of edition, wikis are designed to be fully open, but in our case could be dangerous, there are examples like doom, these violent games with the availability to be downloaded as activities generate controversy among teachers and parents (and also high the alarms between education officials of countries). Also people can put non-free activities there which we cannot distribute. Other advantage is that ASLO is controlled by the same activity authors not by third parties. regards, Gonzalo On Wed, Jan 19, 2011 at 9:52 AM, Daniel Drake d...@laptop.org wrote: On 18 January 2011 22:46, Bernie Innocenti ber...@codewiz.org wrote: Originally, there was no way to pin particular versions in collections. One would always get the latest version flagged to work on your browser. Which is exactly what you're asking for. I'm not sure what's currently missing server-side, but it shouldn't be hard to do. We already have that, in a different format, which works fine: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 And it sounds like this (plus pestering of activity authors and/or use of admin power to correct compatibility info) is the best thing we have right now, even though both you and Aleksey don't fully see it as within the role of activities.sugarlabs.org (which I can understand too, but am left without somewhere else to turn). Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Wed, Jan 19, 2011 at 11:29 AM, Rafael Enrique Ortiz Guerrero raf...@sugarlabs.org wrote: On Wed, Jan 19, 2011 at 7:56 AM, Gonzalo Odiard gonz...@laptop.orgwrote: Daniel, Why not use the wiki like in http://wiki.laptop.org/go/Activities/G1G1/10.1.3 ? I know is more work maintain the version for every activity, but we can help with this. This is not the best way to go, due to various reasons, one of them is that actvities.sugarlabs.org has filters of edition, wikis are designed to be fully open, but in our case could be dangerous, there are examples like doom, these violent games with the availability to be downloaded as activities generate controversy among teachers and parents (and also high the alarms between education officials of countries). Also people can put non-free activities there which we cannot distribute. Other advantage is that ASLO is controlled by the same activity authors not by third parties. The wiki have permissions too. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
The wiki approach has been tried with http://wiki.laptop.org/go/Activities (which probably needs a bit of a legal/deadlink/does not work with newer OSes/etc. cleanup) but ended up a bit of a mess. I'm not certain if permissions would help much. To split this page up properly in a wiki would require using the wiki as its own database with categories, supported Sugar versions, etc., some of which you might want to eventually change with bulk modifications. And while my wiki skills are not the best, the self-referencing wiki storage of OLPC test cases left me confused about how I could modify them without breaking anything going back. IMHO you basically would have to re-invent activity.sugarlabs.org to put it in a wiki, and I'm not certain if that is necessary at this time. On 01/19/11 09:31, Gonzalo Odiard wrote: On Wed, Jan 19, 2011 at 11:29 AM, Rafael Enrique Ortiz Guerrero raf...@sugarlabs.org mailto:raf...@sugarlabs.org wrote: On Wed, Jan 19, 2011 at 7:56 AM, Gonzalo Odiard gonz...@laptop.org mailto:gonz...@laptop.org wrote: Daniel, Why not use the wiki like in http://wiki.laptop.org/go/Activities/G1G1/10.1.3 ? I know is more work maintain the version for every activity, but we can help with this. This is not the best way to go, due to various reasons, one of them is that actvities.sugarlabs.org http://actvities.sugarlabs.org has filters of edition, wikis are designed to be fully open, but in our case could be dangerous, there are examples like doom, these violent games with the availability to be downloaded as activities generate controversy among teachers and parents (and also high the alarms between education officials of countries). Also people can put non-free activities there which we cannot distribute. Other advantage is that ASLO is controlled by the same activity authors not by third parties. The wiki have permissions too. Gonzalo ___ 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] Activities not compatible with Sugar-0.90
On Wed, 2011-01-19 at 12:52 +, Daniel Drake wrote: We already have that, in a different format, which works fine: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 And it sounds like this (plus pestering of activity authors and/or use of admin power to correct compatibility info) is the best thing we have right now, even though both you and Aleksey don't fully see it as within the role of activities.sugarlabs.org (which I can understand too, but am left without somewhere else to turn). I don't think we're going to phase out the RDF updater anytime soon, since all versions of Sugar shipped with Linux distros depend on it, including SoaS and USR. *However*, it would be nice if we could provide equivalent functionality with the microformat updater as well, so that the same olpc-os-builder module would work with both aslo and the wiki. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Mon, Jan 17, 2011 at 11:34:34PM -0500, Bernie Innocenti wrote: On Mon, 2011-01-17 at 17:11 -0500, Rafael Enrique Ortiz Guerrero wrote: I can't. I think every maintainer must do the change. Right every maintainer has to make that change in ASLO. Aren't you an aslo admin? You can change any activity. Imho, thats the job for activity authors (to see what sugar version is compatible with his activity). Another thing is that there is no way to say sugar = 0.86 on ASLO and uploaders need to add any new sugar version after it appeared. In dextrose we already have the code that relies on activity.info spec for sugar dep version, not to ASLO info. In my mind, thats the best way to go (and after that many activities switched to activity.info, we can remove sugar versions from ASLO at all). Btw, I guess most of not-all-sugars activities are Fructose, in time w/ switching to the new ASLO[1], we can review all activities and maybe do not implement sugar versions in new ASLO. For the record, the current aslo admins are: Tomeu Vizoso Wade Brainerd Simon Schampijer Mick Weiss Gary Martin david farning Walter Bender Sebastian Dziallas Rafael Ortiz Aleksey Lim Pablo Flores Bernie Innocenti josh [j...@tucson-labs.com] Thomas Gilliard Stefan Unterhauser Anish Mangal Sascha Silbe The activity editors are: Tomeu Vizoso Simon Schampijer Gary Martin Sebastian Dziallas Luke Faraone Rafael Ortiz James Simmons Aleksey Lim Activity Team We should probably cleanup both lists from people who are no longer actively working on ASLO. I think, would be better to do that on explicit requests from these people. As always, if anyone would like to help us maintaining ASLO or any other service provided by Sugar Labs, just let one of the Infrastructure Team members know. We hire volunteers after a short interview to ensure that they have the necessary technical skills and they intend to take the job seriously. Of course, when you run out of free time you can step down (responsibly!) from your role. Also, in my mind, ASLO is primarily a doer/user tool, so ASLO editors should not change existed uploads in the way they think is needed. They can remove existed activities if activities don't follow Editors policy[2] (or don not accept them to public). On other hand, when people (especially deployments) need the handle to say what activity version work in particular env., they can create collections and specify particular activity versions. This feature is accessible on activities-testing.sl.o and will be moved to production in time w/ dextrose-2 (that will contain new microformat updater). [1] http://wiki.sugarlabs.org/go/Platform_Team/Roadmap [2] http://wiki.sugarlabs.org/go/Activity_Library/Editors/Policy -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On 18 January 2011 13:06, Aleksey Lim alsr...@member.fsf.org wrote: Also, in my mind, ASLO is primarily a doer/user tool, so ASLO editors should not change existed uploads in the way they think is needed. I guess this means that my usage of activities.sugarlabs.org is not according to its design. Here's the task: I want to pull the latest activity version compatible with Sugar-0.90 for a specific set of activities from now until mid-April, several times a week. This is for their inclusion in development OS builds. What's your suggested approach to this? Right now I am querying http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 and parsing the resultant XML. Thanks, Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Tue, Jan 18, 2011 at 05:48:05PM +, Daniel Drake wrote: On 18 January 2011 13:06, Aleksey Lim alsr...@member.fsf.org wrote: Also, in my mind, ASLO is primarily a doer/user tool, so ASLO editors should not change existed uploads in the way they think is needed. I guess this means that my usage of activities.sugarlabs.org is not according to its design. Here's the task: I want to pull the latest activity version compatible with Sugar-0.90 for a specific set of activities from now until mid-April, several times a week. This is for their inclusion in development OS builds. What's your suggested approach to this? Right now I am querying http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 and parsing the resultant XML. You can either do not use appVersion and update-aslo.php will return recent versions or just create collection. The activity-testing.sl.o implementation allows setting particular activity versions (it will be pushed to production after testing within dextrose-2, that was the purpose for this feature). In the last case, collection content will be accessible via microformat page, eg: http://activities-testing.sugarlabs.org/services/micro-format.php?collection_nickname=fructose Thanks, Daniel -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On 18 January 2011 19:58, Aleksey Lim alsr...@member.fsf.org wrote: You can either do not use appVersion and update-aslo.php will return recent versions or just create collection. The activity-testing.sl.o implementation allows setting particular activity versions (it will be pushed to production after testing within dextrose-2, that was the purpose for this feature). In the last case, collection content will be accessible via microformat page, eg: http://activities-testing.sugarlabs.org/services/micro-format.php?collection_nickname=fructose I don't think either of those is what I need: If I drop appVersion, I'd get activities that run only on Sugar-0.92 and are incompatible with Sugar-0.90 (none right now, but I forsee a couple appearing before mid-April arrives). I want activities that are compatible with Sugar-0.90. If I use a collection, the versions are fixed to the exact versions that I add to the collection, whereas (see last mail) I want the latest activity version compatible with Sugar-0.90. (please correct me if I've misunderstood what a collection is) I'm now feeling more confident that my current approach is correct. Thoughts? Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Tue, 2011-01-18 at 20:32 +, Daniel Drake wrote: If I use a collection, the versions are fixed to the exact versions that I add to the collection, whereas (see last mail) I want the latest activity version compatible with Sugar-0.90. (please correct me if I've misunderstood what a collection is) The latest activity compatible with Sugar-X.Y is what the RDF protocol provided. This wasn't considered good for deployments enough because it doesn't allow the pedagogical team to do any QA on updates before they hit the users. So the idea is that Dextrose could create a collection dextrose2 which pins certain activity versions. Paraguay could create a collection dextrose2-py and pin slightly different activities. The downside of this approach is that development builds no longer get the latest and greatest activities automatically. Is this what is bothering you? Perhaps we could add separate microformat URLs that filter by Sugar version. In my mind, letting the activity owner self-certify which versions of Sugar are known to work well is poor QA practice. I'd rather have someone responsible to do some testing upfront before blessing them for the sugar-0.90 collection. Moreover, the version range currently supported by ASLO is a little too simplistic for the variety of ABIs that we're going to see soon: f14-s0.90-i386, f15-s0.92-arm... maybe even crazier. With multiple architectures, the dream of a simple universal bundle format for activity is over and our package management tools are still very immature. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On 18 January 2011 22:00, Bernie Innocenti ber...@codewiz.org wrote: This wasn't considered good for deployments enough because it doesn't allow the pedagogical team to do any QA on updates before they hit the users. Agreed. This is not for deployments, this is for development. The downside of this approach is that development builds no longer get the latest and greatest activities automatically. Is this what is bothering you? Yes. Perhaps we could add separate microformat URLs that filter by Sugar version. This would be good, but is basically what we have now in a different format: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 and I gathered from Aleksey that this isn't what activities.sugarlabs.org is designed for. (but judging from further responses, it's perhaps the only non-manual option that we have for now) Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Tue, Jan 18, 2011 at 05:00:07PM -0500, Bernie Innocenti wrote: On Tue, 2011-01-18 at 20:32 +, Daniel Drake wrote: If I use a collection, the versions are fixed to the exact versions that I add to the collection, whereas (see last mail) I want the latest activity version compatible with Sugar-0.90. (please correct me if I've misunderstood what a collection is) The latest activity compatible with Sugar-X.Y is what the RDF protocol provided. This wasn't considered good for deployments enough because it doesn't allow the pedagogical team to do any QA on updates before they hit the users. So the idea is that Dextrose could create a collection dextrose2 which pins certain activity versions. Paraguay could create a collection dextrose2-py and pin slightly different activities. The downside of this approach is that development builds no longer get the latest and greatest activities automatically. Is this what is bothering you? Perhaps we could add separate microformat URLs that filter by Sugar version. In my mind, letting the activity owner self-certify which versions of Sugar are known to work well is poor QA practice. I'd rather have someone responsible to do some testing upfront before blessing them for the sugar-0.90 collection. That depends on what side we are talking :), from deployment/distro pov, there is a need in [downstream] QA and collection is the right way (all activities need to be passed via such QA, if we talking about QA not just about letting deployment/distro users install some activities). My strong thinking is that ASLO should-not/impossible/useless be like a GNU/Linux distribution repository when all packages are well QAed and tested (it is perpendicular to sugar purposes when it is all about experiments and, thus, producing not-well-working/temporary solutions). ASLO is just a sharing place, we can have tens implementations of the same Record on ASLO (which is impossible in distribution repositories) from different doers and there [should not] is no any guaranties that all these implementations works well. If there is a need in guaranties, people work with particular doer (on improving particular activity) or create QAed/supporteded [downstream] collections. Moreover, the version range currently supported by ASLO is a little too simplistic for the variety of ABIs that we're going to see soon: f14-s0.90-i386, f15-s0.92-arm... maybe even crazier. With multiple architectures, the dream of a simple universal bundle format for activity is over and our package management tools are still very immature. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Tue, 2011-01-18 at 22:06 +, Daniel Drake wrote: Perhaps we could add separate microformat URLs that filter by Sugar version. This would be good, but is basically what we have now in a different format: http://activities.sugarlabs.org/services/update-aslo.php?id=ACTIVITYappVersion=0.90 and I gathered from Aleksey that this isn't what activities.sugarlabs.org is designed for. (but judging from further responses, it's perhaps the only non-manual option that we have for now) Ah, yeah... I agree it's a useful feature for development. Originally, there was no way to pin particular versions in collections. One would always get the latest version flagged to work on your browser. Which is exactly what you're asking for. I'm not sure what's currently missing server-side, but it shouldn't be hard to do. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Mon, Jan 17, 2011 at 09:07:32PM +, Daniel Drake wrote: Hi, According to activities.sugarlabs.org, the following activities (amongst others, probably) are not compatible with Sugar-0.90: org.laptop.WebActivity org.laptop.sugar.ReadActivity org.laptop.TamTamSynthLab, org.laptop.TamTamJam, org.laptop.TamTamEdit, org.laptop.TamTamMini, org.vpri.EtoysActivity, org.laptop.MeasureActivity org.laptop.ImpodeActivity vu.lux.olpc.Maze com.garycmartin.Moon edu.mit.media.ScratchActivity org.laptop.Terminal org.laptop.Log If these activities do work on 0.90, please mark them as so. Last changes for collections/microformat batch updater for ASLO: http://activities-testing.sugarlabs.org/services/micro-format.php?collection_nickname=collection-nick[sugar=sugar-version] * if activity version was not set in collection and sugar request argument wasn't passed, then return recent activity version * if activity version was not set in collection and sugar request argument was passed, then return either recent activity version only for this sugar or nothing * if activity version was set in collection, regardless sugar request argument, exactly this version will be returned Any help with testing this feature on activities-testing.sugarlabs.org (it several months copy of activities.sugarlabs.org) is welcome. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On 17 January 2011 21:07, Daniel Drake d...@laptop.org wrote: Hi, According to activities.sugarlabs.org, the following activities (amongst others, probably) are not compatible with Sugar-0.90: If these activities do work on 0.90, please mark them as so. Found a few more: org.laptop.community.TypingTurtle org.sugarlabs.InfoSlicer org.laptop.community.Colors org.laptop.community.Finance org.laptop.StopWatchActivity ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
Daniel I did a test with your image OS4, http://wiki.laptop.org/go/User:Godiard/Activities_for_F14#Activities_test_in_OS4 Gonzalo On Mon, Jan 17, 2011 at 6:10 PM, Daniel Drake d...@laptop.org wrote: On 17 January 2011 21:07, Daniel Drake d...@laptop.org wrote: Hi, According to activities.sugarlabs.org, the following activities (amongst others, probably) are not compatible with Sugar-0.90: If these activities do work on 0.90, please mark them as so. Found a few more: org.laptop.community.TypingTurtle org.sugarlabs.InfoSlicer org.laptop.community.Colors org.laptop.community.Finance org.laptop.StopWatchActivity ___ 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] Activities not compatible with Sugar-0.90
On 17 January 2011 21:17, Gonzalo Odiard gonz...@laptop.org wrote: Daniel I did a test with your image OS4, http://wiki.laptop.org/go/User:Godiard/Activities_for_F14#Activities_test_in_OS4 Thanks, I assume you found some of the ones in my list to be working? If so, please mark them as 0.90 compatible on activities.sugarlabs.org Thanks, Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Mon, Jan 17, 2011 at 6:22 PM, Daniel Drake d...@laptop.org wrote: On 17 January 2011 21:17, Gonzalo Odiard gonz...@laptop.org wrote: Daniel I did a test with your image OS4, http://wiki.laptop.org/go/User:Godiard/Activities_for_F14#Activities_test_in_OS4 Thanks, I assume you found some of the ones in my list to be working? If so, please mark them as 0.90 compatible on activities.sugarlabs.org Thanks, Daniel I can't. I think every maintainer must do the change. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
On Mon, Jan 17, 2011 at 4:28 PM, Gonzalo Odiard gonz...@laptop.org wrote: On Mon, Jan 17, 2011 at 6:22 PM, Daniel Drake d...@laptop.org wrote: On 17 January 2011 21:17, Gonzalo Odiard gonz...@laptop.org wrote: Daniel I did a test with your image OS4, http://wiki.laptop.org/go/User:Godiard/Activities_for_F14#Activities_test_in_OS4 Thanks, I assume you found some of the ones in my list to be working? If so, please mark them as 0.90 compatible on activities.sugarlabs.org Thanks, Daniel I can't. I think every maintainer must do the change. Right every maintainer has to make that change in ASLO. Gonzalo ___ 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] Activities not compatible with Sugar-0.90
On Mon, 2011-01-17 at 17:11 -0500, Rafael Enrique Ortiz Guerrero wrote: I can't. I think every maintainer must do the change. Right every maintainer has to make that change in ASLO. Aren't you an aslo admin? You can change any activity. For the record, the current aslo admins are: Tomeu Vizoso Wade Brainerd Simon Schampijer Mick Weiss Gary Martin david farning Walter Bender Sebastian Dziallas Rafael Ortiz Aleksey Lim Pablo Flores Bernie Innocenti josh [j...@tucson-labs.com] Thomas Gilliard Stefan Unterhauser Anish Mangal Sascha Silbe The activity editors are: Tomeu Vizoso Simon Schampijer Gary Martin Sebastian Dziallas Luke Faraone Rafael Ortiz James Simmons Aleksey Lim Activity Team We should probably cleanup both lists from people who are no longer actively working on ASLO. As always, if anyone would like to help us maintaining ASLO or any other service provided by Sugar Labs, just let one of the Infrastructure Team members know. We hire volunteers after a short interview to ensure that they have the necessary technical skills and they intend to take the job seriously. Of course, when you run out of free time you can step down (responsibly!) from your role. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities not compatible with Sugar-0.90
Hi On Mon, Jan 17, 2011 at 11:34 PM, Bernie Innocenti ber...@codewiz.orgwrote: On Mon, 2011-01-17 at 17:11 -0500, Rafael Enrique Ortiz Guerrero wrote: I can't. I think every maintainer must do the change. Right every maintainer has to make that change in ASLO. Aren't you an aslo admin? You can change any activity. Right!, i was forgotting those powers ;), I'll be testing those activities for sugar 0.9 and making changes on ASLO. For the record, the current aslo admins are: Tomeu Vizoso Wade Brainerd Simon Schampijer Mick Weiss Gary Martin david farning Walter Bender Sebastian Dziallas Rafael Ortiz Aleksey Lim Pablo Flores Bernie Innocenti josh [j...@tucson-labs.com] Thomas Gilliard Stefan Unterhauser Anish Mangal Sascha Silbe The activity editors are: Tomeu Vizoso Simon Schampijer Gary Martin Sebastian Dziallas Luke Faraone Rafael Ortiz James Simmons Aleksey Lim Activity Team We should probably cleanup both lists from people who are no longer actively working on ASLO. As always, if anyone would like to help us maintaining ASLO or any other service provided by Sugar Labs, just let one of the Infrastructure Team members know. We hire volunteers after a short interview to ensure that they have the necessary technical skills and they intend to take the job seriously. Of course, when you run out of free time you can step down (responsibly!) from your role. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
