Difference between revisions of "GSoC Skills"

From Audacity Wiki
Jump to: navigation, search
(very minor rewording (reads nicer?))
(Retain more of original sense.)
Line 13: Line 13:
 
=Communication=
 
=Communication=
  
We don't demand a daily blog or endless status reports.  We do want to know what is actually going on, and if there are problems, to know them early.  If there are problems with your mentor, or CVS won't accept any of your check-ins, we need you to get this across to us.
+
We don't demand a daily blog or endless status reports.  We do want to know what is actually going on, and if there are problems, to know them early.  We need to be confident that if there are problems with your mentor, or if CVS won't accept any of your check-ins, that you will get this across to us.
  
 
Our current plan is to have a weekly IRC meeting on Fridays during the GSoC period [Time(s) to be announced].  All students involved will be expected to sign into that, or to have made other arrangements with their mentor.
 
Our current plan is to have a weekly IRC meeting on Fridays during the GSoC period [Time(s) to be announced].  All students involved will be expected to sign into that, or to have made other arrangements with their mentor.

Revision as of 10:34, 3 March 2008

For nearly all Audacity Google Summer of Code project ideas, wxWidgets and C++ programming are essential. The project makes extensive use of CVS, mailing lists and MediaWiki, so students will need to get to grips with these. Some projects need additional skills too.

Students who show that they have experience with wxWidgets will generally be at a considerable advantage to those who don't. Whilst Audacity is cross-platform, it isn't necessary to have programming experience on all three platforms (Windows, Mac, Linux/Unix), but some familiarity with all three will make things go more smoothly.

Difficulty of Projects

We have rated the GSoC projects 'Easy', 'Moderate' or 'Hard'. We want to ensure that students do a project that matches their experience and ability. We're more concerned with having a successful outcome than getting the most technically challenging problems tackled. If a very experienced student wants to do an 'easy' project, but add to the spec to make it more challenging for them, then that's fine by us. If a fairly new student can see a way to simplify a 'Hard' project so that it's a realistic goal for them, we'd be delighted.

We'd like to get the matching right so that:

  • Students are tackling problems they have excellent prospects of completing.
  • Students enjoy the challenge and get experience and real satisfaction from it, and not just the stipend from Google.

Communication

We don't demand a daily blog or endless status reports. We do want to know what is actually going on, and if there are problems, to know them early. We need to be confident that if there are problems with your mentor, or if CVS won't accept any of your check-ins, that you will get this across to us.

Our current plan is to have a weekly IRC meeting on Fridays during the GSoC period [Time(s) to be announced]. All students involved will be expected to sign into that, or to have made other arrangements with their mentor.