GSOC 2011 Student Application - Revision history

Onomou: /* Set yourself up */ Spelling "Of" -> "If"

2011-04-08T03:55:48Z

‎Set yourself up: Spelling "Of" -> "If"

Habi: Added deadline-details

2011-03-22T22:18:11Z

Added deadline-details

Habi: updated the rest of the page, so it is a bit more coherent.

2011-02-18T17:14:09Z

updated the rest of the page, so it is a bit more coherent.

Habi: /* You */ added link to google group

2011-02-18T17:04:30Z

‎You: added link to google group

Erik Krause: /* Your Project */

2011-02-04T15:50:45Z

‎Your Project

Habi: (Partially) overhauled Student Application from 2009

2011-01-31T17:29:34Z

(Partially) overhauled Student Application from 2009

Habi: Initial copy-paste from 2009

2011-01-31T17:11:14Z

Initial copy-paste from 2009

New page

==You==
Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.

==Your Coding Skills==
If you're adding a project proposal, make sure to let us know what platform you use to code? Tell us about your hardware and operating system. Then we'd like to know a bit more about your coding experience: Did you ever code in C or C++, or are you a guru in some other language?

===Set yourself up===

* Set up your platform to build Hugin, Panotools and Enblend-Enfuse from SVN/CVS. Try to do it based on the instructions listed below.
** Linux: Ubuntu or other, including BSD and other Unix
** Mac OSX
** Windows
* If you decide to work on Lighttwist, ask for help on hugin-ptx.

* If you need help, ask on hugin-ptx.
* Report success on hugin-ptx.
* If you find that the instructions can be improved, get a wiki account and do it, or suggest the improvements on hugin-ptx.
* Produce a patch against Hugin's SVN repository to show proficiency of the toolchain and your coding style. You can find ideas in our tracker, either bug reports or feature requests. Optimize your time, you don't have to impress us. Some ideas are listed in this ToDo List for Student Applicants.
* Publish your patch for peer review on hugin-ptx. We do not consider applications without patches.

==Your Photography Skills (Optional)==

===In your introduction on hugin-ptx tell us:===

* What camera gear do you use?
* Do you photograph panoramas? please provide links to examples
* Do you make other use of hugin/panotools than for stitching panoramas? please describe and show examples
* Do you photograph otherwise? please provide links

==You and Us==

===In your introduction on hugin-ptx tell us:===

* Were you involved in Hugin/Panotools development in the past? What was your contribution?
* Were you involved in other OpenSource development projects in the past? which, when and in what role?
* Why have you chosen your development idea and what do you expect from your implementation?

===Your Project===

Add yourself/your project with a short synopsis to the list of projects on the wiki if you have not done so yet.

* Start a wiki page to work on your proposal
* What do you want to achieve?
* If you have chosen an idea from our list, why did you choose this specific idea?
* If you are proposing a project of your own, what is unique about it?
* What makes you suited to carry the project?
* How much time do you plan to invest in the project before, during and after the Summer of Code? (we expected full time 40h/week during GSoC, but better make this explicit)
* Please provide a schedule of how this time will be spent on subtasks of the project. While this is only preliminary, you will be required to provide a detailed plan latest at the beginning of GSoC and during the project you will issue weekly progress reports against that plan.

[[Category:Community:Project]]

@@ Line 13: / Line 13: @@
 Get up and running with your system to build Hugin, Panotools and Enblend-Enfuse from our [http://sourceforge.net/scm/?type=hg&group_id=77506 repository]. Informations for several OSses can be found here: [[Hugin_Compiling_Fedora|Fedora]], [[Hugin_Compiling_OSX|OS X]], [[Hugin_Compiling_Windows|Windows]], [[Hugin_Compiling_ubuntu|Ubuntu]] and [[Hugin_Compiling_Gentoo|Gentoo]].
-Of you need help on compiling, ask on the mailing list. If you're successful, we'd like to hear it too. If you find an error/omission on the wiki page, do correct it, it's a wiki!
+If you need help on compiling, ask on the mailing list. If you're successful, we'd like to hear it too. If you find an error/omission on the wiki page, do correct it, it's a wiki!
 To show proficiency of the toolchain, we ask you to produce a patch against Hugin's repository. This helps us to assess your coding style. You can find ideas in our tracker, either bug reports or feature requests. Optimize your time, you don't have to impress us. Then talk about your your patch for peer review on our mailing list. We do not consider applications without patches.

← Older revision		Revision as of 22:18, 22 March 2011
Line 1:		Line 1:
		+	'''The application deadline is April 8 19:00 UTC.'''
	== You ==		== You ==
	Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [http://groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.		Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [http://groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.

@@ Line 1: / Line 1: @@
 == You ==
-Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.
+Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [http://groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.
 It's optional but nice if you also tell us about your photography skills in your introduction. What kind of photographic gear do you use, do you photograph panoramas? Show us some of your examples, preferably somewhere online, not attached to the email (i.e., show us your flickr, deviantart or some other online gallery of yours). If you make other use of hugin/panotools than for stitching panoramas we'd also like to hear about it. Such ideas are almost always very interesting.

@@ Line 16: / Line 16: @@
 To show proficiency of the toolchain, we ask you to produce a patch against Hugin's repository. This helps us to assess your coding style. You can find ideas in our tracker, either bug reports or feature requests. Optimize your time, you don't have to impress us. Then talk about your your patch for peer review on our mailing list. We do not consider applications without patches.
-{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
+== Get going ==
-|-valign="top"
+* First you probably need to familiarize yourself with how the past Summers of Code went; so you might want to read up the necessary pages in the  [[Summer of Code overview]] first.
-! '''NOTE:'''
+* Add yourself/your project with a short synopsis to the list of projects on the wiki, don't forget to put <pre>[[Category:Community:Project]]</pre> to the bottom of the page you make, so it will show up in the overview. In the page of your proposal, make clear 1) what you want to achieve and 2) what do you expect from your implementation. If you chose an idea from the [https://blueprints.launchpad.net/hugin Blueprints over at Launchpad] tell us why and what you'd exactly like to do with it. If you're having an idea of your own, tell us more about it. We want to know what's great about and why it would be of benefit for hugin. On your proposal page, tell us why you're suited to carry out the project.
-! The stuff below is copied verbatim from 2009 and still needs an overhaul. But I don't have the time now...
+* Be prepared to tell us how much time do you plan to invest in the project before, during and after the Summer of Code? We expected full time 40h/week during GSoC, would that be doable for you?
-|}
-===Your Project===
-−
-Add yourself/your project with a short synopsis to the list of projects on the wiki if you have not done so yet.
-−
-* Please read [[Summer of Code overview]] first.
-* Start a wiki page to work on your proposal
-* What do you want to achieve?
-* Why have you chosen your development idea and what do you expect from your implementation?
-* If you have chosen an idea from our list, why did you choose this specific idea?
-* If you are proposing a project of your own, what is unique about it?
-* What makes you suited to carry the project?
-* How much time do you plan to invest in the project before, during and after the Summer of Code? (we expected full time 40h/week during GSoC, but better make this explicit)
 * Please provide a schedule of how this time will be spent on subtasks of the project. While this is only preliminary, you will be required to provide a detailed plan latest at the beginning of GSoC and during the project you will issue weekly progress reports against that plan.
 [[Category:Community:Project]]

@@ Line 1: / Line 1: @@
-==You==
+== You ==
 Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the [groups.google.com/group/hugin-ptx hugin-ptx Google Group] we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.
-==Your Coding Skills==
+It's optional but nice if you also tell us about your photography skills in your introduction. What kind of photographic gear do you use, do you photograph panoramas? Show us some of your examples, preferably somewhere online, not attached to the email (i.e., show us your flickr, deviantart or some other online gallery of yours). If you make other use of hugin/panotools than for stitching panoramas we'd also like to hear about it. Such ideas are almost always very interesting.
-If you're adding a project proposal, make sure to let us know what platform you use to code? Tell us about your hardware and operating system. Then we'd like to know a bit more about your coding experience: Did you ever code in C or C++, or are you a guru in some other language?
+{| style="margin: 1em auto 1em 1em;background:#FFFF99;color:#FF0000;text-align:left;border: solid #FF3300;"
+|-valign="top"
+! '''NOTE:'''
-===Set yourself up===
+! The stuff below is copied verbatim from 2009 and still needs an overhaul. But I don't have the time now...
+|}
-* Set up your platform to build Hugin, Panotools and Enblend-Enfuse from SVN/CVS. Try to do it based on the instructions listed below.
-** Linux: Ubuntu or other, including BSD and other Unix
-** Mac OSX
-** Windows
-* If you decide to work on Lighttwist, ask for help on hugin-ptx.
-−
-* If you need help, ask on  hugin-ptx.
-* Report success on hugin-ptx.
-* If you find that the instructions can be improved, get a wiki account and do it, or suggest the improvements on hugin-ptx.
-* Produce a patch against Hugin's SVN repository to show proficiency of the toolchain and your coding style. You can find ideas in our tracker, either bug reports or feature requests. Optimize your time, you don't have to impress us. Some ideas are listed in this ToDo List for Student Applicants.
-* Publish your patch for peer review on hugin-ptx. We do not consider applications without patches.
-−
-==Your Photography Skills (Optional)==
-−
-===In your introduction on hugin-ptx tell us:===
-−
-* What camera gear do you use?
-* Do you photograph panoramas? please provide links to examples
-* Do you make other use of hugin/panotools than for stitching panoramas? please describe and show examples
-* Do you photograph otherwise? please provide links
-−
-==You and Us==
-−
-===In your introduction on hugin-ptx tell us:===
-−
-* Were you involved in Hugin/Panotools development in the past? What was your contribution?
-* Were you involved in other OpenSource development projects in the past? which, when and in what role?
-* Why have you chosen your development idea and what do you expect from your implementation?
-−
 ===Your Project===
@@ Line 50: / Line 27: @@
 * Start a wiki page to work on your proposal
 * What do you want to achieve?
 * If you have chosen an idea from our list, why did you choose this specific idea?
 * If you are proposing a project of your own, what is unique about it?