| 49 | | For future reference you may check the [https://www.google-melange.com/ Google SoC website]. You will find more information on their page on [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Students]. |
| 50 | | The official [http://www.google-melange.com/gsoc/events/google/gsoc2014 timeline] should be consulted for the other dates. |
| 51 | | |
| 52 | | There are several things to consider. We are willing to support and |
| 53 | | mentor students who want to gain an experience by working on the |
| 54 | | MacPorts Project. We have many ideas for potential internship subjects, |
| 55 | | yet we are open to anything that is both interesting and relevant to |
| 56 | | MacPorts. Motivated students do not necessarily need to know Tcl |
| 57 | | language beforehand, especially if they already know several scripting |
| 58 | | languages such as Python, Ruby, PHP or Perl. |
| | 49 | For future reference you may check the [https://www.google-melange.com/ Google Summer of Code website]. The [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide] is also worth reading and explains what GSoC is about and how it works in detail. We suggest you take a few minutes and read this guide. |
| | 50 | |
| | 51 | For the official schedule and deadlines, consult the [http://www.google-melange.com/gsoc/events/google/gsoc2014 timeline]. |
| 62 | | The best way to apply is to first make contact with us, either by |
| 63 | | sending a mail to the MacPorts developer |
| 64 | | [http://lists.macosforge.org/mailman/listinfo/macports-dev "mailing list"], |
| 65 | | to the potential mentors listed below, or to IRC members on #macports on |
| 66 | | [http://freenode.net/ FreeNode]. |
| 67 | | |
| 68 | | What we expect from students for their applications: |
| 69 | | * Write your own abstract and proposal, copying text from this idea page is not enough. |
| 70 | | * Show us that you fully understand your task and know what you want to do over the summer. |
| 71 | | * At best, include a short weekly roadmap covering how you would work on the task. |
| 72 | | |
| 73 | | What you should do before handing in an application: |
| 74 | | * Get familiar with the MacPorts Project resources. Especially [GetMacPortsSource check out the code] and [http://guide.macports.org read the guide]. |
| 75 | | * Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial] |
| 76 | | * Subscribe to the mailing lists [http://lists.macosforge.org/mailman/listinfo/macports-dev macports-dev] and [http://lists.macosforge.org/mailman/listinfo/macports-users macports-users] if you do not already read them. Don't be too shy to post. |
| 77 | | * '''Get in contact! ''' Most important is to discuss your ideas with potential mentors via private e-mail, the MacPorts development list, or the IRC channel before applying. |
| | 55 | We are eager to support and mentor students who want to gain experience by working on the MacPorts Project. We have many ideas for potential internship subjects, yet we are open to anything that is both interesting and relevant to MacPorts. If you have an idea of your own, feel free to [#contact contact us] to discuss the ideas. |
| | 56 | |
| | 57 | MacPorts is written in the Tcl scripting language with some low-level parts implemented in C. Most students that have previously applied and successfully completed Google Summer of Code with us did not know Tcl when they applied. Feel free to apply if you don't know Tcl yet, especially if you're willing to learn and already know several scripting languages such as Python, Ruby, PHP or Perl. |
| | 58 | |
| | 59 | The best way to apply is to first make contact with us, either by sending a mail to the mailing list, to potential mentors listed below, or to IRC member on #macports on [http://freenode.net/irc_servers.shtml Freenode]. See also [#contact Ways to Contact Us] for in-depth information on how to reach us. |
| | 60 | |
| | 61 | ==== What we expect from students for their applications ==== |
| | 62 | - Write your own abstract and proposal, copying text from this idea page is not enough. |
| | 63 | - Show us that you fully understand your task and know what you want to do over the summer. |
| | 64 | - At best, include a short weekly roadmap covering how you would work on the task. |
| | 65 | |
| | 66 | ==== What you should do before handing in an application ==== |
| | 67 | - Get familiar with the MacPorts Project resources. Especially [GetMacPortsSource check out the code] and [https://guide.macports.org read the guide]. |
| | 68 | - Read the [http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html Tcl Tutorial]. |
| | 69 | - Subscribe to the [MailingLists mailing list] [http://lists.macosforge.org/mailman/listinfo/macports-dev macports-dev] if you do not already read it. Don't be too shy to post. |
| | 70 | - '''[#contact Get in contact!]''' Most important is to discuss your ideas with potential mentors via private email, the MacPorts development list, or the IRC channel before applying. |
| | 419 | |
| | 420 | |
| | 421 | == Contacting us == #contact |
| | 422 | There are several ways to contact us: |
| | 423 | - Dropping a mail to the [MailingLists MacPorts-dev mailing list] will get you most attention. Note that you have to be subscribed to the list in order to send mail to it. We recommend you create a filter matching the header line `List-Id: macports-dev.lists.macosforge.org` and sort all mails matching this filter into a separate folder. When sending inquiries about Google Summer of Code, we would welcome if you included "GSoC" in the subject of your mail. |
| | 424 | - You can get quick feedback and less formal discussion by joining the `#macports` channel on the [http://freenode.net/irc_servers.shtml Freenode IRC network]. You'll need an IRC client to do so – [http://colloquy.info/ Colloquy] is a popular choice on OS X. Please note that due to timezones and day jobs you might not receive an answer right away. Most users will read your messages when they return and answer as soon as they can. Be prepared to wait a few hours. |
| | 425 | - Feel free to contact any potential mentor via email directly. You can get the email address by appending `@macports.org` to the handle listed in [#Mentors] above. |
| | 426 | |
| | 427 | In general, don't hesitate to contact us – we're here to help you and eager to mentor motivated students in this year's GSoC! |
