DrupalCamp Ohio Saturday Dec. 3rd 2011
Don't let December weather leave you cold.
Warm up to Ohio's First ever DrupalCamp!
Saturday December 3rd on the glorious campus of OSU you will join Drupalers from all over as we learn more about Drupal and how it's rocking the web!
This post is just to get the date on the groups.drupal.org/events calendar. We're in the early stages of planning right now.
Reply to this thread or contant Me or Jim if you want to join the effort.
We have some seriously cool announcements to make but we need to sure things up and get our stuff together. ARGGGHH! i can hardly stand it! :-)
Drupalcamp Atlanta 2011
In case you missed any earlier announcements, the Drupalcamp Atlanta 2011 website is live (http://drupalcampatlanta.com/)! Registration and session submissions are now open and well underway. There are sponsorship opportunities still available.
You can read more about Drupalcamp Atlanta here:
http://www.mediacurrent.com/blog/drupalcamp-atlanta-2011-officially-open...
I would highly encourage everyone to sign-up as soon as possible - we have to cap attendance due to venue constraints, and the previous two years have sold out weeks in advance.
Cheers,
Dave
Mediacurrent
RFC: Core issue queue office hours and 'triage team'
Update
First office hours are this week, see http://drupal.org/node/1242856
A few of us have been discussing in irc ways to improve the triage of the core issue queue.
The proposal
Several times per week, people join #drupal-contribute and ask for help getting started contributing to Drupal. Depending on who's in the channel at the time, they might be pulled into reviewing a specific core issue or contrib module, writing documentation, or if the channel is quiet just ignored.
To help structure this process better, we're proposing holding 'core issue queue office hours' a couple of times per week (or more regularly if enough people volunteer). This is not a new idea, Views already has a bug squad, jQuery has a bug triage team (and fancy graphs), and the Usability team and some Drupal 8 initiatives are holding regular office hours or irc meetings.
There is no 'core development team' as such, however there are people who regularly work on core issues, as well as people who are regularly in the #drupal-contribute irc channel. For new contributors, it is not at all obvious who those people are, or how to get involved. Regular office hours will make it easier for people to join the effort.
Read more
Session proposals for DrupalCamp LA 2011
Post your session proposals here. Be sure to mention if you're looking for co-presenters!
Update: Reverse proposals are good, too! If there's something you'd like to see someone else present, you can post your requests and suggestions.
Read moreFinding Drupal Association board candidates with nonprofit experience
The Drupal Association is reaching out to identify candidates for a diverse board, and one of the areas we're relatively lacking is candidates with a lot of nonprofit experience.
The current DA board is mainly associated with Drupal shops (and mainly US-based).
You can find information on the nominations committee and process here: http://association.drupal.org/node/1139.
Read moreImproving accessibility oversight for a website
Often a single organization will have multiple staff creating content. The staff member who is most concious of accessibility requirements will often discover content that other staff members have added that are not as accessible as they might be, if only because certain checks cannot be automated. It would be good if Drupal modules provided productivity tools for these individuals who have oversight whether by responsibility or default.
Read more
Core Context UX: Page & Component library
Drupal’s site building user experience currently consists of moving between a lot of different tools and interfaces. Within Drupal 8 we want to unify these experiences (blocks, menus, views, panels…) more.
The experience that we are focusing on, is that of creating the front-end of your website - where content, blocks, views, menus are placed on pages and how these can be configured.
Read more
Core template conversion methodology - cart before the horse?
The way we have been approaching changes to core templates has, at least afaict, been a piecemeal affair - we change one or two templates at a time working through the various markup issues until such time as we have some broad consensus and ta da, here's our new template.
This bottom-up-esque methodology seems reasonable because we we are not overhauling the entire system at any one time and are just looking to adjust or tweak parts of it.
I think this has worked OK in the past, however I tend to think this methodology has a few drawbacks.
Read more
Summary of Configuration Management sprint
Last week, before DrupalCamp Colorado, Greg "heyrocker" Dunlap, David Strauss, Larry "Crell" Garfield, and Karoly "chx" Negyesi met to hash out architectural details and whip up some prototype code for the Drupal 8 Configuration Management initiative.
What problems are we trying to solve?
- Currently there is no good way to move Drupal configuration information between environments because this data is scattered throughout the database in a variety of formats, oftentimes intermingled with content.
- This also makes it impossible to version control this information, to store history, and to be able to rollback changes.
- Every module stores their configuration data in a different format, there is no standardization at all, even within core.
- There is also no standard API for saving this information (aside from the simple case of the variables table) so developer often roll their own solutions.
- The entire contents of the variables table is loaded on each page request, even for rarely-accessed data, leading to memory bloat.
- It is cumbersome to manage information that is different between server environments for the same project (database information, api keys, etc.)
We specifically are NOT (yet) trying to solve the problem of contextual configuration; only the underlying API that handles getting/setting this configuration data and shuffling it around to different sites.
The code that was developed at the sprint as a prototype is available at http://drupal.org/sandbox/heyrocker/1145636 for your reviewing pleasure. The main things to look at are the includes/config.inc and modules/config/config.test files.
What follows is a summary of the results. Your feedback is welcomed!
Read more
DrupalCamp LA 2011 (August 6th & 7th)
Get ready for the fifth annual DrupalCamp LA this August 6-7th. Mark your calendars... this year is a milestone for us and we’re going all out!
Update: Videos posted at http://replay.uci.edu/clients/drupal
Drupal has changed, so we updated the camp accordingly. Join us for this jam-packed weekend of free Drupal community training - now with even more awesome sauce!
Event Highlights:
* Job Fair
* Drupal 7 Sessions
* Dedicated Beginners Track
* Step-By-Step Workshops
* Drupal Training Video Archives
