Difference between revisions of "SOC Application Template"
Jump to navigation
Jump to search
(→Tasks) |
Joneuhauser (talk | contribs) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
== Google Summer of Code - | == Google Summer of Code - Candidate Application Template for Inkscape == | ||
Thanks for considering | Thanks for considering Inkscape for your SoC project! To help us identifying you as a good candidate, we ask a few questions. | ||
=== Inkscape Questions === | === Inkscape Questions === | ||
# When did you first hear about Inkscape? | # When did you first hear about Inkscape? | ||
# What kind of drawings do you create with Inkscape? | # What kind of drawings do you create with Inkscape? | ||
# Describe your participation in our community (e.g. uploaded drawings, tutorials, bug reports, communication via mailing lists or IRC). | |||
# Describe | # Describe your contributions to the Inkscape development (e.g. bug fixes, translations, packaging, testing). | ||
# Describe | # In exactly '''two''' sentences, why should we pick '''YOU'''? | ||
=== About Yourself === | === About Yourself === | ||
| Line 20: | Line 20: | ||
=== Tasks === | === Tasks === | ||
# Submit a drawing you have made with Inkscape. It doesn't have to be professional quality but it should show us that you know how to use Inkscape. | # Submit a drawing you have made with Inkscape. It doesn't have to be professional quality but it should show us that you know how to use Inkscape. | ||
# Introduce yourself on the [ | # Introduce yourself on the [https://chat.inkscape.org Inkscape chat], and post your project ideas for feedback, ''before'' submitting your application | ||
# [ | # [https://inkscape.org/develop/getting-started/ Checkout] the Inkscape sourcecode through git and review it. Make sure you can compile and build Inkscape on your own PC! | ||
# Find and fix two bugs in the [https:// | # Find and fix two bugs in the [https://gitlab.com/inkscape/inkscape/issues Inkscape bug tracker]. Create and upload patches for the bugs, and make sure we know to connect those bug fixes and your GSoC application. You can alternatively submit a patch that improves code unrelated to a bug. | ||
# Prepare a detailed plan (with timetable) of the work you | # Prepare a detailed plan (with timetable) of the work you want to do. | ||
#Explain any additional costs that the project would have to cover in order for you to perform this work, such as license costs for proprietary tools (when no suitable OSS replacement exists) or hardware costs (e.g. when the target is to support specific hardware). There is no guarantee that these costs can be reimbursed, but we still need to know in advance. | |||
Latest revision as of 12:20, 14 June 2024
Google Summer of Code - Candidate Application Template for Inkscape
Thanks for considering Inkscape for your SoC project! To help us identifying you as a good candidate, we ask a few questions.
Inkscape Questions
- When did you first hear about Inkscape?
- What kind of drawings do you create with Inkscape?
- Describe your participation in our community (e.g. uploaded drawings, tutorials, bug reports, communication via mailing lists or IRC).
- Describe your contributions to the Inkscape development (e.g. bug fixes, translations, packaging, testing).
- In exactly two sentences, why should we pick YOU?
About Yourself
- What is your name, email address, and irc nickname?
- Describe any plans you have for the summer in addition to GSoC (classes, thesis, job, vacation, etc.).
- What programming projects have you completed?
- What are your favorite programming tools (editor, etc.)?
- Describe any work on other open-source projects.
- List other GSoC projects you are applying to.
Tasks
- Submit a drawing you have made with Inkscape. It doesn't have to be professional quality but it should show us that you know how to use Inkscape.
- Introduce yourself on the Inkscape chat, and post your project ideas for feedback, before submitting your application
- Checkout the Inkscape sourcecode through git and review it. Make sure you can compile and build Inkscape on your own PC!
- Find and fix two bugs in the Inkscape bug tracker. Create and upload patches for the bugs, and make sure we know to connect those bug fixes and your GSoC application. You can alternatively submit a patch that improves code unrelated to a bug.
- Prepare a detailed plan (with timetable) of the work you want to do.
- Explain any additional costs that the project would have to cover in order for you to perform this work, such as license costs for proprietary tools (when no suitable OSS replacement exists) or hardware costs (e.g. when the target is to support specific hardware). There is no guarantee that these costs can be reimbursed, but we still need to know in advance.