Difference between revisions of "GSoC Planning"

From Audacity Wiki
Jump to: navigation, search
(pulled together some recent comments)
(responses.)
Line 5: Line 5:
 
* '''Richard:''' "Is it a good time to start on a "what are we looking for in students" page for next year. I think a reasonable number of applicants (especially from outside US/Europe) have mis-judged what we were looking for, and some more concrete points (based on what was said in private comments but in a general form) might help students (and us) next year. A key one is about time commitment, especially for post-grad people who don't really have a summer vac. There are also a lot of new-to-open-source people who don't get the whole fitting in / code re-use / connected open source philosophy, which I've tried to lever a number of people towards, but hasn't always worked."
 
* '''Richard:''' "Is it a good time to start on a "what are we looking for in students" page for next year. I think a reasonable number of applicants (especially from outside US/Europe) have mis-judged what we were looking for, and some more concrete points (based on what was said in private comments but in a general form) might help students (and us) next year. A key one is about time commitment, especially for post-grad people who don't really have a summer vac. There are also a lot of new-to-open-source people who don't get the whole fitting in / code re-use / connected open source philosophy, which I've tried to lever a number of people towards, but hasn't always worked."
 
** '''Gale:''' Could also be included/linked to in the "Hints on writing a good proposal" panel in [[Writing GSoC Proposals]]. Information in situ may have more chance of being read than in a link.
 
** '''Gale:''' Could also be included/linked to in the "Hints on writing a good proposal" panel in [[Writing GSoC Proposals]]. Information in situ may have more chance of being read than in a link.
 +
** '''James:'' I think personal opinion works well here.  So a blog on it, with a link from the wiki?  One thing I want to get across to students is that different mentors will have different views, so whilst I'll agree with what Richard says, I'd have a different slant on it and emphasise some other points.
 
    
 
    
 
* '''James:''' [[More GSoC Ideas]] has over ten times fewer views than [[GSoC Ideas]].  
 
* '''James:''' [[More GSoC Ideas]] has over ten times fewer views than [[GSoC Ideas]].  
** '''Gale:''' Make the link to [[More GSoC Ideas]] more prominent, or list a summary of all projects on one page with links to them, marking the provisional ones as such?  
+
** '''Gale:''' Make the link to [[More GSoC Ideas]] more prominent, or list a summary of all projects on one page with links to them, marking the provisional ones as such?  
 +
** '''James:''' Link to more prominent. 
  
 
* '''Gale:''' There seemed to be some student resistance in 2008 to having to get a gmail/googlemail account. Other organisations do not insist on this. Should we ask only for one of a few named webmail services like Yahoo!, Windows Live Hotmail as well as Google?  
 
* '''Gale:''' There seemed to be some student resistance in 2008 to having to get a gmail/googlemail account. Other organisations do not insist on this. Should we ask only for one of a few named webmail services like Yahoo!, Windows Live Hotmail as well as Google?  
 +
** '''James:''' No.  Gmail means we can ask Google to look into the problem.  They will at least know if there have been 'issues in China with gmail'.  See FAQ.
  
 
* In the run up to GSoC 2008 we wanted to get our developer documentation into good shape.  This is particularly important for new features like the plug in interface.  Help with bringing the Doxygen documentation back up to date would be appreciated and is also a good way of learning the code.  We'd also like to go further and have diagrams and more written documentation that shows how things work.   
 
* In the run up to GSoC 2008 we wanted to get our developer documentation into good shape.  This is particularly important for new features like the plug in interface.  Help with bringing the Doxygen documentation back up to date would be appreciated and is also a good way of learning the code.  We'd also like to go further and have diagrams and more written documentation that shows how things work.   

Revision as of 12:44, 12 April 2008


This page is to help with planning for Google Summer of Code. It's a 'brainstorming' page at the moment. All subscribers to audacity-devel are very welcome to add comments and suggestions. James 05:26, 27 July 2007 (PDT)

  • Richard: "Is it a good time to start on a "what are we looking for in students" page for next year. I think a reasonable number of applicants (especially from outside US/Europe) have mis-judged what we were looking for, and some more concrete points (based on what was said in private comments but in a general form) might help students (and us) next year. A key one is about time commitment, especially for post-grad people who don't really have a summer vac. There are also a lot of new-to-open-source people who don't get the whole fitting in / code re-use / connected open source philosophy, which I've tried to lever a number of people towards, but hasn't always worked."
    • Gale: Could also be included/linked to in the "Hints on writing a good proposal" panel in Writing GSoC Proposals. Information in situ may have more chance of being read than in a link.
    • 'James: I think personal opinion works well here. So a blog on it, with a link from the wiki? One thing I want to get across to students is that different mentors will have different views, so whilst I'll agree with what Richard says, I'd have a different slant on it and emphasise some other points.
  • James: More GSoC Ideas has over ten times fewer views than GSoC Ideas.
    • Gale: Make the link to More GSoC Ideas more prominent, or list a summary of all projects on one page with links to them, marking the provisional ones as such?
    • James: Link to more prominent.
  • Gale: There seemed to be some student resistance in 2008 to having to get a gmail/googlemail account. Other organisations do not insist on this. Should we ask only for one of a few named webmail services like Yahoo!, Windows Live Hotmail as well as Google?
    • James: No. Gmail means we can ask Google to look into the problem. They will at least know if there have been 'issues in China with gmail'. See FAQ.
  • In the run up to GSoC 2008 we wanted to get our developer documentation into good shape. This is particularly important for new features like the plug in interface. Help with bringing the Doxygen documentation back up to date would be appreciated and is also a good way of learning the code. We'd also like to go further and have diagrams and more written documentation that shows how things work.
  • We can always do with new ideas on the ideas page. Suggestions that have an element of novelty to them, that can be completed in the time frame are particularly welcome. We feel it's important that projects have both an aspect which is fairly straightforward to complete in the time as well as a stretch goal. We need to get something complete and usable out of each project, whether it goes superbly or whether there are difficulties.
  • To get accepted by Google, it will help enormously if we can show that we already have many students queuing up to take part. We would like someone to help us design a half-page flyer for Audacity GSoC which we can put on notice boards in computer science labs in universities. If there are multiple offers to do this, then we'll vote on the flyer to use on the audacity-devel mailing list.
  • All established developers with Audacity need to get gmail accounts. Only with gmail accounts can they be listed as potential mentors. We should also look at getting second-mentors for overlaps. Some of the projects are likely to be on overlap between Audacity and wxWidgets, Portaudio or Jack. In those cases, if the project is being administered and mentored by Audacity, it would still be very useful to have a second mentor from the overlap project already lined up to give advice.