Re: [Sugar-devel] Fwd: Google Summer of Code 2009 is a go!
Students working on Sugar related projects don't have to be restricted to Sugar Labs. Two GSoC 2008 students worked on OLPC projects through other mentoring organizations; one through Python and the other I can't recall. If there aren't enough OLPC specific projects, it would still make sense for OLPC students to work on Sugar projects. Though, judging by the number of quality proposals last year, I don't forsee there being any shortage of project ideas. Nirav On Thu, Jan 8, 2009 at 5:26 PM, Ed McNierney wrote: > Yes, but in 2007 "they" were "us", no? > > Thanks, this is helpful information (I didn't know the status of > OLPC's previous GSoC work). I don't see why there is any reason to > presume that OLPC would NOT be interested in 2009 GSoC, but I don't > know of any active ideas/proposals kicking around here. I would > strongly encourage Sugar Labs ideas, however - to Ben's point, there > should be no confusion. The only things I could imagine (and it's > just imagining) coming from OLPC would be ancillary ideas (school > server add-ons?) that would be quite distinct from XO/Sugar software. > Go for it! > >- Ed ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ActivityTeam proposal
Count me in as well. This is a wonderful idea and could very well be what is necessary to make the wish list of Activities proposals real. Nirav On Sun, Jan 11, 2009 at 5:09 AM, Arjun Sarwal wrote: > +1 > I am in too. > > Arjun > > On Sun, Jan 11, 2009 at 3:02 PM, Tomeu Vizoso wrote: >> >> I believe this will make a very big difference in the future of Sugar. >> >> Good luck and have fun, >> >> Tomeu >> >> On Sat, Jan 10, 2009 at 19:46, Wade Brainerd wrote: >> > Hi all, hope you are enjoying FUDcon. >> > >> > Given the recent events at OLPC, I'm planning to refocus my activity >> > development efforts on SugarLabs. I imagine other activity developers >> > are planning to do the same. >> > >> > SugarLabs is off to a great start getting packages into distributions, >> > but I can't help noticing that the activities on the home page are >> > essentially the same were shipped with OLPC build 650 back in 2007. >> > >> > One of the things that drew me to Sugar and OLPC was the promise of >> > high quality, collaborative, constructivist educational software. >> > While the initial activity set was good, it was also clear that there >> > were large holes to be filled. For a variety reasons, many of those >> > holes remain two years later. >> > >> > And that's why I'm proposing the creation of a SugarLabs ActivityTeam. >> > The new team will be separate from the DevelopmentTeam, and will have >> > the responsibility of maintaining and extending the suite of >> > activities available for Sugar. >> > >> > We will: >> > 1. Maintain and develop the current suite of Sugar activities. >> > 2. Recruit and mentor activity developers from the community. >> > 3. Collect, document and organize new activity and activity feature >> > ideas from the EducationTeam, deployments and community. >> > 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure >> > activity developers are well supported. >> > 5. Gather feedback with the DeploymentTeam about how Sugar activities >> > are doing in the field. >> > >> > Until now, activity development has largely been an individual effort. >> > The purpose of this proposal is to collect the activity development >> > community into an effective team who can tackle the entire ecosystem >> > of Sugar activities together. One result should be fewer activities >> > "dropping off the radar" into lack of maintenance. >> > >> > Please respond with your feedback about the proposal. If you like the >> > idea and would like to be part of the ATeam, feel free to indicate >> > that. >> > >> > Best, >> > Wade >> > ___ >> > 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 > > > > -- > Arjun Sarwal > > > ___ > 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] Pippy not ready for Sucrose
PyBox2D is included locally in the activity, just as it is in Physics, x2o, Bridge, and other Activities that use physics. Though, that is ~2.5mB of duplicated libraries for each. Nirav On 1/20/09, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, Jan 20, 2009 at 12:27:08PM +0100, Simon Schampijer wrote: >>the Sucrose package of Pippy is version 25 - when I last released it >>back in August. Since then there has been some development going into >>Pippy (now version 30) >>http://dev.laptop.org/git?p=projects/pippy-activity;a=shortlog >> >>But none of the maintainers did follow the Sucrose release cycle, even >>though I sent a reminder >>http://lists.laptop.org/pipermail/sugar/2008-November/010021.html >> >>Any, specific reason for that? Pippy has not been moved to >>git.sugarlabs.org, as well. > > > (this is related, but does not actually answer above) > > If I recall correctly, recent releases of Pippy depend on box2d which is > not yet packaged for Debian. This means newer Pippy releases will not > work on next official Debian release (codenamed "Lenny"). > > I've tried but have had problems compiling it cleanly using newest gcc > toolchain (if I recall correctly). > > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkl15AEACgkQn7DbMsAkQLi8UACfVUE1Qa6T5fltU5oC55v7aOtq > kMsAoJwujsqw6Y12l50THI+HMWWN331n > =YX2i > -END PGP SIGNATURE- > ___ > 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] Pippy not ready for Sucrose
I prefer to look at it pragmatically. Until there is some kind of dependency handling for .xo packages, this is the difference between a child at an existing deployment being able to browse to the wiki, download an activity, and use it, or not being able to. Nirav On Tue, Jan 20, 2009 at 2:03 PM, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, Jan 20, 2009 at 01:10:11PM -0500, Nirav Patel wrote: >>PyBox2D is included locally in the activity, just as it is in Physics, >>x2o, Bridge, and other Activities that use physics. Though, that is >>~2.5mB of duplicated libraries for each. > > ...which causes such .xo packages to *not* be arch-independent! > > ...and makes bugs in those libraries harder and slower to fix! > > > Also, distributing such .xo packages violates license if not either the > full source is included as well or a written statement promising to > provide sources at no exceptional charge if later requested. > > Distributing binary stuff without its sources is not outright bad, but > more complex and often more cumbersome: It is asking for "surprises"! > > > > - Jonas ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Pippy not ready for Sucrose
Indeed. To bring things back to Pippy, Box2D and pyBox2D are both licensed zlib. Fulfilling the terms of the license is a simple as including http://code.google.com/p/pybox2d/source/browse/trunk/LICENSE somewhere in the .xo. Unfortunately, it seems none of the Activities using PyBox2D are currently doing so. Nirav On Tue, Jan 20, 2009 at 6:24 PM, Chris Ball wrote: > > Not in the case we're discussing; Box2D and pyBox2D are not licensed > under the GPL. While the complaint in general is reasonable, please > don't accuse people of breaching software licenses until they actually > do so. > > Thanks, > > - Chris. > -- > Chris Ball > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC mentors. Also ideas for projects and community-cementing processes.
> I propose that we require two mentors per project, but allow especially > committed people to act as double-mentors (preferably across two projects). > Main mentoring responsibilities should be clearly split up beforehand > between co-mentors (ie, alternating weeks), but both should keep read up > with all communication and be ready to cover for each other (or just add > extra advice) should the need become clear. A "single" mentoring commitment > should expect to be able to handle an average of at least several hours per > week of GSoC-related work; let's say, 4 hours/week minimum available time. The Google end of GSoC is really quite structured to having one mentor per student, in that only one mentor is officially paired to that student, and only that mentor (or the org admin) can submit evaluations. However, I personally experienced the mild frustration of having a disappearing mentor during GSoC 2008, and it is certainly a problem needing solved. Perhaps rather than something like alternating weeks, we could have an official mentor and a "hot spare" mentor who also stays in contact with the student and remains up to date in the event the official mentor disappears. I'd be interested in mentoring. > Name/contact Nirav Patel nrpatel at gmail > Timezone UTC-5 > What kind of projects could/would you mentor? Pygame or PyGTK based Activities > How much time could you devote to mentoring? Can you make the especially > solid commitment of being a double-mentor? What are your other commitments > over the summer? Graduating and no job prospects, so it is likely I will have quite a bit of free time as of early May. 5 hours a week is certainly doable. > What relevant coding experience do you have (very briefly, two sentences at > most)? Some Pygame/PyGTK Activity development and a module for Pygame. > What relevant mentoring (or related) experience do you have? Teaching Assistant and miscellaneous mentoring experiences at school. > Anything else you think is relevant. I survived GSoC on the student end of things in 2008. Nirav ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GSoC Proposal: Multimedia Broadcasting
Geza, Interesting proposal, and certainly a useful Activity to have. Keep in mind though, that Sugar Labs is focusing on development tools and core features more than Activities for this summer. You may also want to take a look at Video Chat [1] for an example of an Activity that had similar goals. Nirav [1] http://wiki.laptop.org/go/Video_Chat On Thu, Apr 2, 2009 at 6:52 PM, Geza Kovacs wrote: > Hi all, > > I am proposing a Multimedia Broadcasting activity for GSoC 2009, and > would appreciate any feedback or potential mentors. The idea is > described at: > > http://wiki.sugarlabs.org/go/Multimedia-broadcasting > > This proposal is somewhat a variation on the standard audio-video > chatting concept; rather than having students audio-video chat > one-on-one, which would be redundant in a classroom where the person is > physically nearby, I believe broadcasting audio and video streams > displaying presentations or live experiments locally to the masses via > streaming on their laptops, thereby replacing the need to use > projectors, would be a good usage of the available video and audio > capture sources, in a classroom setting. For full details please read > the proposal. > > Regards, > Geza > > ___ > 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] A bot activity for sugar
Sounds like cool idea. Just some issues you may run into. IIRC, most of pyglet uses OpenGL, which would require hardware that most of what Sugar runs on doesn't have (XOs, netbooks) or Mesa, which may not be fast enough. Pygame is already a Sugar dependency, but combining pygame with pyGTK in a meaningful way on Sugar is currently an unsolved problem. Combining pyglet and pyGTK may result in similar problems, though I haven't tried it. There are UI libraries for pygame, but using pyGTK with cairo would probably result in a visual style more consistent with the rest of Sugar. Nirav On Tue, Apr 14, 2009 at 7:47 AM, Vamsi Krishna Davuluri wrote: > Hello, > > So I have been working on an IRC bot for a while, and an idea had occurred, > what if we have a graphical bot with a few limited animations for now, make > it an activity, and feed it with help and documentation on every other > activity and itself ofcourse. In the future a language dictionary and such > can be embedded into this bot. > The bot's graphical features can be coded with pygtk(for the widget frame, > text input), some pyglet/pygame for animations > http://pyglet.org > > This will be most entertaining/ fun for any kid. As I remember my own > experiences with such bots from a particular os. Kids love interaction, > graphical interaction is by far the fastest way to plant knowledge about > anything. > > Give me your opinions on this, maybe this will be something I will work on > for sugar in the near future ;) > > Thank you > > Vamsi Krishna Davuluri > > ___ > 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] Wacom Bamboo with XO?
Chris, We're working on switching from gstreamer to the pygame camera module. Gstreamer in 8.2 had some changes that broke the pipeline Colors was using. While it would have been possible to change the pipeline, switching to pygame will be easier/better for both the videopaint and photo snap parts. This will likely be done before the end of the month. Nirav On Mon, Dec 8, 2008 at 8:02 AM, Chris Marshall <[EMAIL PROTECTED]>wrote: > > BTW, Colors! version 11 did not appear to have > the photo snap capability. Was that removed? > > Cheers, > Chris > ___ > Devel mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
