Public

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.

In summary: CiviCRM and Drupal worked great for us. Not really any detail, maybe a good add for non-tech people in an org.

Cricket Wallace
[in glorious dreadlocks and a suit.]

Organization is mission driven.

Jane Goodall
UN Representative for Peace
and of course known for her chimpanzee reearch

Roots & Shoots Youth Programs
and
Community Centered Conservation (in Africa)

We're not necessarily people who use the internet a whole lot.

We're trying to get our stories out.

We needed better tools.

Posted issue: http://drupal.org/node/777086

Related closed issues:

Usability: Hide machine readable name of node type by default. Catch wanted this patch only on the condition of it "not changing the type name automatically apart from on creation."

Make node type visible on editing form by default.

Reuse a theme hook if you can!

links
image
image_style
item_list
username
file_link
html_tag
more_link
pager
progress_bar
table

See full list:
http://api.drupal.org/api/group/themeable/7

Advantages of re-using:

Webchick indicates that, if there is not an issue posted yet, there has been discussion on IRC and many feel that one or a partial solution is to split it to only be used by default for truly contextual links-- the links you reach from a page-- edit menu, edit block, edit node.

Here's the issue:

http://drupal.org/node/666974