GSoC Status Reports for week 1 due, code expected starting June 4th
For those of you who don't keep track, our GSoC students officially started coding on May 21st, so today marks their second week (except for George, who started early). I hope you've all gotten settled in and are getting down to work!
I've got two things I need from all of the GSoC students:
- By tomorrow, you need to write a status report telling us all about
your first week (see more detail below) 2. I want ALL of you to make some sort of commit or merge request to the Mailman/Postorius/Hyperkitty repositories by June 4th, so get ready to do that!
This first commit to the repository doesn't have to be a big deal. If you don't have any code yet, it's ok if you just check in some directory structure you'll be using later and files with nothing but comments explaining how they'll be used later. The idea is to make sure all of us know how to get your code into the repositories in a useful way, including making sure we all know where to find the appropriate knobs in launchpad.
The status report also doesn't have to be huge, but here's what I'd like to see:
- What did you do in the past week? (May 21-28th)
- Include links to any code/documentation you've written. If it's
not checked in somewhere yet, check it in!
What do you plan to do next week? (May 28-June 4)
- This can be a bit sketchy, but feel free to dream big!
What, if anything, caused you trouble this week?
Do you have any questions that came up? (And these can be things
like "why is this directory here?" or "why is it called Postorius, anyhow?" as well as stuff relevant to exactly what you're working on.)
- Do you have any other important upcoming plans? (This includes
reminding us when you have exams coming up, or you have to go to your sister's wedding, or other things that just don't fit under "next week")
Expect to be doing weekly reports for most of the summer -- it's an easy way to help give all the mentors and other developers an idea of where you are and when you might need help.
Starting next week I may start sending private reminders, but I figured I'd start by telling the whole list so they know to be prepared for your code commits and to expect status reports starting tomorrow.