281
edits
Summer of Code - Getting Started: Difference between revisions
Jump to navigation
Jump to search
→Steps toward a successful application: rearranging and rewording
(→Steps toward a successful application: rearranging and rewording) |
|||
| Line 6: | Line 6: | ||
# 😉💬 '''We want to get to know you (before the deadline). Communicate with us.''' | # 😉💬 '''We want to get to know you (before the deadline). Communicate with us.''' | ||
#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or our [https://webchat.freenode.net/?channels=#octave '''IRC channel''']. | #* Join [https://octave.discourse.group/ '''Octave Discourse'''] or our [https://webchat.freenode.net/?channels=#octave '''IRC channel''']. Using a nickname is fine. | ||
#* | #* Show us that you're motivated to work on Octave 💻. There is no need to present an overwhelming CV 🏆; evidence of involvement with Octave is more important. | ||
#* '''<span style="color:darkblue;">If you never talked to us, we | #* '''<span style="color:darkblue;">If you never talked to us, we will likely reject your proposal</span>''', even it looks good 🚮 | ||
# 👩🔬 '''Get your hands dirty.''' | # 👩🔬 '''Get your hands dirty.''' | ||
#* We are curious about your programming skills 🚀 | #* We are curious about your programming skills 🚀 | ||
#** | #** Your application will be much stronger if you [https://savannah.gnu.org/bugs/?group=octave fix Octave bugs] or [https://savannah.gnu.org/patch/?group=octave submit patches] before or during the application period. | ||
#** | #** You can take a look at the [[short projects]] for some simple bugs to start with. | ||
#* '''Use Octave!''' | #* '''Use Octave!''' | ||
#** If you come across something that does not work the way you like ➡️ try to fix that 🔧 | #** If you come across something that does not work the way you like ➡️ try to fix that 🔧 | ||
#** Or you | #** Or if you find a missing function ➡️ try to implement it. | ||
# 📝💡 '''Tell us what you are going to do.''' | |||
#* Do not write just to say what project you're interested in. Be specific about what you are going to do, include links 🔗, show us you know what you are talking about 💡, and ask many [http://www.catb.org/esr/faqs/smart-questions.html smart questions] 🤓 | |||
#* Remember, '''we are volunteer developers and not your boss''' 🙂 | |||
# 📔 '''Prepare your proposal with us.''' | # 📔 '''Prepare your proposal with us.''' | ||
#* If we see your proposal for the first time after the application deadline, it might easily contain some paragraphs not fully clear to us. Ongoing interaction will give us more confidence that you are capable of working on your project 😓 | |||
#* If we see your proposal for the first time after the application deadline, | |||
#* Try to show us as early as possible a draft of your proposal 👍 | #* Try to show us as early as possible a draft of your proposal 👍 | ||
#* Then submit the proposal following the applicable rules, e.g. for [https://google.github.io/gsocguides/student/writing-a-proposal GSoC]. | |||
= How do we judge your application? = | = How do we judge your application? = | ||