MeeGo is an open source project created by merging the Moblin and Maemo software platforms, producing a state of the art Linux stack targeting hardware platforms such as netbooks, handhelds, in-vehicle infotainment devices, connected TVs and media/smartphones. We, the MeeGo community, are made up of all the people who collectively work on or with Meego: platform and application developers, users, vendors, and other contributors; currently we have more than 18000 registered members, and are enlarging daily. MeeGo's governance model is based on a meritocracy.
We value the work that has been done in previous Google Summer of Code events, and we believe they have had a measurable positive effect in the participating organizations by providing them with much required help and resources. We also have already seen some students interested in participating in a potential MeeGo participation in the Summer of Code.
Bringing new, talented developers with their innovative ideas to MeeGo is also one of our main objectives. Just by trying to participate in GSoC we are already seeing the benefits, as everyone has tried to brainstorm and document his best ideas.
There's lots of smaller projects happening around our community that so far have been entirely built by a single developer, and we have seen past GSoCs encouraging collaboration with those smaller project and students that were interested in them. This benefits not only the project itself but also all of the developers involved,as everyone wins experience in open source team work.
We have not formally participate in any previous GSoC. However, many of us come from the maemo.org community which successfully participated in the 2007, 2009 and 2010 editions. Most of the projects ended correctly and the community is enjoying the applications and enhancements that were developed as part of our involvement with the program.
We didn't participate; however, maemo.org did with the following ratios: 2010: 9/10 2009: 10/10 2007: 3/5 (this must be a "short answer")
http://wiki.meego.com/GSoC_2011/Ideas
The main MeeGo development mailing list address is: meego-dev@meego.com
All MeeGo community mailing lists can be found at: http://meego.com/community/mailing-lists
The main forum for discussing MeeGo community-related topics is: http://forum.meego.com/
Yes.
Student Template:
* Project title * Project abstract (very short description) * Project full description * Project tasks and deliverables * Project schedule * Do you have any other commitments during the summer of code coding period? If yes, what kind of commitments? * Why do you believe you the right person for this project? * What are the benefits of your project for the MeeGo Community? * Contact information (email/IM handle/IRC nickname). * Short biography (academic or professional work, your open source background or other activities you've done that you'd like us to know)
Most of the current individuals are established members with years long records of participation in either maemo.org or MeeGo development. A big majority are former GSoC mentors or students (not necessarily from either MeeGo or maemo.org). They have proven track records in the open source world.
We will also strive to assign to approved projects the most knowledgeable mentors in the areas each project is about.
Our first step will be a careful selection process; we do not want to overload a student with more work than what we believe he might been able to do. Since some of us are past students, we have experience with the amount of work that needs to be done and can provide estimates.
Our second step will be to encourage students to publish and advertise their work and progress in the open. This way, public interest in their projects or comments from users and other community members will encourage to continue with their work. Also, the mentor will be able to monitor the student's progress so that issues are discovered as quickly as possible.
We expect project schedules to be realistic; during the first weeks of the coding period students and their mentors are encouraged to review and adapt them as they see fit.
Every selected project will have at least one backup mentor; in case problems with the primary mentor arise. The organization administration members will also be in touch with all of the mentors in order to provide help and assistance throughout the duration of the project, to avoid possible problems as soon as possible.
We will encourage all of the students to get involved in our mailing lists and IRC channels as soon as possible. Their ideas will be posted to the same lists active and established community members post so that lively discussion appears around them. Students will be able to look to other student's proposals as well as MeeGo work being done in the open, so they will be able to properly grasp the projects the community would like, those that are already being worked on as well as get a sense of the amount of work that would need to be done for each of them.
During the coding period, we will encourage students to advertise their work on their personal blogs (which will be aggregated), so that they get fresh opinions from the community. We will also request them to post their problems and thoughts with MeeGo development on the standard mailing lists, so that will be able to discuss with existing contributors.
N/A
N/A
I (javispedro) participated in the maemo.org 2010 GSoC, as a student. I hope this is proof enough that past GSoC students stick with the project :).
User:Javispedro (link_id: javispedro)
User:Andre (link_id: andreklapper)