Search results

Jump to navigation Jump to search
  • Thank you to everyone who applied for GSoC this year. Here are some comments: == Competing proposals ==
    3 KB (463 words) - 11:25, 10 April 2009
  • ...any case we'd like to talk to you about participating in Sugar outside of GSoC. ...gh we can't give you a slot, you can also contact us on the sugar-devel or gsoc mailing list and we'll work something out.
    4 KB (561 words) - 15:22, 15 April 2009
  • ;2009-04-03 ;2009-04-12
    8 KB (1,277 words) - 12:07, 26 April 2009
  • ...w your creativity—combine the best aspects from the pool. Bring your proposals to the community, developers, and potential mentors (not limited to [[Summe ...you do to ensure that your accepted students stick with the project after GSoC concludes?
    2 KB (309 words) - 20:30, 10 March 2010
  • ;2009-04-03 ;2009-04-12
    13 KB (2,056 words) - 12:28, 30 September 2009
  • ...to everyone who participated in the selection process—the feedback on the proposals from the community has been especially of great value. Kudos to Jamison Quinn for organizing our GSoC efforts and seeing to all of the details. Finally, thanks once again to Goo
    6 KB (1,034 words) - 19:37, 27 July 2010
  • ...e developers to our project. We've had great success in the past with both GSoC and Google Code In in identifying and retaining talent that has had signifi ...appoint some of the participants from Google Code In—too young to apply to GSoC—as Sugar Labs “mentors in training”, sharing their experiences and le
    8 KB (1,240 words) - 04:50, 31 March 2013
  • [[Category:2010 GSoC applications]] [[Category:GSoC]]
    12 KB (1,999 words) - 08:01, 9 April 2010
  • :'''<walterbender>''' mchua: as per the wiki: TM, ASLO, GSoC, Goals :'''<mchua>''' has two proposals + poll results.
    18 KB (3,215 words) - 00:21, 2 March 2011
  • ...both a proposer and seconder from among the members of the board. Several proposals that were not taken as motions are shown here struck out, as in <s>MEMBER M ;PENDING MOTION 2019-01: Preserve the unpaid GSoC 2018 stipend for marketing purposes, and thank the mentors who suggested th
    50 KB (7,772 words) - 16:47, 11 November 2020
  • ...plaining how they use Sugar and read some [http://olpc-ceibal.blogspot.com/2009/01/anecdotes-of-plan-ceibal-in-durazno.html stories from the field].<BR CLE ...cation period for Google Summer of Code 2016 has ended. We have 62 project proposals, which we will vet over the next few weeks. Thanks to the applicants and co
    16 KB (2,491 words) - 11:29, 18 May 2016
  • ...ich were misplaced in a pootle migration. Etoys has not been updated since 2009 and the localization files are no longer available in Pootle, but we do hav ...(Python) activities to see if they support Pootle and attempt, eg. through GSOC, to get activities upgraded to implement Pootle and to include a base set o
    20 KB (3,239 words) - 22:41, 6 June 2016
  • This page contains a list of project ideas. For now, the focus is on giving [[GSoC]] students an idea of the kind of thing we're looking for. Summer of Code a ...ummarize that thread: the highest priority is for you to have a successful GSoC, which should bias you towards easier projects such as [[#Stand-alone activ
    38 KB (5,778 words) - 20:38, 22 December 2016
  • ;what we have been working on:quashing Music Blocks bugs, preparing tasks for GSoC, project mining, clean up activity metadata format, moved more of developer ...h visualisation, Clock activity user documentation, and creating tasks for GSoC.
    59 KB (8,636 words) - 17:29, 10 April 2018