[IAEP] SL GSoC proposal text
walter.bender at gmail.com
Fri Feb 3 14:26:07 EST 2017
As per the request at the SL overight board meeting: please see the
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
Why does your org want to participate in Google Summer of Code?
GSoC is a great opportunity to both broaden the reach of our community, but also a place to take risks on new ideas that could lead to new directions for the program. For example, for the past two years we mentored a project on programming and music that has turned into a major initiative. GSoC has also been instrumental in helping us reach beyond the desktop onto other platforms, such as Android and Chromium. Plus it is a good way to engage the existing community around these initiatives.
How many potential mentors have agreed to mentor this year?
How will you keep mentors engaged with their students?
We have weekly group meetings and individual meetings between mentor teams and students.
How will you help your students stay on schedule to complete their projects?
In their proposals, students must present a detailed weekly plan. Each student makes a weekly report at our group meeting. They report what they did, what worked, what didn't, and what is queued up for the next week.
How will you get your students involved in your community during GSoC?
We conduct all of our meetings in our public IRC channel. Also, students will send regular blog reports to the community as a whole.
How will you keep students involved with your community after GSoC?
We've had great success in keeping students involved (as mentors in GCI, for example.) Because Sugar is a community project, many of our students do local projects as well. Some former GSoC students are also now GSoC mentors.
Has your org been accepted as a mentor org in Google Summer of Code before?
Which years did your org participate in GSoC?
For each year your organization has participated, provide the counts of successful and total students. (e.g. 2016: 3/4)
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?
Anything else we should know (optional)?
We are a member project of the Software Freedom Conservancy. We just completed a very successful GCI experience.
We make tools that learners use to explore, discover, create, and reflect.
A very short description of your organization.
Your organization logo. Must be a 24-bit PNG, minimum height 256 pixels.
Primary Open Source License
GNU General Public License version 3.0 (GPL-3.0)
The open source license that your organization uses.
Programming Languages and Development Tools
Select which category fits your organization best. Some organizations may fit into multiple categories, you must choose one. Used to help students filter the organization list.
Enter a technology tag
learningRemove Press delete to remove this chip. educationRemove Press delete to remove this chip.
Enter a topic tag
Enter keywords for general topics that describe your organization. Examples: Vision, Robotics, Cloud, Graphics, Web, Real time
Enter the URL of your Ideas List page. This will be linked from your organization page.
These descriptions will be displayed on the organization list page (Short Description) and on your organization's page (Long Description). More details.
The Long Description may include limited Markdown.
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.
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.
Guidance for students on how to apply to your organization. Should include any prerequisites or requirements. You may wish to include a template or tips for their proposals. May include limited Markdown.
Enter tags that students can select (one) from and apply to their own proposals to help organize them. Examples: New Feature, Optimization. You can also use these to designate "sub-organizations" if you are an umbrella organization.
Welcome to GSoC 2017
Sugar Labs expectations
* We expect you to be playful, inquisitive, and diligent;
* GSoC is a full-time commitment; unless you are prepared to work full time, 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 2017](https://wiki.sugarlabs.org/go/Summer_of_Code/2017).
+ Add tag
You must complete at least one of the following three contact options.
Link to a web page that describes how to get on your IRC channel or other realtime communication system.
Link to a page describing how to join your organization's mailing list.
walter at sugarlabs.org
A general purpose contact email for your organization.
Google+ URL (optional)
Twitter URL (optional)
Blog URL (optional)
More information about the IAEP