Summer of Code 2013 is over!

GSOC 2013 is over - thanks to all students and mentors and congrats to the finalists.

Here are our initial project ideas.

Projects

What to do in Community Bonding Phase?

• become familiar with the community

  • stay connected on the IRC channel (if you want a shell account for irssi/weechat + screen [so you can stay connected 24/7], just tell so)
  • follow changes in the wiki (and subscribe to THIS page!)
  • follow changes on bitbucket
  • subscribe to moin-user mailing list
  • discuss your ideas, ask questions, make suggestions, help other people (preferably on IRC)

• make a more precise plan about your project

  • use etherpad to do that, get feedback/suggestions from mentors/helpers
  • research and develop the ideas to a state of detailledness / clarity / order so you can start coding when coding phase begins

• become (more) familiar with the code, coding style, workflow, the tools

  • read the code / the docs
  • read PEP8, the python coding style guide
  • get familiar with mercurial / bitbucket DVCS workflow
  • get familiar with py.test / TDD

  • get your development environment ready and fine tuned (if you like, use PyCharm)

• do practical development work

  • please note that code written outside the coding phase does not count for SOC

  • fix bugs, do cleanups, improve tests, implement small features
  • always check / use the issue tracker on bitbucket
  • make moin more ready for your SOC project

• http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html

What to do in the Coding Phase?

• make sure you have a relatively clear idea about what to implement before starting to hack

• implement your plans, code! Obey PEP8.

• before committing to your repo, use codereview (e.g. on codereview.appspot.com)
  • always do the first reviews yourself, before asking your mentor(s) and fix all trivial stuff you find
• before committing to your repo, run the tests, make sure there are no regressions
• push daily to your public bitbucket repo

• update your diary daily with a short summary of what you did on that day

  • 5d / 8h is the expected weekly work amount, it is up to you how you distribute that
  • if you did not work on some specific day, do not make a calendar entry

  • if you have other committments, document them in advance below your calendar

  • it is helpful if you declare "coding / online hours" there also, so your mentors know when you are usually online / working
• be present on IRC, talk to your mentors regularly, talk about what you do, ask questions
• enhance / refactor your etherpad (remove outdated stuff, clarify stuff after decisions)
• every Sunday 10:00 UTC (duration: about 1..1.5h) : do not miss the weekly meetings

  • students please prepare yourself before the meeting, so you can copy&paste stuff into the channel:

    • DONE last week
    • BLOCKED by ... (means stuff that you can't solve with reasonable effort / that is technically not possible / that someone else needs to solve)
    • TODO next week
  • all mentors should ask questions / give additional info about the current status of the projects

What you need to do after GSoC has ended

• Fill out and submit all forms Google requires
• Send your code to Google. You can use the following command to extract all of your changesets into a file

  • Linux/Mac OS X: hg export `hg log -M --template '{rev} ' -k 'Joe Doe' -r ad303592c64c:` > my_changesets

  • Windows:

    hg log -M --template "{rev} " -k "Joe Doe" -r 359d51f0fa90: > exportchanges.cmd
    # now edit that file:
    # add hg export at the beginning of the line
    # add > my_changesets.txt at the end of the line
    # run that file:
    exportchanges

  • in case you committed stuff to your repo after the end of gsoc, remove it manually, it is not part of GSOC work
  • Compress the file afterwards