[IAEP] Updates of Sugar Labs' finances?
Hi all, reading through Sean's Marketing Team Report I remembered the Finances page (http://wiki.sugarlabs.org/go/Finance) and went there to see what the current status was. Unfortunately the page hasn't been updated since late April and it's still not clear how the ~$19,000 in the bank as of January are earmarked. I think Sean raises good points about the resources constraints holding Sugar Labs back in many ways. Hence I think knowing what we actually do have in the bank should be a starting point for figuring out what we want to do with what we have:-) Cheers, Christoph -- Christoph Derndorfer editor, OLPC News [www.olpcnews.com] volunteer, OLPC (Austria) [www.olpc.at] e-mail: christ...@derndorfer.eu ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] team updates
On Thu, Sep 08, 2011 at 07:58:29PM +, Aleksey Lim wrote: Hi all, In fact, the original request cannot be considered as a fully valid in case of Platform Team. The http://wiki.sugarlabs.org/go/Platform_Team page exists but Platform Team is in initiation stage and wasn't somehow announced or requested to be a Sugar Labs Team. In any case, it is the right moment to do that. The purpose to create this team might be found of its mssion page http://wiki.sugarlabs.org/go/Platform_Team/Mission, i.e.: The general goal is to support Sugar doers in their regular behaviors within the Sugar ecosystem by providing a seamless environment by which to follow a common strategy. In other words, it is exactly about having a platform that supports Sugar doers. There are key differences with the existing teams: * Compared to the [[Activity Team]], the Platform Team does not care about developing any particular activities, but rather provides a useful software infrastructure to help people in the activity development process. * Compared with the [[Development Team]], the Platform Team does not care about developing the Sugar learning environment (Sucrose), but rather provides a useful software architecture to help as many people as possible to take part in the Sucrose development process. * Compared with the [[Infrastructure Team]], the Platform Team does develop some of the services that the [[Infrastructure Team]] administers. In particular, the Platform Team will * Support ''doing'' behaviors by providing useful [[Platform_Team/Sweets|distribution method]]s and various Sugar Doers' Kits (that really sounds better than the traditional SDK transcription, Software Developers Kit). * Connect doers and other learners (users) by developing services for a seamless infrastructure for sharing software, e.g., [[Activity Library]]. * Extend the previous two goals to non-Sugar environments, not to ''sugarize'' them all, but rather to merge and promote Sugar software with and within the common [http://en.wikipedia.org/wiki/Free_software Free Software] and education ecosystems. As you can see there is a clear difference in goals with existed teams (mostly with development related ones). In my mind, such team needed to be created right after Sugar Labs initiation because it is critically important (for Sugar Labs mission, how I understand it) to provide reliable doing platform for heterogeneous ecosystem that Sugar is, i.e., it might be not such in case of particular XO based deployment, but on Sugar Labs level it is such. For example, being an Activity Library administrator (and a technical maintainer for now), I can say that any not pure Python activity is less (if activity developers take care about providing all possible variants of their activity, but it is very exhausting and unreliable way in GNU/Linux world) or more (if activity developers just place the variant of activity that was built in their environment, i.e., in most cases it won't work in different cases). And that is the exact task for Platform Team that will do a work that will be used by activity developers. An update for goals. == Shot-term goals == * Activity Library related tasks: ** polish the [[Activity_Library/Editors/Policy|Policy]], ** start discussion on MLs, ** land it. == Medium-term goals == * Work with [[Infrastructure Team]] on the Central Login system to make it possible to be logged in only once while browsing Sugar Labs resources. * Develop an infrastructure to share logs on activity fails. * Develop an infrastructure to share anonymous usage statistics on Sugar Labs level, i.e., not only for particular deployment. * See around for ways how Sugar objects (Journal objects, .xol, etc) might be shared. The requested roadmap for Platform Team is http://wiki.sugarlabs.org/go/Platform_Team/Roadmap but it lacks of answers for: What does the team see as its constraints from being more successful in its Mission? What are you doing to try to resolve the constraint? What can Sugar Labs 'central' or the community do to help? since Platform Team is in initiation team and the only issue is the lack of contributors interested in taking part in Platform Team projects. An update for constraints. The most [not-only-technical] critical constraint related to the Activity Library is a lack of editors and the fact that all active editors are techinical people. In other words, it relates to the 3rd point from What can Sugar Labs 'central' or the community do to help? Marketing Team Report, i.e., it would be useful to have common strategy, created in cooperation with Education Team, that covers such important resources like Activity Library. And, eventually having educators as Activity Library editors. -- Aleksey
Re: [IAEP] [SLOBS] meeting reminder
On Mon, Sep 12, 2011 at 12:27 PM, Walter Bender walter.ben...@gmail.com wrote: We will be having a Sugar Oversight Board meeting on Thursday, 15 September, at 15:00 UTC on ircr.freenode.net #sugar-meeting. Topics include: * Team updates * Local labs updates * some outstanding GSoC business Please let me know if you will be attending. My apologies, but I got the dates mixed up. In all previous correspondence about this meeting, we had agreed it would be on the 16th. I think we should stick to the original date as I am hearing from people that they had freed up that timeslot. I'll be hanging out in #sugar-meeting today in case anyone wants to chat about the various topics in advance of the meeting. -walter PS: UTC 15 is 11AM EST at the moment (according to timeconverter) regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] Activity Team Report
Sugar Teams Update Report, September 2011 Name of team: Activity Team Mission statement: The Activity Team develops and maintains many of the activities available for Sugar. We encourage independent developers to write and maintain activities, and we support them in their efforts. Our goal is to ensure that Sugar provides a complete set of high quality educational, collaborative, constructivist activities. Short Term Goals (three–six months): 1. Finish implementation of the UI review with guidance of the Design Team. 2. Write a criteria for inclusion of activities into the core activities group. 3. Create a list of core activities, with the maintainers responsible for each one of them. 4. Re-start Activity Team IRC meetings. 5. Look to the Development Team for a best practice recommendation for GTK3, PyGI activity migration and Sugar 0.96 red flag day changes. Medium Term Goals (6 months–one year): 1. Promote co-maintainership of Core Activities. 2. Identify code repeated in activities, and useful in sugar-toolkit, and help to improve it, doing easier the work to activity developers. 3). Try to gather more feedback on actual activity use by children in deployments to help focus development effort (Journal metadata analysis, teacher feedback, deployment team feedback). 4). Look to the Design Team to help work towards adoption of UI changes needed for the support of touch based interfaces. Long Term Goals (one year–three years): 1. Design, develop, or support an activity (or Sugar shell component) useful to edit/create activities. What does the team see as its constraints from being more successful in its Mission? Finding developers willing to maintain activity code over the longer term. What are you doing to try to resolve the constraint? We will restart periodic IRC meetings (probably once a fortnight) to try and re-engague activity developers. What can Sugar Labs 'central' or the community do to help? Get involved in some way with Activity testing, review, feedback, opening bug or enhancement tickets, documentation, lesson plan writing, video tutorials – so that activity developers are not working in a vacuum. More feedback from the bottom up would be wonderful (children/teacher/deployment - activity developers) Gonzalo Gary ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [support-gang] Problems!
Hi Again, I ran the test and found that the culprit is the 2 key, as I suspected. I have no qualms about dis-assembly and messing with the keyboard (done it before... remember my wiki article on Keyboard Field Repairs? http://wiki.laptop.org/go/Keyboard_field_repairs ). I left all my tiny screwdrivers in CA so I may have to take the machine with me... maybe Ed (my husband) has some small ones here I can borrow. I would prefer to return it to the CP here in MT in working condition before I head back to SoCal. When I ran the test, it indicated another problem... something about 5 Bad blocks in NAND flash or something like that, it flew by really fast). Is this something that I need to worry about? Will it cause problems? I'll try the fixes referred to in the wiki article and the links there. They are all pretty old. Does anyone have anything new to add? If this doesn't work, I'll take it home and, maybe let the kids in one of the other CP projects I work with fix it. They are just getting started on that sort of stuff. http://famliolpcsocalaudubonms.wordpress.com/ Thanks for all the help. This is part of what makes volunteering with OLPC and Sugar Labs so much fun! Caryl Date: Thu, 15 Sep 2011 10:42:13 -0400 From: nathanr...@charter.net To: support-g...@lists.laptop.org Subject: Re: [support-gang] [IAEP] Problems! On Thu, Sep 15, 2011 at 3:32 AM, John Watlington wrote: On Sep 15, 2011, at 2:58 AM, Kevin Mark wrote: This brings to mind the wiki page for 'sticky keys'. my xo-1 and other xo-1s has this keybaord that had keyboard issue like you described. Sometimes messaging the keys works, sometimes playing with the membrane, or other ideas on the wiki page and of couse replacement. if you attached a USB keyboard, could that override the internal to access OFW? I don't believe so. The damaged keyboard would continue to insert keypress events into the input stream. the OFW keyboard testa (test /keyboard?) would show the issue if you could get to it I'm guessing. You should be able to enter hardware self-test by holding down the check key (to the far right of the display). It eventually gets around to testing the keyboard.Early versions of OFW may not support this. Use the hardware tests --- hold down left rocker on power on. This is OFW function and not linux. The keyboard test that runs at the end will show stuck keys. Try each key to see if you can catch it. Most often it is one of the keys near a corner, especially the lower left corner. Stuck or intermittent alt or ctrl gives strange results. Glue is used on the areas between the keys and sometimes it gets in the key area. The lower left is probably a start or stop point for gluing. The corners can be accessed from the rear of the keyboard and the key area swabbed with a q-tip moistened with rubbing alcohol (70 % isopropyl alcohol) to remove the glue, but this does leave the surrounding areas unglued, which generally does not cause a problem. This is NOT recommend for someone not comfortable with disassembly. Nate ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ support-gang mailing list support-g...@lists.laptop.org http://lists.laptop.org/listinfo/support-gang ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
