Difference between revisions of "Historical:Google SoC 2007"

From PanoTools.org Wiki
Jump to navigation Jump to search
Line 5: Line 5:
 
* fill in the application
 
* fill in the application
  
−
===Application Summary (pls. don't edit this section)===
+
===Talk===
 +
discussions at http://lists.sourceforge.net/lists/listinfo/panotools-devel
  
−
  1.  Describe your organization.
+
===Application===
−
  2. Why is your organization applying to participate in GSoC 2007? What do you hope to gain by participating?
+
feel free to work on the [[SoC2007_application|application]] text. every contribution / idea is welcome.
−
  3. Did your organization participate in GSoC 2005 or 2006? If so, please summarize your involvement and the successes and failures of your student projects.
 
−
  4. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
 
−
  5. Who will your organization administrator be? Please include Google Account information.
 
−
  6. What license does your project use?
 
−
  7. What is the URL for your ideas page?
 
−
  8. What is the main development mailing list for your organization?
 
−
  9. What is the main IRC channel for your organization?
 
−
  10. Does your organization have an application template you would like to see students use? If so, please provide it now.
 
−
  11. Who will be your backup organization administrator? Please include Google Account information.
 
−
  12. Who will your mentors be? Please include Google Account Information.
 
−
  13. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
 
−
  14. What is your plan for dealing with disappearing students?
 
−
  15. What is your plan for dealing with disappearing mentors?
 
−
  16. What steps will you take to encourage students to interact with your project's community before, during and after the program?
 
−
  17. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
 
  
−
===Application Text===
+
===Project Ideas===
 +
feel free to add / specify the [[SoC2007_projects|projects]] ideas.
  
−
feel free to work on the [[SoC2007_application|application]] text. every contribution / idea is welcome.
+
===Students===
 +
* join the mailing list at http://lists.sourceforge.net/lists/listinfo/panotools-devel
 +
* read the [[SoC2007_projects|projects]] ideas.
 +
* take ownership of one of them. Contact the mentioned mentor or the overall list if the mentor is not fixed.
 +
* refine the idea, add detail, describe what you intend to do and how.
  
−
===Project Ideas===
+
===Mentors===
 +
* join the mailing list at http://lists.sourceforge.net/lists/listinfo/panotools-devel
 +
* read the [[SoC2007_projects|projects]] ideas.
 +
* take mentorship of at least one of them.
 +
* ideally we want two mentors per project. get in touch with the other mentor and with the student.
 +
* if there are no other mentors or student, help moving forward the recruiting effort.
  
−
feel free to add / specify the [[SoC2007_projects|projects]] ideas. Candidates: you are welcome to enlist yourself for the ideas, take ownership and run with them.
+
===Organizers===
 +
* join the mailing list at http://lists.sourceforge.net/lists/listinfo/panotools-devel
 +
* read the [[SoC2007_application|application]] text.
 +
* add and contribute to it
 +
* read the [[SoC2007_projects|projects]] ideas.
 +
* see if you can recruit relevant experts to the steering committee
  
 
===Steering Committee===
 
===Steering Committee===

Revision as of 17:45, 19 February 2007

This is the work in progress for the Google Summer of Code application.

Deadlines

  • application as mentoring organization 5-mar-2007 - 12-mar-2007
  • fill in the application

Talk

discussions at http://lists.sourceforge.net/lists/listinfo/panotools-devel

Application

feel free to work on the application text. every contribution / idea is welcome.

Project Ideas

feel free to add / specify the projects ideas.

Students

Mentors

Organizers

Steering Committee

Who should we invite to the organization/steering committee? what will be their role?

  • project leaders of hugin / panotools / tlalli
  • community leaders (NG / Verein / WorldWidePanorama / IVRPA)
  • academics

goal: broad and relevant support.

role: steer the work of the mentors. shape the projects. make sure the mentors are there for the students. solve interpersonal issues (organizers-mentors-students). give direction.


Invite text draft

Dear ###NAME###

We are setting up an organization to attract Google's sponsoring within its Summer of Code initiative. We hope to obtain sponsoring of projects intended to improve different areas of Open Source panorama creation software. Read more about Google's SoC at ###LINK###

For such projects to be successful they need expert guidance. This is why within that organization we have planned a steering committee. We have thought of you because of your experience, contribution and reputation in the panorama photography world, particularly ###INSERT SPECIFIC REASON HERE###. We believe you could contribute to the steering committee and help guide the projects, if incepted and sponsored by Google, to a successful end, and we hereby invite you to become a member of our steering committee.

The steering committee will hopefully steer a team of mentors. Their number will depend on the number of individual sub-projects that we can get sponsored. Pablo d'Angelo (maker of hugin, the most advanced Open Source stitching software) has initiated a list of potential sub-project. He will also mentor at least one student. The requirements of SoC is to have at least a backup mentor and an administrator. The administrator will liaise between Google and the project. Moreover we forsee within our organization the administrator to liaise between the steering committee, the project and the students. We are working on staffing the team, working out the details of the sub-projects to submit them to Google's program and looking out for qualified students for these internships.

We invite your input from this early stage because we believe that you have relevant expertise and knowledge. Whether it's project ideas, contacts or potential students, we value all input you can provide us.

Our first deadline is the week of march 5-12. It is during that week that Google will accept application from mentoring organizations, and it is by then that we need to have the organization set up. If you accept our invitation, please let us know asap so that we can include you in the organization's description. For this we would also need a short bio.

If you have further questions, do not hesitate to contact ###WHO?###

We hope that you have benefited in the past from panorama related Open Source code such as the panotools and hugin and that your contribution will help us provide you with even better software in the future.

Kind Regards

the ###SIGNATORIES###

Mentors

volunteers? please specify why you are qualified and what is your current day job as well as position in the panorama community, particularly development.

role: mentor the students.

Organizers

volunteers? please specify why you are qualified and what is your current day job as well as position in the panorama community, particularly user community.

role: communicate with google. organize the steering committe. monitor the mentors.

Students

volunteers?

Retrieved from "https://wiki.panotools.org/index.php?title=Historical:Google_SoC_2007&oldid=7803"