To Get the ball rolling here. Here is my position on the topic this year. On Wed, Mar 3, 2010 at 2:34 PM, Tim Donohue <[email protected]> wrote:
> > Before we apply for GSOC 2010, I want to be sure that we have > individuals who are willing and able to act as mentors for student > projects. So far, discussions in our DSpace Developer meetings have > found very few volunteers. The application will spur more volunteers after it is up and publicized on GSoC. > (1) Do we have any interested volunteers who would like to mentor (or > co-mentor) a student for a GSOC 2010 project? You need not be a DSpace > Committer, but you likely should be a developer of some sort. I've put a great deal of thought into this as well and have the following comments: 1.) In the past if the mentor has not been a committer, then there is no avenue for the code to get back into the repository by their efforts. I would like to suggest a different approach this year. a.) If the project is a customization of DSpace trunk, the mentor must be a committer on the trunk, if that means we have to make them one. b.) Otherwise, the project much be in either our modules directory or sandbox c.) If the project requires altering trunk, the mentor must be responsible for assuring the students code is committed in a usable form, if a patch to trunk, at the end of their project as a requirement for completion and payment. It is my intention this year is to volunteer as a mentor, but I have an agenda.... Since launching the DSpace Discovery (Solr Faceted Search) project. My primary interest is in only mentoring students that will work directly on that topic. I believe this will help focus the proposals on a specific task and allow us to choose between multiple appropriate proposals that focus on really enhancing the user experience in DSpace. So, I think that this year, we highly suggest that mentors select a project that they want to see get done and announce that they will work with students who want to approach this project / subject area as well. This will reduce the occurrence of student applications that do not have matching mentor interests. > (2) Would anyone volunteer to help act as the DSpace GSOC > Co-Administrator? I'll gladly take on some of these duties, but I'd > like to have a backup/co-admin to help out. I will advise on things and provide backup support. Its mostly sending out rallying cries to make sure we meet deadlines. I would recommend utilizing "delegation" to mentors wherever possible. > Assuming we have a decent group of interested (or potentially > interested) volunteers, we'll put in an application next week to become > a GSOC 2010 mentoring organization. I would place the application without this criteria, this is one of those "rallying cries". We need to be present in the system before mentors can go to the application and join the project. Mentors can join all the way up to the then end of the summer. Albeit, we want them to join much sooner ;-) Thanks for taking the lead on this Tim! Everyone else, I know there is a great deal of noise, please pass this along on Twitter and elsewhere... Mark -- Mark R. Diggory Head of U.S. Operations - @mire http://www.atmire.com - Institutional Repository Solutions http://www.togather.eu - Before getting together, get t...@ther ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
