The LA user's group is planning the 2009 DrupalCamp, and nbluto and I are going to organize a drupalchix-themed track of some sort. We've just begun planning - and are hoping for feedback from you as to what themes/topics/discussions you would find most useful in such a track!

As part of the Geo June activity, we've started a website to aggregate the work being done: http://www.geojune.org. We're aiming to provide documentation, demos of the developing modules, tutorials, etc.

DrupalCamp Colorado Registration has been opened! You can register at the main camp website - http://www.drupalcampcolorado.org

DrupalCamp Colorado is the regions biggest gathering of people interested in Drupal. The event is based around sessions proposed from the community and voted on by attendees. Camp is funded by a mix of entry fees and sponsorships.

DrupalCamp Colorado 2009

June 27 and 28th we will be at the Denver PPA Event Center (2105 Decatur St. Denver, CO 80211).

On Friday June 12th, we will be having the Drupal.org redesign sprint. All Drupal designers and developers who would like to learn how to how to contribute to theming drupal.org and implementing the redesign are welcome to attend, but must sign-up in advance.

20 Ames St., Cambridge, MA white-tiled building - Sprint is in Conference Room 135: Go to lower level of Media Lab, look for double glass doors "001"; go through doors, up metal staircase; 135 is at the top on right.

As usual, this year's Summer of Code program had way more qualified students and proposals than it did slots. As a result there are some students with amazing potential who will not be getting directly engaged through this program. But- the Summer of Code isn't the only avenue we have to getting students more involved in the community, there are also summer internships at many companies (I know, for example, that Zivtech will likely be looking for a Drupal intern for the summer).

Welcome, accepted Summer of Code students! This post contains important information about prerequisites for starting your project. Please read it carefully.

Google has awarded Drupal 18 slots for the 2009 Google Summer of Code. This year there were many strong applications, and narrowing the field to the top 18 was not an easy task. Thanks to all the mentors who helped out with the evaluating, and congratulations to all of the students. We look forward to working with you this summer! :)

Although coding doesn't formally kick off until May 23, according to Google's program timeline, there are a few things that need to get sorted out first. If you have questions about how to do any of these things, don't be shy! :) Post to the http://groups.drupal.org/soc-2009 or ask in #drupal on irc.freenode.net, and we'll get you hooked up.

1. Create a central wiki page for your project at the SoC 2009 group. This wiki page should basically be a single location that anyone can read over the course of SoC in order to get a good sense of what your project is about, and where it is currently in terms of completion. There's a template you can copy and paste available at http://groups.drupal.org/node/21558. Add a link to your project in here

   This page should be updated when you and your mentors reach a major design decision about your project, or if your schedule and/or deliverables need to be adjusted. Use the SoC 2008 group as a tool to help you achieve your goals. Ask questions. Find people to help you test. Discuss design decisions. Post mockups. Be creative.

2. Obtain a CVS account. The code that you produce during Summer of Code will ultimately reside at cvs.drupal.org, and you need to apply for a CVS account if you don't already have one. In your application, please mention that you are a Google Summer of Code student, so that your account will get approved quickly.

   If you're new to CVS (or revision control systems in general), you might find our CVS handbook helpful, particularly the CVS introduction. Additionally, the CVS quickstart guide is handy to have around as a reference.

3. Create a "project" on drupal.org for your project (even if your delivery is an improvement to an existing module). Once you have CVS access, describe your project briefly in a README.txt and add a sub-folder for it to the contribution repository's modules/ directory, then create a "project" for it on drupal.org, following the instructions at Step-by-step: Create a CVS project. This will give you several tools at your disposal, including:
   • a central project page, which you can use to document your project and its current state.
   • an issue tracker, which you can use to break your project apart into sub-tasks and track their completion status. Using the issue tracker allows your mentors (or any other community members) to provide input on your development process.
   • the ability to create project releases, which testers can download and try out on their own Drupal installations.

   There is helpful information about working with these tools available in the Maintaining d.o projects with CVS guide. Note that issue tracker and CVS commit activity will be primary methods of evaluating projects, and we require you to create an issue every week to report . These show us that you're making progress each week, and should be titled "Milestone X" and tagged with "SoC 2009 Weekly Update".

4. Meet your mentors and discuss your project. Please investigate which means of communication your mentors prefer. Communication is a crucial element of success, and you are encouraged to use email, Skype, IRC (http://drupal.org/node/108355), the SoC 2009 group (http://groups.drupal.org/soc-2009), the devel list (http://drupal.org/mailing-lists), and any other resources that are available to make sure that the lines of communication between you and your mentor are well established and open for the duration of the summer.

   Ensure sure that any broad or project management-related changes are documented in your wiki page, and any code-related decisions/feedback is reflected in your project's issue queue, for the benefit of those who didn't have a chance to take part in your personal communication.

5. Refine the scope of your project. Discuss with your mentors whether they feel the scope of the project described in your application is realistic and clear. If there are ambiguities, try to iron them out. We're looking for clearly stated deliverables that you feel confident you can produce by the end of the summer. Update your project's wiki page with the result.
6. Plan on testing. It is a requirement for this year's Summer of Code projects to include test scripts. For most people the simpletest framework will be the best solution. See documentation at http://drupal.org/simpletest.

If you have any questions to one of the points above, your mentor will be able to help you (or ask here).

We're looking forward to working with you.

Happy Coding,

Drupal's Google Summer of Code team

There are only a few months left before the code freeze on September 1st. Now that Fields API has settled in core, it's time to extend it with some RDF semantics. DERI Galway is hosting an RDF in Drupal code sprint during the week of May 11th until May 14th.

Goals of the code sprint

The RDF code sprint will focus on Drupal core and aim at integrating RDF semantics in it.

1. Extend Fields API to integrate RDF mappings for each field instance. The semantics of a field can differ from a bundle to another. This can be stored either in the existing settings property or by adding a rdf_mappings property to the Field Instance objects.
2. Modify the Fields UI (contrib) to allow RDF mappings editing.
3. Define the appropriate mappings for the core modules, based on the RDF core mapping proposal.
4. Patch core modules with the mappings defined above.
5. Export these mappings in RDFa via the theme layer and keep it as generic as possible in order to ease the work of the themers.
6. Write tests for RDF in core.
7. Identify other non-fieldable entities in core which could benefit from being RDF-ized, and see how to annotate them. Comment is one example. Terms also, though they might become fieldable.
8. RSS 1 (RDF) in core. Arto volunteered to get started with that.

Based on an email conversation I had with Darren, Evgeny, Aron Novak and Walkah I pulled together this roadmap for advanced OpenID features (attribute exchange, provider, etc).

The goal is to reduce the overall number of modules involved in deploying OpenID attribute exchange features, to expand on existing content profile integration, to remove dependencies on modules that are not used in all use cases and to push changes into OpenID and OpenID Provider where it makes sense.

Let's go out, have a few beers (or beverage of your choice) and talk Drupal. No agenda, just a bunch of geeks hanging out.

Location

Stout NYC
133 W 33rd St, NY, NY
Between 6th and 7th Avenue

Take the 1,2,3 to 34th St. Penn Station,
or D,F,N,Q,R,V,W to 34th St. Herald Square.

Time

I'll be there right at 6:00PM. Get there when you can. Stay for as long as you want. There's pretty decent food if you need to eat.

Hello World,

As you may have noticed, Groups.Drupal.org is being upgraded to Drupal 6. In that process we are adding fun new features and re-evaluating decisions from the past.

After careful consideration we have decided to remove the ability to post private content to the site. As a result, we will be unpublishing all existing private content. We manually reviewed existing private content and it was either posts that could be public or which could find a new home outside of groups.drupal.org.