<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 22, 2019 at 9:13 PM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Jan 22, 2019 at 01:29:56PM -0500, Devin Ulibarri wrote:<br>
> Hi,<br>
> <br>
> This was my experience:<br>
> <br>
>   • I came into SugarLabs community at the time that this migration was<br>
>     beginning to happen.<br>
>   • I started a GH account because that is where I was told the software was<br>
>     being maintained.<br>
>   • I have continued to "go with the flow" and work via GH although I have come<br>
>     to understand more of the history and context of this matter.<br>
> <br>
> These are my thoughts and opinions:<br>
> <br>
>   • I remember an argument that one reason to move to GH is "that is where all<br>
>     the developers are", but since our migration I have seen so many kids<br>
>     (usually GCI) set up new accounts with GH in order to contribute to SL (and<br>
>     to participate in GCI). This makes me think that many people are willing to<br>
>     join our development regardless of whatever tools/services we use, and<br>
>     whatever tool/services we use, if they are not yet setup with them, they<br>
>     are willing to get setup in order to join development.<br>
>   • Another argument seems to boil down to "we will be more productive using GH<br>
>     because we need not worry about the hassle of maintaining our own code<br>
>     hosting service". Is there evidence that we are more productive now than<br>
>     before? Not having the opportunity to learn/use the other systems, I would<br>
>     only be guessing.<br>
<br>
Not much evidence, it's about the same.  Like any tooling, you get<br>
good at it with time.  More productive now through the pull request<br>
and issue integration, but less productive through loss of situational<br>
awareness; changes are hidden in GitHub rather than being posted to<br>
sugar-devel@, and new developers fixate on their favourite<br>
repositories.<br>
<br>
>   • In theory, SL running its own version control, seems to me like it would be<br>
>     a) more fun for someone interested in this kind of work, b) a learning<br>
>     opportunity, and c) gives maximum freedom/flexibility to the ways in which<br>
>     we would like to do development.<br>
<br>
<a href="http://git.sugarlabs.org" rel="noreferrer" target="_blank">git.sugarlabs.org</a> hasn't needed any significant maintenance, and is<br>
probably insecure now because of vulnerabilities that haven't been<br>
patched.<br>
<br>
<a href="http://bugs.sugarlabs.org" rel="noreferrer" target="_blank">bugs.sugarlabs.org</a> has needed updates, but they have generally worked<br>
well.<br></blockquote><div><br></div><div>The spam issue made it almost unusable. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
>   • I would rather be using software that is licensed under a FLOSS license<br>
>     than a proprietary license. <a href="http://gnu.org" rel="noreferrer" target="_blank">gnu.org</a> came up with some criteria to evaluate<br>
>     "code hosting services" such as GH: [1]<a href="https://www.gnu.org/software/" rel="noreferrer" target="_blank">https://www.gnu.org/software/</a><br>
>     repo-criteria.html (which, btw, gets an "F", the lowest grade) The whole<br>
>     reason I am in this in the first place is because I believe the free/libre<br>
>     model of software to be the best for society and education. <br>
<br>
Yes, I agree.  Setting up an instance of GitLab could be done, but we<br>
would need someone willing to do that and maintain it.  Or we could<br>
use GitLab directly as other projects have done.<br></blockquote><div><br></div><div>What does that accomplish at this point? (That being said, I use GitLab for other projects and it works just fine.) </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> <br>
> Devin<br>
> <br>
> On Tue, 2019-01-22 at 07:15 +0200, Tony Anderson wrote:<br>
> <br>
>     Walter,<br>
> <br>
>     I will try. I am moving on Feb 3 to Palawan. I'll try to get to it then. My<br>
>     principal concern re GSOC is to define projects with manageable scope -<br>
>     many of the past projects ended undelivered.<br>
> <br>
>     Tony<br>
> <br>
>     On 1/21/19 3:10 PM, Walter Bender wrote:<br>
> <br>
>         On Mon, Jan 21, 2019 at 3:44 AM James Cameron <[2]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>><br>
>         wrote:<br>
> <br>
>             Fascinating, I never thought the move to GitHub was ever going to<br>
>             achieve all that.  It was to enable a shutdown of the unmaintained<br>
>             gitorious instance at [3]<a href="http://git.sugarlabs.org" rel="noreferrer" target="_blank">git.sugarlabs.org</a>.  Which still hasn't<br>
>             happened<br>
>             because it is still useful, in turn because this community hasn't<br>
>             the<br>
>             time to do the necessary leg work to finish the move to GitHub.<br>
> <br>
>         I would be curious what is still on Gitorious that hasn't been<br>
>         migrated.<br>
> <br>
>         FWIW, my principle motivations for the move were (1) as James points<br>
>         out -- on less piece of infrastructure for us to maintain; and (2)<br>
>         GitHub for better or worse is much more familiar to and likely to be<br>
>         discovered by potential developers. I think GH has been a decent tool<br>
>         which requires minimal effort on our part. Not sure that the latter<br>
>         really amounts to too much.<br>
> <br>
>         Re Tony's point about the ownership model, I don't see that anything we<br>
>         are doing suggests we don't want to continue to support individual<br>
>         contributions. I interpreted James's list not as a matter of ownership<br>
>         but rather a surfacing of what is actually happening re maintenance. In<br>
>         some sense, what is being articulated is the equivalent of the Fructose<br>
>         vs Honey nomenclature of the past where the core developers are saying:<br>
>         "These activities will be maintained. Cannot speak for everything<br>
>         else."<br>
> <br>
>         That said, I think Tony makes a great point re thinking about the<br>
>         pedagogical implications of our choices, which have had little if any<br>
>         input from the learning side of the house. Would be great to get more<br>
>         input to help us in regard to what is most valuable to our users<br>
>         (whether they know it or not). [4]@Tony Anderson would be great if you<br>
>         could rework you thoughts about Python into a GSoC idea.<br>
> <br>
>         regards.<br>
> <br>
>         -walter<br>
>          <br>
> <br>
>             In short, it has nothing to do with the tools, and everything to do<br>
>             with contributors.<br>
> <br>
>             I'll continue to focus on the activities I've got on my list.  That<br>
>             doesn't mean I won't help with the other activities, but I won't<br>
>             necessarily spend as much time with the others.<br>
> <br>
>             On Mon, Jan 21, 2019 at 09:12:01AM +0200, Tony Anderson wrote:<br>
>             > While it is marvelous to see some actual attention to the Sugar<br>
>             activities,<br>
>             > this approach is the direct opposite of the logic behind the move<br>
>             of the<br>
>             > activities to gitHub. This is a return to the G1G1 model in which<br>
>             individuals<br>
>             > develop, contribute and own activities. There can be no abandoned<br>
>             or orphaned<br>
>             > activities in a community support model.<br>
>             ><br>
>             > It was recognized by Walter and others that there were two<br>
>             factors which made<br>
>             > that ownership model unworkable. First, changes in Sugar software<br>
>             support such<br>
>             > as the move to GTK3 made common changes to all activities<br>
>             necessary and,<br>
>             > second, that many of the original contributors are no longer<br>
>             involved with<br>
>             > Sugar.<br>
>             ><br>
>             > GitHub was touted as the way in which Sugar Labs as a community<br>
>             would support<br>
>             > Sugar and its library of activities. However, in practice support<br>
>             for<br>
>             > activities has become increasingly limited to a small number of<br>
>             ones selected<br>
>             > for inclusion in the 13.2 series of builds.<br>
>             ><br>
>             > The Sugar activities library is made available to our users via<br>
>             ASLO.<br>
>             > Unfortunately, there are activities with new versions in gitHub<br>
>             which have not<br>
>             > been released to ASLO and thus are unknown to our users. There is<br>
>             even<br>
>             > confusion over which 'github'. It has to be kept clear that<br>
>             developers can use<br>
>             > any method they chose. What is controlled is the repository on<br>
>             gitHub. Any<br>
>             > changes outside of the Sugar Labs github are invisible until they<br>
>             are submitted<br>
>             > as a new version.<br>
>             ><br>
>             > Educational intent<br>
>             ><br>
>             > What I would like to see is a return to the founding philosophy<br>
>             of Sugar.<br>
>             > Everyone is welcome to contribute. When you get 10 lines of code<br>
>             working,<br>
>             > submit your activity. Sugar is designed to provide all the<br>
>             software tools<br>
>             > needed to develop activities in Sugar - no cross-development,<br>
>             containers, or<br>
>             > virtual environments. Instead of requesting new contributors to<br>
>             demonstrate<br>
>             > their technical proficiency by putting their name on the XO icon<br>
>             in the Home<br>
>             > View, identify some real examples of changes that would improve<br>
>             Sugar. There<br>
>             > are plenty available:<br>
>             ><br>
>             > Fix the icons on 'my settings' so they are visible instead of<br>
>             switching to<br>
>             > gnome by clicking on the big toe.<br>
>             > When you take a screenshot and switch to the Journal to give it a<br>
>             title, you<br>
>             > must use the Frame to return, not the Activity key.<br>
>             > The kids love the ability to customize their laptop with a<br>
>             background picture.<br>
>             > Unfortunately this often makes the icons in the Home View<br>
>             invisible.<br>
>             > Add Jupyter Notebook as a built-in capability of Sugar (possibly<br>
>             as a service<br>
>             > of Browse).<br>
>             > Help solve problems with a long list of activities (such as the<br>
>             lack of sound<br>
>             > in Block Party).<br>
>             > Find a way for Browse to support the css FlexBox.<br>
>             ><br>
>             > Stop using Pippy as a ceiling to our users learning to program in<br>
>             Python. They<br>
>             > can work up to 'Make your own Sugar Activities'.  Start with the<br>
>             Hello World<br>
>             > activity. Explain GTK and its benefits. PyDebug provides recipes<br>
>             for many<br>
>             > common coding situations. Stop hiding the Terminal and Log<br>
>             activities - try to<br>
>             > encourage them to become favorites. Soon we could see a new<br>
>             generation of<br>
>             > user-programmers as we did in Uruguay.<br>
>             ><br>
>             > Along this theme, we should embrace the RPI and its compatriots<br>
>             as a way to<br>
>             > make embedded computing tangible. It would not be difficult to<br>
>             connect such a<br>
>             > device via the Ad Hoc network so that it could be used to<br>
>             transfer a program<br>
>             > written on an XO to the device and execute it with the user<br>
>             seeing the results<br>
>             > on LEDs (e.g. Sense Hat).<br>
>             ><br>
>             > Tony<br>
>             ><br>
>             > On 1/20/19 3:48 PM, Walter Bender wrote:<br>
>             ><br>
>             >     I noticed Dimensions fell off the list. I will take that one<br>
>             on as I think<br>
>             >     it is of real value.<br>
>             ><br>
>             >     -walter<br>
>             ><br>
>             >     On Sun, Jan 20, 2019 at 8:44 AM James Cameron <[1][5]<br>
>             <a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br>
>             ><br>
>             >         Thanks.  So the list looks like;<br>
>             ><br>
>             >         # Walter Bender<br>
>             ><br>
>             >         * Music Blocks,<br>
>             >         * Turtle Blocks JS,<br>
>             ><br>
>             >         # Rahul Bothra<br>
>             ><br>
>             >         * CowBulls,<br>
>             >         * Flappy,<br>
>             >         * Cedit,<br>
>             >         * Polari,<br>
>             ><br>
>             >         # James Cameron<br>
>             ><br>
>             >         * Abacus,<br>
>             >         * Browse (master),<br>
>             >         * Browse (fedora 18 - webkit - v157.x),<br>
>             >         * Calculator,<br>
>             >         * Chart,<br>
>             >         * Chat,<br>
>             >         * Clock,<br>
>             >         * Develop,<br>
>             >         * Distance,<br>
>             >         * Finance,<br>
>             >         * Find Words,<br>
>             >         * Fototoon,<br>
>             >         * Fraction Bounce,<br>
>             >         * Gears,<br>
>             >         * GetBooks,<br>
>             >         * Help,<br>
>             >         * ImageViewer,<br>
>             >         * Implode,<br>
>             >         * Jukebox,<br>
>             >         * Labyrinth,<br>
>             >         * Letters,<br>
>             >         * Log,<br>
>             >         * Maze,<br>
>             >         * Measure,<br>
>             >         * Memorize,<br>
>             >         * Moon (master),<br>
>             >         * Moon (fedora 18 - gtk2 - v17.x),<br>
>             >         * MusicKeyboard (master),<br>
>             >         * MusicKeyboard (fedora 18 - csound - v8.x),<br>
>             >         * Paint,<br>
>             >         * Physics,<br>
>             >         * Pippy,<br>
>             >         * Poll,<br>
>             >         * Portfolio,<br>
>             >         * Read (master),<br>
>             >         * Read (fedora 18 - webkit - v118.x),<br>
>             >         * Record (master),<br>
>             >         * Record (fedora 18 - gstreamer - v10x),<br>
>             >         * SimpleEnglishWikipedia,<br>
>             >         * Speak,<br>
>             >         * StopWatch,<br>
>             >         * Story,<br>
>             >         * Terminal,<br>
>             >         * TurtleBlocks,<br>
>             >         * Words,<br>
>             >         * Write,<br>
>             ><br>
>             >         On Fri, Jan 18, 2019 at 09:04:50AM -0500, Walter Bender<br>
>             wrote:<br>
>             >         > I am actively maintaining Music Blocks and Turtle<br>
>             Blocks JS.<br>
>             >         > I just haven't had the bandwidth to do much beyond that<br>
>             of late. That<br>
>             >         said, I<br>
>             >         > am happy to kibbutz on any of the activities which I<br>
>             used to<br>
>             >         maintain.<br>
>             >         ><br>
>             >         > On Fri, Jan 18, 2019 at 3:11 AM Rahul Bothra <[1][2]<br>
>             >         [6]<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a>> wrote:<br>
>             >         ><br>
>             >         >     *<br>
>             >         >     I am maintaining CowBulls and Flappy.<br>
>             >         ><br>
>             >         >     I can take up cedit and Polari<br>
>             >         ><br>
>             >         >     On Fri, Jan 18, 2019 at 12:53 PM James Cameron <[2]<br>
>             [3]<br>
>             >         [7]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br>
>             >         ><br>
>             >         >         Once we had a list of abandoned activities,<br>
>             where the<br>
>             >         maintainer is<br>
>             >         >         missing in action, not doing testing or<br>
>             releasing.<br>
>             >         ><br>
>             >         >         Now, I propose the inverse; a list of<br>
>             activities with a<br>
>             >         maintainer<br>
>             >         >         testing and releasing.  It will be easier to<br>
>             maintain that<br>
>             >         list.<br>
>             >         ><br>
>             >         >         For myself, each of the Fructose activities,<br>
>             each of the<br>
>             >         activities we<br>
>             >         >         ship on OLPC OS.  I know Walter is looking<br>
>             after Music<br>
>             >         Blocks.  Lionel<br>
>             >         >         is looking after Sugarizer.  Are there any<br>
>             other developers<br>
>             >         who are<br>
>             >         >         maintainers?<br>
>             >         ><br>
>             >         >         --<br>
>             >         >         James Cameron<br>
>             >         >         [3][4][8]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             >         >         _______________________________________________<br>
>             >         >         Sugar-devel mailing list<br>
>             >         >         [4][5][9]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >         >         [5][6][10]<a href="http://lists.sugarlabs.org/listinfo/" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/</a><br>
>             sugar-devel<br>
>             >         ><br>
>             >         >     _______________________________________________<br>
>             >         >     Sugar-devel mailing list<br>
>             >         >     [6][7][11]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >         >     [7][8][12]<a href="http://lists.sugarlabs.org/listinfo/" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/</a><br>
>             sugar-devel<br>
>             >         ><br>
>             >         > --<br>
>             >         > Walter Bender<br>
>             >         > Sugar Labs<br>
>             >         > [8][9][13]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a><br>
>             >         > [9]<br>
>             >         ><br>
>             >         > References:<br>
>             >         ><br>
>             >         > [1] mailto:[10][14]<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
>             >         > [2] mailto:[11][15]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
>             >         > [3] [12][16]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             >         > [4] mailto:[13][17]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >         > [5] [14][18]<a href="http://lists.sugarlabs.org/listinfo/" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/</a><br>
>             sugar-devel<br>
>             >         > [6] mailto:[15][19]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >         > [7] [16][20]<a href="http://lists.sugarlabs.org/listinfo/" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/</a><br>
>             sugar-devel<br>
>             >         > [8] [17][21]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             >         > [9] [18][22]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             ><br>
>             >         --<br>
>             >         James Cameron<br>
>             >         [19][23]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             >         _______________________________________________<br>
>             >         Sugar-devel mailing list<br>
>             >         [20][24]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >         [21][25]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             ><br>
>             >     --<br>
>             >     Walter Bender<br>
>             >     Sugar Labs<br>
>             >     [22][26]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a><br>
>             ><br>
>             >   <br>
>             >     _______________________________________________<br>
>             >     Sugar-devel mailing list<br>
>             >     [23][27]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             >     [24][28]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             ><br>
>             > References:<br>
>             ><br>
>             > [1] mailto:[29]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
>             > [2] mailto:[30]<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
>             > [3] mailto:[31]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
>             > [4] [32]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             > [5] mailto:[33]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [6] [34]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             > [7] mailto:[35]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [8] [36]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             > [9] [37]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             > [10] mailto:[38]<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
>             > [11] mailto:[39]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
>             > [12] [40]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             > [13] mailto:[41]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [14] [42]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             > [15] mailto:[43]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [16] [44]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             > [17] [45]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             > [18] [46]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             > [19] [47]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             > [20] mailto:[48]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [21] [49]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
>             > [22] [50]<a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
>             > [23] mailto:[51]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [24] [52]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
>             > _______________________________________________<br>
>             > Sugar-devel mailing list<br>
>             > [53]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             > [54]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
>             --<br>
>             James Cameron<br>
>             [55]<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
>             _______________________________________________<br>
>             Sugar-devel mailing list<br>
>             [56]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>             [57]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
>         --<br>
>         Walter Bender<br>
>         Sugar Labs<br>
>         [58]<a href="http://www.sugarlabs.org" rel="noreferrer" target="_blank">http://www.sugarlabs.org</a><br>
> <br>
>        <br>
>         _______________________________________________<br>
>         Sugar-devel mailing list<br>
>         [59]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>         [60]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
>     _______________________________________________<br>
>     Sugar-devel mailing list<br>
>     [61]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
>     [62]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> <br>
> References:<br>
> <br>
> [1] <a href="https://www.gnu.org/software/repo-criteria.html" rel="noreferrer" target="_blank">https://www.gnu.org/software/repo-criteria.html</a><br>
> [2] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [3] <a href="http://git.sugarlabs.org/" rel="noreferrer" target="_blank">http://git.sugarlabs.org/</a><br>
> [4] mailto:<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a><br>
> [5] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [6] mailto:<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
> [7] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [8] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [9] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [10] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [11] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [12] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [13] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [14] mailto:<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
> [15] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [16] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [17] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [18] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [19] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [20] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [21] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [22] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [23] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [24] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [25] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [26] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [27] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [28] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [29] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [30] mailto:<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
> [31] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [32] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [33] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [34] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [35] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [36] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [37] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [38] mailto:<a href="mailto:rrbothra@gmail.com" target="_blank">rrbothra@gmail.com</a><br>
> [39] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br>
> [40] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [41] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [42] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [43] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [44] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [45] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [46] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [47] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [48] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [49] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [50] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [51] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [52] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [53] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [54] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [55] <a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
> [56] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [57] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [58] <a href="http://www.sugarlabs.org/" rel="noreferrer" target="_blank">http://www.sugarlabs.org/</a><br>
> [59] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [60] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
> [61] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> [62] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
<br>
-- <br>
James Cameron<br>
<a href="http://quozl.netrek.org/" rel="noreferrer" target="_blank">http://quozl.netrek.org/</a><br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div></div>