Re: [Sugar-devel] Bundlebuilder and mime-type related files
Quoting Martin Abente (2015-05-25 20:21:55) So basically, there are 2 problems. 1. symlinks creation during ./setup.py --install (for installing the mimetypes.xml file .svg icons for mime types declared in activity.info) and, 2. the execution of update-mime-database (which generates the database files). I agree with 1. but have not yet experienced 2. myself. I would appreciate if you could provide steps to reproduce 2. on Debian, so that I can help investigate. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bundlebuilder and mime-type related files
Quoting James Cameron (2015-05-26 10:03:00) On Tue, May 26, 2015 at 08:49:41AM +0200, Jonas Smedegaard wrote: Quoting Martin Abente (2015-05-25 20:21:55) So basically, there are 2 problems. 1. symlinks creation during ./setup.py --install (for installing the mimetypes.xml file .svg icons for mime types declared in activity.info) and, 2. the execution of update-mime-database (which generates the database files). I agree with 1. but have not yet experienced 2. myself. I would appreciate if you could provide steps to reproduce 2. on Debian, so that I can help investigate. I've a system tracking Debian Stretch on which 2 can be reproduced, using the Memorize-35 activity: a. git clone git://anonscm.debian.org/collab-maint/sugar-memorize-activity.git b. edit /usr/bin/update-mime-database to show evidence of activation, and print arguments, by adding a line: echo $0 $* c. ./setup.py install In this context, outside of dpkg-buildpackage, the argument to update-mime-database is /root/.local/share/mime, and is set in activitybundle.py in python-sugar3 package. Hope that helps. That is helpful, yes: I thought the problem was MIME database files ending up inside the package, but I do see now how the update-mime-database call generates those database files in XDG paths. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bundlebuilder and mime-type related files
On Tue, May 26, 2015 at 08:49:41AM +0200, Jonas Smedegaard wrote: Quoting Martin Abente (2015-05-25 20:21:55) So basically, there are 2 problems. 1. symlinks creation during ./setup.py --install (for installing the mimetypes.xml file .svg icons for mime types declared in activity.info) and, 2. the execution of update-mime-database (which generates the database files). I agree with 1. but have not yet experienced 2. myself. I would appreciate if you could provide steps to reproduce 2. on Debian, so that I can help investigate. I've a system tracking Debian Stretch on which 2 can be reproduced, using the Memorize-35 activity: a. git clone git://anonscm.debian.org/collab-maint/sugar-memorize-activity.git b. edit /usr/bin/update-mime-database to show evidence of activation, and print arguments, by adding a line: echo $0 $* c. ./setup.py install In this context, outside of dpkg-buildpackage, the argument to update-mime-database is /root/.local/share/mime, and is set in activitybundle.py in python-sugar3 package. Hope that helps. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Musicpainter-14
Activity Homepage: http://activities.sugarlabs.org/addon/4730 Sugar Platform: 0.82 - 0.104 Download Now: http://activities.sugarlabs.org/downloads/file/29113/musicpainter-14.xo Release notes: Musicpainter-14 includes full network features, in which the user can share their creations to the world, and explore music composed by others. The release fixes a critical bug from previous version, and is now backward compatible to XO 1.5 (avoid using features that is only supported in PyGtk 2.16 or above). Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 79, Issue 61
On Sat, May 23, 2015 at 2:35 PM, Tony Anderson tony_ander...@usa.net wrote: Somewhere I got lost. I had originally understood docker as a mechanism to run Sugar on platforms other than an XO. You are right. This is a experiment, don;t take it out of proportion. In learning to program in Python, I lean to the idea that it should be done with the Terminal Activity (command line, nano text editor). The use of an integrated development environment (Pippy, IDLE, IPython, Eclipse) can be introduced as an advanced topic - incidentally IPython runs quite nicely on an XO). I can't image a professional building a web application using Pippy. I think students should learn to build web applications using standard methods: HTML, CSS, and Javascript. Again, using the command line and nano. The GSOC project to build an interactive javascript shell reflects the fact that Python has an inherently better development environment and that Javascript really needs an interactive display of the web page (and debugging via the console.log mechanism). Although Sugar is becoming more dependent on internet access, that is not an option for many deployments. Flask or Django could be introduced as an advanced topic with the framework hosted on the school server. This will require some careful planning so that student interaction does not introduce instability since there is normally no qualified system administrator available to deal with server problems. I am lost here now :) Why we are talking about use pippy for professional work? If you want teach some kids to develop a web site, is ok, but Sugar is not designed to be a production environment, in the same way that Eclipse is not designed to tech math. Why should we want teach Flask or Django to kids from 6 to 12 years old? Gonzalo Tony On 05/23/2015 06:00 PM, sugar-devel-requ...@lists.sugarlabs.org wrote: Message: 6 Date: Sat, 23 May 2015 08:11:54 + From: tkk...@nurturingasia.com To: Sebastian Silva sebast...@fuentelibre.org, tkk...@nurturingasia.com, sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop Message-ID: W6839625023265491432368714@atl4webmail07 Content-Type: text/plain; charset=windows-1252 Thanks for the feedback. Just that I have been testing other people web applications (and saving me time) with docker that I feel perhaps a kid with an XO can do the same and learn something with lighter weight virtualization. Hope some developer can take up Sam's and your recommendation of Flask. Cheers -Original Message- From: Sebastian Silva [mailto:sebast...@fuentelibre.org] Sent: Saturday, May 23, 2015 03:55 PM To:tkk...@nurturingasia.com,sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop On 23/05/15 02:00,tkk...@nurturingasia.com wrote: Hope it makes sense:-) It still doesn't, to me at least. It's sounds like you are saying you want to run any linux distro on virtualbox on xo. It would be pointless waste of machine resources because you are already running a linux distro. You can write full, professional web apps from Pippy, if you have access to one or two extra python packages ( personal favorite, try Flask http://flask.pocoo.org/ ). The trick is getting to them, which is why Sam's proposal is quite good, access to the Python Package Index from Pippy... -- I+D SomosAzucar.Org icarito #somosazucar en Freenode IRC Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan en comuni?n - P. Freire -- ___ 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 -- 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] Sugar-devel Digest, Vol 79, Issue 61
On Tue, May 26, 2015 at 9:06 AM, Gonzalo Odiard godi...@sugarlabs.org wrote: On Sat, May 23, 2015 at 2:35 PM, Tony Anderson tony_ander...@usa.net wrote: Somewhere I got lost. I had originally understood docker as a mechanism to run Sugar on platforms other than an XO. You are right. This is a experiment, don;t take it out of proportion. In learning to program in Python, I lean to the idea that it should be done with the Terminal Activity (command line, nano text editor). The use of an integrated development environment (Pippy, IDLE, IPython, Eclipse) can be introduced as an advanced topic - incidentally IPython runs quite nicely on an XO). I can't image a professional building a web application using Pippy. I think students should learn to build web applications using standard methods: HTML, CSS, and Javascript. Again, using the command line and nano. The GSOC project to build an interactive javascript shell reflects the fact that Python has an inherently better development environment and that Javascript really needs an interactive display of the web page (and debugging via the console.log mechanism). Although Sugar is becoming more dependent on internet access, that is not an option for many deployments. Flask or Django could be introduced as an advanced topic with the framework hosted on the school server. This will require some careful planning so that student interaction does not introduce instability since there is normally no qualified system administrator available to deal with server problems. I am lost here now :) Why we are talking about use pippy for professional work? If you want teach some kids to develop a web site, is ok, but Sugar is not designed to be a production environment, in the same way that Eclipse is not designed to tech math. Why should we want teach Flask or Django to kids from 6 to 12 years old? The idea from Day One was that the Sugar environment would be for exploration and the GNOME desktop would be used for production. Students would gradually migrate from one to the other. Is there a reason to abandon this framework? Hence I agree with Gonzalo that we need to not distort Sugar's goals to service professional production values. -walter Gonzalo Tony On 05/23/2015 06:00 PM, sugar-devel-requ...@lists.sugarlabs.org wrote: Message: 6 Date: Sat, 23 May 2015 08:11:54 + From: tkk...@nurturingasia.com To: Sebastian Silva sebast...@fuentelibre.org, tkk...@nurturingasia.com, sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop Message-ID: W6839625023265491432368714@atl4webmail07 Content-Type: text/plain; charset=windows-1252 Thanks for the feedback. Just that I have been testing other people web applications (and saving me time) with docker that I feel perhaps a kid with an XO can do the same and learn something with lighter weight virtualization. Hope some developer can take up Sam's and your recommendation of Flask. Cheers -Original Message- From: Sebastian Silva [mailto:sebast...@fuentelibre.org] Sent: Saturday, May 23, 2015 03:55 PM To:tkk...@nurturingasia.com,sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop On 23/05/15 02:00,tkk...@nurturingasia.com wrote: Hope it makes sense:-) It still doesn't, to me at least. It's sounds like you are saying you want to run any linux distro on virtualbox on xo. It would be pointless waste of machine resources because you are already running a linux distro. You can write full, professional web apps from Pippy, if you have access to one or two extra python packages ( personal favorite, try Flask http://flask.pocoo.org/ ). The trick is getting to them, which is why Sam's proposal is quite good, access to the Python Package Index from Pippy... -- I+D SomosAzucar.Org icarito #somosazucar en Freenode IRC Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan en comuni?n - P. Freire -- ___ 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 -- Gonzalo Odiard SugarLabs - Software for children learning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 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] Sugar DIgest 2015-05-26
1. It is with great sadness that write these words: Marco Presenti Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and one of the founders of Sugar Labs, passed away this past weekend after a long illness. Marco was a brilliant engineer whose work still reverberates throughout the Sugar stack and a warm, personable colleague, father, and husband. We will miss you Marco. == Sugar Digest == 2. For those of you who are interested, we hold our GSoC group meetings on Fridays, 11:00 EST (Boston), 14:00 UTC on irc.freenode.net #sugar-meeting. === Tech Talk === 3. Peter Robinson, Sam Parkinson, Sean Daly, and Iain Brown Douglas have done a great job of revamping the Sugar on a Stick spin site for Fedora. Please see [1]. === Sugar Labs === 4. Please visit our planet [2]. --- [1] http://spins.stg.fedoraproject.org/en/soas/ [2] http://planet.sugarlabs.org -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 79, Issue 61
On 26/05/15 08:13, Walter Bender wrote: The idea from Day One was that the Sugar environment would be for exploration and the GNOME desktop would be used for production. I never read this and I completely disagree. IMHO one should be able to do the same things on either desktop. Of course, this is not to say one should deploy production apps on any desktop. -- I+D SomosAzucar.Org icarito #somosazucar en Freenode IRC Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan en comunión - P. Freire ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Sugar DIgest 2015-05-26
Just saw the news as well. https://mail.gnome.org/archives/desktop-devel-list/2015-May/msg00027.html I exchanged a few notes with him about his illness some time ago (my mother had the same. She passed away a few months ago). Marco seemed to be doing better. His work will live on. Sameer On May 26, 2015 6:28 AM, Walter Bender walter.ben...@gmail.com wrote: 1. It is with great sadness that write these words: Marco Presenti Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and one of the founders of Sugar Labs, passed away this past weekend after a long illness. Marco was a brilliant engineer whose work still reverberates throughout the Sugar stack and a warm, personable colleague, father, and husband. We will miss you Marco. == Sugar Digest == 2. For those of you who are interested, we hold our GSoC group meetings on Fridays, 11:00 EST (Boston), 14:00 UTC on irc.freenode.net #sugar-meeting. === Tech Talk === 3. Peter Robinson, Sam Parkinson, Sean Daly, and Iain Brown Douglas have done a great job of revamping the Sugar on a Stick spin site for Fedora. Please see [1]. === Sugar Labs === 4. Please visit our planet [2]. --- [1] http://spins.stg.fedoraproject.org/en/soas/ [2] http://planet.sugarlabs.org -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar all-hands meeting
The next Sugar Labs oversight board meeting is on Monday. Anyone in the community is, as always, welcome to suggest discussion topics. -walter On Tue, May 26, 2015 at 1:28 PM, Samuel Greenfeld sam...@greenfeld.org wrote: I know there have been various board and development meetings for Sugar. But I would like to propose having an all-hands meeting where anyone in the Sugar community as well as related groups (deployments, schoolserver, etc.) could raise a topic and attend. If there are few enough people, we might be able to do this with a Google Hangout. For larger crowds we should try to get permission to use an international conference bridge (to avoid a dozen echo cancelers getting confused by each other). There are a lot of things that need to be done that I suspect could happen given a wider audience. --- SJG ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 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] Fwd: Fedora 22 is here!
Hi All, Fedora 22, and by association, Sugar on a Stick 22 is now available. To go along with the new SoaS release we have a spiffy new site too. https://spins.fedoraproject.org/en/soas/ Full details about the Fedora 22 release is below. Thanks to all for their assistance and hard work in this release. Regards, Peter -- Forwarded message -- From: Matthew Miller mat...@fedoraproject.org Date: Tue, May 26, 2015 at 2:49 PM Subject: Fedora 22 is here! To: annou...@lists.fedoraproject.org We are proud to announce the official release of Fedora 22, the community-driven and community-built operating system now available in Cloud, Server, and Workstation editions. If that's all you need to hear, jump over to Get Fedora to download -- or for current users, run the FedUp upgrade tool. * https://getfedora.org/ * https://fedoraproject.org/wiki/FedUp In addition to the latest versions of all your favorite free and open source software, Fedora 22 marks our second release with distinctly-targeted offerings for cloud computing, the server room, and the desktops and laptops of software developers and creators everywhere. Thanks to the hard work of developers, designers, packagers, translators, testers, documentation writers, and everyone else, we're incredibly confident in saying that this is our best and most polished release yet. Also with this release, we return to our traditional six-month cadence -- we'll see you back here sometime around Halloween! Highlights in the Fedora 22 release === Every Fedora release has its own character. If this release had a human analogue, it'd be Fedora 21 after it'd been to college, landed a good job, and kept its New Year's Resolution to go to the gym on a regular basis. What we're saying is that Fedora 22 has built on the foundation we laid with Fedora 21 and the work to create distinct editions of Fedora focused on the desktop, server, and cloud (respectively). It's not radically different, but there are a fair amount of new features coupled with features we've already introduced but have improved for Fedora 22. Fedora Cloud Fedora 22 Cloud edition has a number of interesting updates that should be exciting for users and developers. * Updated Docker Images – The Fedora 22 release includes updated Docker images that you can use as the base of your containerized applications. * Vagrant Boxes – One of the oft-requested features for Fedora is an “official” Vagrant box that developers can use to spin up images using the popular Vagrant tool for building development environments. With the Fedora 22 release we now offer Vagrant Boxes for libvirt and VirtualBox, so developers on Linux, Mac OS X, and Windows can spin up Fedora-based development environments with ease. Users can choose a Vagrant box for Fedora 22 Atomic Host and Fedora 22 Cloud base edition. * Atomic Improvements – Fedora 22 Atomic Host includes a number of interesting improvements, including the Atomic command, updated Docker, Kubernetes, Flannel, and rpm-ostree packages. * Dockerfiles – Fedora 22 also includes a fedora-dockerfiles package (and up-to-date git repository) for building applications with the base Fedora 22 Dockerfile and additional packages. Fedora Server - * Database Server Role -- The Fedora Server edition focuses on easy of different server roles. Fedora 21 debuted with an Domain Controller Role featuring FreeIPA. For this release, we've added a Database Server role, built around PostgreSQL. * Default to XFS filesystem -- The default file system type for Fedora Server installs will be XFS running atop LVM for all partitions except /boot. The /boot partition will remain a non-LVM, ext4 partition due to technological limitations of the bootloader. * Cockpit will be compatible between OS releases -- Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser. - Easy to use. Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services. - No interference. Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface. - Multi-server. You can monitor and administer several servers at the same time. Fedora Workstation -- * Better notifications. Thanks both to work done in GNOME 3.16 and other projects like the Automatic Bug Reporting Tool (ABRT), notifications keep you better informed, but interfere less with your work. They now appear anchored to the center of the top bar, and no longer cover up the bottom of the screen where you are often reading a terminal or browser. An unobtrusive marker appears in
Re: [Sugar-devel] [IAEP] Sugar DIgest 2015-05-26
On Tue, May 26, 2015 at 10:28 AM, Walter Bender walter.ben...@gmail.com wrote: 1. It is with great sadness that write these words: Marco Presenti Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and one of the founders of Sugar Labs, passed away this past weekend after a long illness. Marco was a brilliant engineer whose work still reverberates throughout the Sugar stack and a warm, personable colleague, father, and husband. We will miss you Marco. Our condolences to his family and friends. I din't have the luck of work with him, but his work is everywhere in Sugar, we can dedicate 0.106 to him. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar all-hands meeting
+1 On 05/26/2015 09:29 PM, Samuel Greenfeld wrote: Looking at past minutes, I think I am proposing more of a change in procedure than topics for the oversight meeting. We need to get more people involved than are present in the IRC meetings. In general I am echoing what was said on the Planning for the Future email thread from three months ago. But some topics (for the oversight meeting or an all-hands meeting) would be: 1. What can Sugar publicly commit to having in terms of users/developers/finances/etc. beyond what was mentioned in the deployment survey. Witness Dan's complaints over the 3 million number, James noting no one filed a bug report for Sugar 0.105.1 yet, the lack of candidates for past elections, the lack of interaction between the XS development and Sugar development communities, etc. It also would be useful to know what users/developers/etc. could publicly commit to Sugar. 2. What is being done to address the main issues raised by deployments in the latest development survey. 3. A complete holistic overhaul of how releases are done and marketed. Sugar was originally created with a if you build it, they will come approach that many community members have at least privately complained about. We need real-world examples of how to integrate Sugar with curriculums, reference deployments willing to speak with prospective ones, etc. Setting up Sugar needs to be no harder than a child using it for the first time. 4. What is being done to attract new deployments, developers (besides GSoC) and project sponsors. 5. I would like to propose a Sugar Ambassador program similar to the Fedora one where less-technical members of the community could engage with other groups to figure out what they would need to use Sugar. This does not necessarily mean that we need to fly them everywhere; but it would give us a good idea of what might be required to obtain gain certain types of deployments. On Tue, May 26, 2015 at 1:47 PM, Walter Bender walter.ben...@gmail.com mailto:walter.ben...@gmail.com wrote: The next Sugar Labs oversight board meeting is on Monday. Anyone in the community is, as always, welcome to suggest discussion topics. -walter On Tue, May 26, 2015 at 1:28 PM, Samuel Greenfeld sam...@greenfeld.org mailto:sam...@greenfeld.org wrote: I know there have been various board and development meetings for Sugar. But I would like to propose having an all-hands meeting where anyone in the Sugar community as well as related groups (deployments, schoolserver, etc.) could raise a topic and attend. If there are few enough people, we might be able to do this with a Google Hangout. For larger crowds we should try to get permission to use an international conference bridge (to avoid a dozen echo cancelers getting confused by each other). There are a lot of things that need to be done that I suspect could happen given a wider audience. --- SJG ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org mailto:Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 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 mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar all-hands meeting
Looking at past minutes, I think I am proposing more of a change in procedure than topics for the oversight meeting. We need to get more people involved than are present in the IRC meetings. In general I am echoing what was said on the Planning for the Future email thread from three months ago. But some topics (for the oversight meeting or an all-hands meeting) would be: 1. What can Sugar publicly commit to having in terms of users/developers/finances/etc. beyond what was mentioned in the deployment survey. Witness Dan's complaints over the 3 million number, James noting no one filed a bug report for Sugar 0.105.1 yet, the lack of candidates for past elections, the lack of interaction between the XS development and Sugar development communities, etc. It also would be useful to know what users/developers/etc. could publicly commit to Sugar. 2. What is being done to address the main issues raised by deployments in the latest development survey. 3. A complete holistic overhaul of how releases are done and marketed. Sugar was originally created with a if you build it, they will come approach that many community members have at least privately complained about. We need real-world examples of how to integrate Sugar with curriculums, reference deployments willing to speak with prospective ones, etc. Setting up Sugar needs to be no harder than a child using it for the first time. 4. What is being done to attract new deployments, developers (besides GSoC) and project sponsors. 5. I would like to propose a Sugar Ambassador program similar to the Fedora one where less-technical members of the community could engage with other groups to figure out what they would need to use Sugar. This does not necessarily mean that we need to fly them everywhere; but it would give us a good idea of what might be required to obtain gain certain types of deployments. On Tue, May 26, 2015 at 1:47 PM, Walter Bender walter.ben...@gmail.com wrote: The next Sugar Labs oversight board meeting is on Monday. Anyone in the community is, as always, welcome to suggest discussion topics. -walter On Tue, May 26, 2015 at 1:28 PM, Samuel Greenfeld sam...@greenfeld.org wrote: I know there have been various board and development meetings for Sugar. But I would like to propose having an all-hands meeting where anyone in the Sugar community as well as related groups (deployments, schoolserver, etc.) could raise a topic and attend. If there are few enough people, we might be able to do this with a Google Hangout. For larger crowds we should try to get permission to use an international conference bridge (to avoid a dozen echo cancelers getting confused by each other). There are a lot of things that need to be done that I suspect could happen given a wider audience. --- SJG ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sugar-news] Sugar DIgest 2015-05-26
On Tue, May 26, 2015 at 3:28 PM, Walter Bender walter.ben...@gmail.com wrote: 1. It is with great sadness that write these words: Marco Presenti Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and one of the founders of Sugar Labs, passed away this past weekend after a long illness. Marco was a brilliant engineer whose work still reverberates throughout the Sugar stack and a warm, personable colleague, father, and husband. We will miss you Marco. Thank you for sharing this sad news which I - and I assume many others here - would have missed otherwise. Reading it made me go back through my e-mail and photo archives and I found this shot from FUDCon Brno in September 2008: [image: Inline image 1] I'll always remember mpg like that: A brilliant and cheerful software engineer amidst like-minded and equally friendly and dedicated software geniuses who built the foundations of Sugar. And +1 to Gonzalo's suggestions of dedicating 0.106 to Marco and his young family! If anyone has his physical address please let me know as I'd love send my condolences to his two Danielas in this time of sadness and mourning. Christoph == Sugar Digest == 2. For those of you who are interested, we hold our GSoC group meetings on Fridays, 11:00 EST (Boston), 14:00 UTC on irc.freenode.net #sugar-meeting. === Tech Talk === 3. Peter Robinson, Sam Parkinson, Sean Daly, and Iain Brown Douglas have done a great job of revamping the Sugar on a Stick spin site for Fedora. Please see [1]. === Sugar Labs === 4. Please visit our planet [2]. --- [1] http://spins.stg.fedoraproject.org/en/soas/ [2] http://planet.sugarlabs.org -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Community-news mailing list community-n...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/community-news -- Christoph Derndorfer volunteer, OLPC (Austria) [www.olpc.at] editor, OLPC News [www.olpcnews.com] co-founder, TechnikBasteln® [www.technikbasteln.net] e-mail: christ...@derndorfer.eu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 79, Issue 61
On Tue, May 26, 2015 at 9:36 AM, Sebastian Silva sebast...@fuentelibre.org wrote: On 26/05/15 08:13, Walter Bender wrote: The idea from Day One was that the Sugar environment would be for exploration and the GNOME desktop would be used for production. I never read this and I completely disagree. IMHO one should be able to do the same things on either desktop. Of course, this is not to say one should deploy production apps on any desktop. Maybe we can agree to disagree on this issue. While it would be lovely to have the resources to make every GNOME tool run flawlessly in Sugar, I don't see that happening. (Nor do I see the point, but I am happy to hear arguments as to why this would be important.) To me, Sugar has always had different goals than GNOME, hence the need to build a separate desktop. But never was one of the goals to replace GNOME. regards. -walter -- I+D SomosAzucar.Org icarito #somosazucar en Freenode IRC Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan en comunión - P. Freire -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Docker in Sugar/XO laptop
I was responding to Sebastian Silva's comment: You can write full, professional web apps from Pippy, if you have access to one or two extra python packages ( personal favorite, try Flask http://flask.pocoo.org/ ). The trick is getting to them, which is why Sam's proposal is quite good, access to the Python Package Index from Pippy... My confusion was the reference to pippy for writing web apps. I assume the reference to Flask was to the availability of Python packages to install. My remarks were that it would be difficult to set up Flask or Django on a school server and have students create applications from a systems administration point of view. At some point, students learning to program should understand message-passing whether between processes or between server and client. My leaning is to a 'bare bones' approach, not basing the learning on a framework intended to make the mechanics invisible. That can come later as the student develops experience and an understanding of work flow. I am not sure I understand the distinction between exploration and production in this context. At my last workshop, we needed to use GIMP to crop and resize images. Naturally we could have used GIMP in Sugar from the command line. Using GIMP to crop images is certainly production, although needed in a context of exploration (printing booklets). Tony On 05/26/2015 03:13 PM, Walter Bender wrote: I am lost here now :) Why we are talking about use pippy for professional work? If you want teach some kids to develop a web site, is ok, but Sugar is not designed to be a production environment, in the same way that Eclipse is not designed to tech math. Why should we want teach Flask or Django to kids from 6 to 12 years old? The idea from Day One was that the Sugar environment would be for exploration and the GNOME desktop would be used for production. Students would gradually migrate from one to the other. Is there a reason to abandon this framework? Hence I agree with Gonzalo that we need to not distort Sugar's goals to service professional production values. -walter Gonzalo Tony On 05/23/2015 06:00 PM, sugar-devel-requ...@lists.sugarlabs.org mailto:sugar-devel-requ...@lists.sugarlabs.org wrote: Message: 6 Date: Sat, 23 May 2015 08:11:54 + From: tkk...@nurturingasia.com mailto:tkk...@nurturingasia.com To: Sebastian Silva sebast...@fuentelibre.org mailto:sebast...@fuentelibre.org, tkk...@nurturingasia.com mailto:tkk...@nurturingasia.com, sugar-devel@lists.sugarlabs.org mailto:sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop Message-ID: W6839625023265491432368714@atl4webmail07 Content-Type: text/plain; charset=windows-1252 Thanks for the feedback. Just that I have been testing other people web applications (and saving me time) with docker that I feel perhaps a kid with an XO can do the same and learn something with lighter weight virtualization. Hope some developer can take up Sam's and your recommendation of Flask. Cheers -Original Message- From: Sebastian Silva [mailto:sebast...@fuentelibre.org mailto:sebast...@fuentelibre.org] Sent: Saturday, May 23, 2015 03:55 PM To:tkk...@nurturingasia.com mailto:to%3atkk...@nurturingasia.com,sugar-devel@lists.sugarlabs.org mailto:sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] Docker in Sugar/XO laptop On 23/05/15 02:00,tkk...@nurturingasia.com mailto:tkk...@nurturingasia.com wrote: Hope it makes sense:-) It still doesn't, to me at least. It's sounds like you are saying you want to run any linux distro on virtualbox on xo. It would be pointless waste of machine resources because you are already running a linux distro. You can write full, professional web apps from Pippy, if you have access to one or two extra python packages ( personal favorite, try Flask http://flask.pocoo.org/ ). The trick is getting to them, which is why Sam's proposal is quite good, access to the Python Package Index from Pippy... -- I+D SomosAzucar.Org icarito #somosazucar en Freenode IRC Nadie libera a nadie, nadie se libera solo. Los seres humanos se liberan
Re: [Sugar-devel] [Sugar-news] Sugar DIgest 2015-05-26
I never had to chance to meet Marco but I can say that I only have heard wonderful things about him, as a human being and as an engineer. My most sincere condolences to his family and friends. On Tue, May 26, 2015 at 5:07 PM, Christoph Derndorfer christ...@olpcnews.com wrote: On Tue, May 26, 2015 at 3:28 PM, Walter Bender walter.ben...@gmail.com wrote: 1. It is with great sadness that write these words: Marco Presenti Gritti, the principal Sugar developer from Red Hat from 2006 to 2008 and one of the founders of Sugar Labs, passed away this past weekend after a long illness. Marco was a brilliant engineer whose work still reverberates throughout the Sugar stack and a warm, personable colleague, father, and husband. We will miss you Marco. Thank you for sharing this sad news which I - and I assume many others here - would have missed otherwise. Reading it made me go back through my e-mail and photo archives and I found this shot from FUDCon Brno in September 2008: [image: Inline image 1] I'll always remember mpg like that: A brilliant and cheerful software engineer amidst like-minded and equally friendly and dedicated software geniuses who built the foundations of Sugar. And +1 to Gonzalo's suggestions of dedicating 0.106 to Marco and his young family! If anyone has his physical address please let me know as I'd love send my condolences to his two Danielas in this time of sadness and mourning. Christoph == Sugar Digest == 2. For those of you who are interested, we hold our GSoC group meetings on Fridays, 11:00 EST (Boston), 14:00 UTC on irc.freenode.net #sugar-meeting. === Tech Talk === 3. Peter Robinson, Sam Parkinson, Sean Daly, and Iain Brown Douglas have done a great job of revamping the Sugar on a Stick spin site for Fedora. Please see [1]. === Sugar Labs === 4. Please visit our planet [2]. --- [1] http://spins.stg.fedoraproject.org/en/soas/ [2] http://planet.sugarlabs.org -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Community-news mailing list community-n...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/community-news -- Christoph Derndorfer volunteer, OLPC (Austria) [www.olpc.at] editor, OLPC News [www.olpcnews.com] co-founder, TechnikBasteln® [www.technikbasteln.net] e-mail: christ...@derndorfer.eu ___ Community-news mailing list community-n...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/community-news ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar all-hands meeting
I know there have been various board and development meetings for Sugar. But I would like to propose having an all-hands meeting where anyone in the Sugar community as well as related groups (deployments, schoolserver, etc.) could raise a topic and attend. If there are few enough people, we might be able to do this with a Google Hangout. For larger crowds we should try to get permission to use an international conference bridge (to avoid a dozen echo cancelers getting confused by each other). There are a lot of things that need to be done that I suspect could happen given a wider audience. --- SJG ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] Sugar all-hands meeting
On Tue, May 26, 2015 at 6:28 PM, Samuel Greenfeld sam...@greenfeld.org wrote: I know there have been various board and development meetings for Sugar. But I would like to propose having an all-hands meeting where anyone in the Sugar community as well as related groups (deployments, schoolserver, etc.) could raise a topic and attend. If there are few enough people, we might be able to do this with a Google Hangout. For larger crowds we should try to get permission to use an international conference bridge (to avoid a dozen echo cancelers getting confused by each other). There are a lot of things that need to be done that I suspect could happen given a wider audience. What topics are you proposing to address or outline in such a call? Ultimately a all hands call needs to be well overseen to ensure that it's actually effective. I think the first part of that is to define what needs to be covered on such call. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
