Project Planning
Now that I’m finished with finals, I’m focusing on my summer of code project.
The first challenge is coming up with a name. The best so far is phpDBviz. If nothing better comes up, I’ll register a google code project for it tomorrow. This brings up the secondary question: what version control system to use? Google code provides a subversion repository, and although more modern systems like git are tempting, I’ll probably stick with gcode for the moment since it provides so much more than just the version control (a wiki, a bug tracker, an easy system for bringing other devs onto the project).
What license? I’m leaning towards a BSD style license for simplicity. I doubt that I need to worry greatly about some external force taking the code and not giving it back, and I feel like users will be more comfortable with fewer requirements.
I’ve put together a google doc with various items of interest for me to work on, though I’ll probably move at least some of the info to the project wiki once I get that set up. It’s available here:
http://docs.google.com/Doc?id=ddq9nrb4_109gw6fsnfk
Although not listed in that doc, my goals for this week generally involve getting everything set up to allow me to make real progress next week. I want to
- Set up google code project
- Create and sketch in all the main sections for the Design Document
- Begin integration documentation
- Write short README style description of the project
- Create “Deliverable” document describing end result
- Write detailed schedule for next 3 weeks
- Begin working on the setup steps listed for week1
This is going to be a lot of work, but I feel like the mentors and NESCent have the management experience to help me keep this project on track. As I break it down into smaller pieces, things start to look more manageable.