Difference between revisions of "Historical:SoC2009 Application Template"
Jump to navigation
Jump to search
(Created page with 'You * Name * University / current enrollment * Short bio / overview of your background * Join the hugin-ptx GoogleGroup and introduce yourself * Get yourself...') |
Erik Krause (talk | contribs) (wikified) |
||
| Line 1: | Line 1: | ||
| − | You | + | ==You== |
| − | + | * Name | |
| − | + | * University / current enrollment | |
| − | + | * Short bio / overview of your background | |
| − | + | * Join the hugin-ptx GoogleGroup and introduce yourself | |
| − | + | * Get yourself an account on our Wiki and add your project proposal on your user page | |
| − | Your Coding Skills | + | ==Your Coding Skills== |
| − | In your project proposal let us know | + | ===In your project proposal let us know=== |
| − | + | * What platform do you use to code? hardware specifications and operating system | |
| − | + | * Did you ever code in C or C++, yes/no? what is your experience? | |
| − | Set yourself up | + | ===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) | + | ==Your Photography Skills (Optional)== |
| − | In your introduction on hugin-ptx tell us: | + | ===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 | + | ==You and Us== |
| − | In your introduction on hugin-ptx tell 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 | + | ===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. | Add yourself/your project with a short synopsis to the list of projects on the wiki if you have not done so yet. | ||
| − | + | * Start to work on your proposal on your user page. | |
| − | + | * 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. | |
Revision as of 00:31, 5 April 2009
You
- Name
- University / current enrollment
- Short bio / overview of your background
- Join the hugin-ptx GoogleGroup and introduce yourself
- Get yourself an account on our Wiki and add your project proposal on your user page
Your Coding Skills
In your project proposal let us know
- What platform do you use to code? hardware specifications and operating system
- Did you ever code in C or C++, yes/no? what is your experience?
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 to work on your proposal on your user page.
- 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.