200
edits
Changes
GSoC 21' SL application (view source)
Revision as of 11:12, 27 February 2021
, 11:12, 27 February 2021Created page with "== Organization Application == === Why does your org want to participate in Google Summer of Code? === In Sugar Labs, we applaud the essence of collaboration between existin..."
== Organization Application ==
=== Why does your org want to participate in Google Summer of Code? ===
In Sugar Labs, we applaud the essence of collaboration between existing member of the organisation and potential new contributors. GSoC is a program that brings together a lot of students who can become long term contributors to the program. On the part of the students, getting the opportunity to contribute to an open source project like the projects we have in Sugar Labs, they will gain more experience and get to work on amazing & exciting projects.
=== How many potential mentors have agreed to mentor this year? ===
11-15
=== How will you keep mentors engaged with their students? ===
Mentors have daily meetings with their students. We also hold group meetings regularly (every week) where all mentors and students get to connect and share project updates. We use our mailing list and IRC as our primary communication channel this helps the students to not only connect with mentors but the Sugar Labs community at large.
=== How will you help your students stay on schedule to complete their projects? ===
The student may seek help from the Sugarlabs community via the mailing list or IRC channel. We have a brilliant and welcoming community who is always willing to help. We advise all students to post weekly progress to the mailing list and keep the community updated. In Addition to that, we expect students to be in constant touch with their mentors and document their progress on the project. At the daily meetings with their mentors, we discuss progress, roadblocks, etc.
=== How will you get your students involved in your community during GSoC? ===
Students join a group meeting once per week and also send a report in the form or either a blog or email to the developer community.
=== How will you keep students involved with your community after GSoC? ===
We have a pretty good track record of students becoming mentors in subsequent years. But the real draw is seeing one’s work being used in the community. So we try to ensure that students have some level of engagement with Sugar users. (For example, the students who work on Music Blocks also run Music Blocks classes.) Students are welcome to join discussion meets that happen every 15 days where they get to see the bigger picture and impact their project had.
=== Has your org been accepted as a mentor org in Google Summer of Code before? ===
Yes
=== Which years did your org participate in GSoC? ===
2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, , , ,
=== How many students did your org accept for 2020? ===
9
=== How many of your org's 2020 students have been active in your community in the past 60 days? ===
5
=== For each year your organization has participated, counts of successful and total students: ===
2013: 8/8 2014: 9/9 2015: 6/6 2016: 5/6 2020: 9/9
=== If your org has applied for GSoC before but not been accepted, select the years: ===
-
If you are a new organization to GSoC, is there a Google employee or previously participating organization who will vouch for you? If so, please enter their name, contact email, and relationship to your organization. (optional)
-
=== What year was your project started? ===
2008
=== Where does your source code live? ===
https://github.com/sugarlabs
Refer an organization (optional)?
-
=== Is your organization part of any government? ===
No
Anything else we should know (optional)?
-
== Organization Profile ==
=== Tagline ===
We build and maintain tools that learners use to explore, create, and reflect.
=== Short Description ===
We make tools that learners use to explore, discover, create, and reflect. We encourage our users to appropriate them, taking ownership and responsibility for their learning.
=== Long Description ===
Sugar Labs, a volunteer-driven, non-profit organization, had its origins in the One Laptop Per Child project and is has been a member project of the Software Freedom Conservancy since 2008.
At Sugar Labs, we make a collection of tools (Sugar) that learners use to explore, discover, create, and reflect. We distribute these tools freely and encourage our users to appropriate them, taking ownership and responsibility for their learning.
Sugar is both a desktop and a collection of Activities. Activities, as the name implies, are Apps that involve active engagement from the learner. Activities automatically save results to a journal, where reflections are recorded. Activity instances can be shared between learners; many support real-time collaboration.
Sugar facilitates sharing and collaboration: Children can write, share books, or make music together with a single mouse-click.
Activities, not applications: Sugar activities are applicable beyond the scope of the classroom and even Sugar itself.
Automatic backup of Activity work; no worrying about files or folders. Sugar’s Journal makes it almost impossible to lose any data.
The Sugar Journal records everything you do: It is a place to reflect upon and evaluate your work.
Sugar runs on most computer hardware, including slower machines.
Sugar is Free (Libre) Software: It is written in the Python language and easily customized.
Sugar is documented by its users: It is easy to use and teachers worldwide have created a wealth of pedagogical materials for it.
Sugar is largely written and maintained by its users.
Sugarizer is a fork of Sugar available for tablets and phones.
Turtle Blocks and Music Blocks are popular programming Apps that run in Sugar, Sugarizer, or stand-alone on the GNU/Linux desktop or in a Browser.
=== Primary Open Source License ===
GNU General Public License version 3.0 (GPL-3.0)
=== Organization Category ===
end_user_applications
=== Technology Tags ===
python gtk, javascript, react, vue.js, typescript
=== Topic Tags ===
software, education, open source, learning, collaboration
=== Ideas List ===
https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md
=== Application Instructions ===
Application Instructions Welcome to GSoC 2021
Sugar Labs expectations
We expect you to be playful, inquisitive, and diligent;
GSoC is a commitment; unless you are prepared to work dedicatedly, please do not apply;
GSoC is a community effort; be prepared to participate in the broader set of Sugar activities, not just your individual project;
GSoC is only valuable if there is good communication between you, your mentors, and the rest of the community; be prepared to hang out with us on irc.freenode.net #sugar; to meet weekly with all of the GSoC participants; and to communicate daily with your mentors; we also expect a weekly blog about your project.
What to include in your proposal
a clear statement of "what" you intend to do, including weekly milestones;
a clear statement of "why" what you intend to do is of value (personally, to the Sugar project, and beyond);
evidence that you can achieve your stated goals.
For more details, please go to Sugar Labs GSoC 2021
=== Proposal Tags ===
sugar, sugarizer, musicblocks, python, javascript, gtk, react, vue.js, typescript
=== Chat ===
https://wiki.sugarlabs.org/go/Google_Code_In_2019#Getting_set_up_on_IRC
=== Mailing List ===
https://lists.sugarlabs.org/listinfo/sugar-devel
=== Contact Email ===
walter@sugarlabs.org
=== Twitter URL ===
https://twitter.com/sugar_labs
Blog URL
-
=== Why does your org want to participate in Google Summer of Code? ===
In Sugar Labs, we applaud the essence of collaboration between existing member of the organisation and potential new contributors. GSoC is a program that brings together a lot of students who can become long term contributors to the program. On the part of the students, getting the opportunity to contribute to an open source project like the projects we have in Sugar Labs, they will gain more experience and get to work on amazing & exciting projects.
=== How many potential mentors have agreed to mentor this year? ===
11-15
=== How will you keep mentors engaged with their students? ===
Mentors have daily meetings with their students. We also hold group meetings regularly (every week) where all mentors and students get to connect and share project updates. We use our mailing list and IRC as our primary communication channel this helps the students to not only connect with mentors but the Sugar Labs community at large.
=== How will you help your students stay on schedule to complete their projects? ===
The student may seek help from the Sugarlabs community via the mailing list or IRC channel. We have a brilliant and welcoming community who is always willing to help. We advise all students to post weekly progress to the mailing list and keep the community updated. In Addition to that, we expect students to be in constant touch with their mentors and document their progress on the project. At the daily meetings with their mentors, we discuss progress, roadblocks, etc.
=== How will you get your students involved in your community during GSoC? ===
Students join a group meeting once per week and also send a report in the form or either a blog or email to the developer community.
=== How will you keep students involved with your community after GSoC? ===
We have a pretty good track record of students becoming mentors in subsequent years. But the real draw is seeing one’s work being used in the community. So we try to ensure that students have some level of engagement with Sugar users. (For example, the students who work on Music Blocks also run Music Blocks classes.) Students are welcome to join discussion meets that happen every 15 days where they get to see the bigger picture and impact their project had.
=== Has your org been accepted as a mentor org in Google Summer of Code before? ===
Yes
=== Which years did your org participate in GSoC? ===
2020, 2019, 2018, 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, , , ,
=== How many students did your org accept for 2020? ===
9
=== How many of your org's 2020 students have been active in your community in the past 60 days? ===
5
=== For each year your organization has participated, counts of successful and total students: ===
2013: 8/8 2014: 9/9 2015: 6/6 2016: 5/6 2020: 9/9
=== If your org has applied for GSoC before but not been accepted, select the years: ===
-
If you are a new organization to GSoC, is there a Google employee or previously participating organization who will vouch for you? If so, please enter their name, contact email, and relationship to your organization. (optional)
-
=== What year was your project started? ===
2008
=== Where does your source code live? ===
https://github.com/sugarlabs
Refer an organization (optional)?
-
=== Is your organization part of any government? ===
No
Anything else we should know (optional)?
-
== Organization Profile ==
=== Tagline ===
We build and maintain tools that learners use to explore, create, and reflect.
=== Short Description ===
We make tools that learners use to explore, discover, create, and reflect. We encourage our users to appropriate them, taking ownership and responsibility for their learning.
=== Long Description ===
Sugar Labs, a volunteer-driven, non-profit organization, had its origins in the One Laptop Per Child project and is has been a member project of the Software Freedom Conservancy since 2008.
At Sugar Labs, we make a collection of tools (Sugar) that learners use to explore, discover, create, and reflect. We distribute these tools freely and encourage our users to appropriate them, taking ownership and responsibility for their learning.
Sugar is both a desktop and a collection of Activities. Activities, as the name implies, are Apps that involve active engagement from the learner. Activities automatically save results to a journal, where reflections are recorded. Activity instances can be shared between learners; many support real-time collaboration.
Sugar facilitates sharing and collaboration: Children can write, share books, or make music together with a single mouse-click.
Activities, not applications: Sugar activities are applicable beyond the scope of the classroom and even Sugar itself.
Automatic backup of Activity work; no worrying about files or folders. Sugar’s Journal makes it almost impossible to lose any data.
The Sugar Journal records everything you do: It is a place to reflect upon and evaluate your work.
Sugar runs on most computer hardware, including slower machines.
Sugar is Free (Libre) Software: It is written in the Python language and easily customized.
Sugar is documented by its users: It is easy to use and teachers worldwide have created a wealth of pedagogical materials for it.
Sugar is largely written and maintained by its users.
Sugarizer is a fork of Sugar available for tablets and phones.
Turtle Blocks and Music Blocks are popular programming Apps that run in Sugar, Sugarizer, or stand-alone on the GNU/Linux desktop or in a Browser.
=== Primary Open Source License ===
GNU General Public License version 3.0 (GPL-3.0)
=== Organization Category ===
end_user_applications
=== Technology Tags ===
python gtk, javascript, react, vue.js, typescript
=== Topic Tags ===
software, education, open source, learning, collaboration
=== Ideas List ===
https://github.com/sugarlabs/GSoC/blob/master/Ideas-2021.md
=== Application Instructions ===
Application Instructions Welcome to GSoC 2021
Sugar Labs expectations
We expect you to be playful, inquisitive, and diligent;
GSoC is a commitment; unless you are prepared to work dedicatedly, please do not apply;
GSoC is a community effort; be prepared to participate in the broader set of Sugar activities, not just your individual project;
GSoC is only valuable if there is good communication between you, your mentors, and the rest of the community; be prepared to hang out with us on irc.freenode.net #sugar; to meet weekly with all of the GSoC participants; and to communicate daily with your mentors; we also expect a weekly blog about your project.
What to include in your proposal
a clear statement of "what" you intend to do, including weekly milestones;
a clear statement of "why" what you intend to do is of value (personally, to the Sugar project, and beyond);
evidence that you can achieve your stated goals.
For more details, please go to Sugar Labs GSoC 2021
=== Proposal Tags ===
sugar, sugarizer, musicblocks, python, javascript, gtk, react, vue.js, typescript
=== Chat ===
https://wiki.sugarlabs.org/go/Google_Code_In_2019#Getting_set_up_on_IRC
=== Mailing List ===
https://lists.sugarlabs.org/listinfo/sugar-devel
=== Contact Email ===
walter@sugarlabs.org
=== Twitter URL ===
https://twitter.com/sugar_labs
Blog URL
-