Drupalcon San Francisco 2010

Sharing data between sites in RDF (in theory).

The core RDF module provides an API for mapping RDF data.

Use the contrib RDF package to provide the rdfui and rdfx modules. As of right now, before the release of Drupal 7, the most up-to-date, 7.x version of these modules can be found at http://github.com/scor/rdf

For more advanced querying, the SPARQL module can be used.

Update: New modules for Sharing Data Semantically

They are like me when i started out as a project manager, no idea of what the project involves or what value it provides.

It's up to you to show them that value.

It's very important that you not let anything get to you as a PM.

Have to be very clear that custom code has to be reported.

"How much Drupal do you feel you have to know? Our project managers want to know Drupal but they don't want to build sites. How much about Drupal, about development, do project managers have to know?"

We started with picking up copies of "Using Drupal".

Open comment from the public.

Webforms used heavily.

Cool and all, but not that much useful information. Sorry!

Michelle L: Why no node body - it prints all values in the body, makes it hard to isolate the real body when theming.

Michelle introduces us to
hook_token_* yay!

hook_token_values

"I always make my own custom breadcrumbs in the theme layer."

Eric G. of Development Seed:

We identified clients with similar interests and needs and started building

it brought a whole new level of [reward, mission] to the team. I don't think we'd be together if we didn't start building managing news three years ago.

An extremely abbreviated summary of developer's summit deployment breakout.

Josh Koenig summarized the discussion so far and tried to put a direction on it: we want to separate configuration from code and have a couple approaches.

Greg Dunlap (heyrocker) of Deploy module disagreed completely: there is no separation of configuration and content in Drupal, there won't be, and there probably shouldn't be.

And lots of clients, what they really care about, is content deployment.

UUIDs in core would be huge.

http://sf2010.drupal.org/conference/sessions/strategies-community-contributions

Development Time

Eric G. encourages you to encapsulate your work in a code page

We were working on Open Atrium for like three years.

There's going to be so many distros in six months, this will be great.

Everyone in Drupal needs to communicate much more about

(Jeff Eaton kicks off.)

Canonical use for token is mailmerge.

User mail is hardcoded system in Drupal 6, it doesn't use token.

Pathauto. Everyone is using it, or should be.

Immediately we proposed it for inclusion in Drupal core. More than three years ago.

Really, it wasn't good enough for core.

Organization: An all-you-can-eat buffet of crazy-- too many modules made tokens available, with all different names, and no categorization.

Code reuse: Date formats are hell.