soc2009

The time you've all been waiting for has arrived! As of yesterday students started adding projects to the Official Summer of Code site, and so if you're planning on participating as either a student or mentor, it's time to get a-rollin'!

If you're a student that wants to work on Drupal projects for the summer of code, you should:

• sign up for accounts on both drupal.org and groups.drupal.org
• either locate a proposal that interests you on the Summer of Code group, or add your own idea as a discussion on the Summer of Code group
• if you're interested in a community proposal you should comment on that proposal's discussion to let the community know you're going to put up a proposal
• add the proposals you're interested in to the Official Summer of Code site. IMPORTANT: you can only work on one Summer of Code project per summer, however you can add as many applications as you want and more than one student can add the same basic proposal (though only one proposal will be accepted for each specific idea)
• if you're adopting a community proposal you also should consider creating your own discussion where you work within this site to clarify and perfect your proposal.

If you're interested in mentoring a SoC project, you should:

• sign up to the Summer of Code 2009 Mentors group
• apply to be a mentor on the the Official Summer of Code site (see instructions below in the comments)
• review ideas, create ideas, and most importantly, help the students navigate through the often choppy community waters here.
• if you're interested mentoring one of the proposed ideas you should comment on that proposal's discussion to let students know that mentors are willing to work with them

Also- if you need to reach me and can't find me in the #drupal irc channel, please feel free to send me an e-mail (alex at zivtech) or through my contact form.

Overview: Make integration of version control systems with Drupal rock, and at the same time help out a module family that's going to be running on drupal.org soon.

Description:

drupal.org has great integration with CVS, including stuff like a commit messages page (which can also be viewed separately for each project), CVS account management, commit restrictions provided dynamically by the website, or automatic packaging of release tarballs just by specifying the CVS tag when creating the release node. All of that makes drupal.org an immensely powerful and easy to use platform for managing Drupal projects in CVS. As a downside though, all of that works only for CVS, and the fact that it doesn't cope with other version control systems is one major reason that drupal.org is still sticking with CVS all the way.

Version Control API was born as a Summer of Code project (the logs!) in 2007, and aims to provide version control integration for Drupal while not depending on any specific version control system (VCS), and being flexible enough for usage on sites other than drupal.org.

A number of solutions are springing up for deploying site configuration (spaces, patterns, etc). And solutions are starting to spring up around deployment of custom sites as well - the Aegir project and the Domains module both provide tools for pushing out multiple sites on a single infrastructure.

For more information, see http://drupal.org/project/image_overlay

Project page is http://drupal.org/node/236461

Official ideas list address is http://drupal.org/node/236135

Hi guys,

Its a new year a of course, another Summer of Code. Please check out http://groups.drupal.org/node/18127.

Who else in mentoring? Ben_c? :D

I hope this year a PH student will apply.