BoF Sessions

I tried posting a long comment and it was deemed "spam" and not allowed, so I'm trying a shorter one now. I've listed a bunch of potential BoF topics at the bottom of my profile page: http://sf2010.drupal.org/user/4683

Please let me know what you'd like to learn about.

Cheers,
Kristen

There is highly likely to be a drupal services bof at some point during the week if we have enough interest. In addition there will be a drupal services specific code sprint as part of the code sprints on the Sunday and Thursday.

Looking for all who are interested in exploring all aspects of drupal and integration with a Enterprise CRM. Particularly Salesforce.com, but all is welcome.

This is a discussion I would like to be a part of. I am very interested in scaling with Pressflow and Varnish. We're getting hit with too many database connections from Google's endless spidering, some we could mitigate by dividing reads and writes through replication or load balancing.

I'd like to meet other folks who are interested in harnessing Drupal's power to do some good in the world. I use a Drupal site for my LGBTQ social justice nonprofit organization. Anybody else?

Am very interested in discussion of ideas/tools/techniques in migratating existing custom internal network relational database applications to Drupal based web platform which meet HIPAA (Health Insurance Portability and Accountability Act) requirements.

Security, detailed query generation and highly structured output are important.

Thank you!

Proteon has conducted a survey about Drupal hosting requirements by Drupal shops in Europe.

If there is interest, I would like to:
- present the results of the survey
- ask more opinions about hosting requirements
- discuss the best hosting solutions based on the survey
- know who has a need for good Drupal hosting in Europe

The questions in the survey were:
1) how many drupal sites did you develop?
2) what modules do you use most frequently?
3) how often have you hacked the core or core modules?
4) what system do you host on?
5) how do you do security updates?
6) how important are security updates?
7) what other tools do you use in conjunction with Drupal?
8) how do you do deployment and releases?
9) do you have sites that have to be up allways (99,9% +)?
10) what is the biggest challenge in Drupal hosting?

Lex

I'm interested in meeting with other Drupallers representing philanthropic foundations and charities. If there's enough of us it might become a BoF group or just a dinner out together.

Would love to chat with others on how they're using Aegir's new multi-server functionality. Has anyone reserved a room for this yet?

@axolx,

Yep, thanks to briwood! Please add your thoughts/ideas in the thread on GDO here: http://groups.drupal.org/node/61708

We will meet again, probably for lunch one day. There's a thread on ravelry in the drupal knitters group with more info.

Crocheters welcome too of course, but please, no nalbindingers.

I'm coming from UC Irvine, and I'm interested too.

We are planning to hold 2 BoF's on Monday. One if the morning for the CiviCRM user and the other in the afternoon for a CiviCRM integrator / developer

If there is sufficient interest, i'd be happy to hold a BoF on CiviSchool, which is a drupal / civicrm modules that helps manage parent/student/staff for K-8 schools

lobo

Hi all!

With the free (GPL) OQGraph engine in MySQL we can handle tree and network traversal easily now.
cafuego has written a drupal module friendlist_graph which extends friendlist.
We'd love to do a BoF exploring this and more uses, as it's clearly something that sites have been avoiding because it used to be just to painful to handle.

Cheers,
Arjen.

Is there anyone else going to Drupalcon who belongs to the Masons / Elks / Lions / Rotary / Kiwanis / Odd Fellows / Grange / etc., and is using Drupal for their district or local lodge/chapter web site? I started a group last year with the eventual goal of creating a 'Lodges' install profile, but haven't really pursued it & would welcome a chance to jump-start the project and start bouncing ideas around with others.

There are a bunch of "lower ed" people at DrupalCon. Can we organize a BOF at this late date?

I am interested in attending a BOF on Dreamweaver and the xtnd.us extensions, I would like to learn more.

We had a good BoF on strategies and techniques for making FileMaker Pro talk to Drupal (and vice versa) at DrupalCon DC last year. Being in San Francisco this week, chances are good that there's a little more FileMaker/Drupal overlap. Let's compare notes!

A bunch of people at the Fusion session raised hands for a genius bar/BoF by the TopNotchThemes crew, so it's on the board for Wednesday afternoon at 3pm. Bring your laptop and your theming questions, and we'll be there to sit down with you one on one and help out :)

There are no public Mercury EBS images at the moment that I know of. We intend to release ones when we release 1.1 at the end of this month. Current images could be converted to EBS but some modifications of the BCFG2 config files would be required (Mercury 1.1 takes EBS into account).

Hope this helps,

Greg
--
Systems Administrator and Mercury Developer
Chapter Three

On Tuesday, April 20 at 11:00 in Room 262, twenty-two of us attended a round-table discussion of concerns when performing major release upgrades. The session was recorded and a link to that recording will eventually be posted here. In the meantime, the list of concerns collected included:

1. Core hacks
2. Contributed modules
3. Hacked contributed modules
4. Changes to the API affecting custom modules
5. Changes to the theme API
6. Business logic stored in the template layer
7. Code stored in the database, especially block visibility code which can often go overlooked
8. The amount of time a site has to be down to perform an upgrade
9. Synchronizing content between the upgraded site and the live site

To address items 1, 2, and 3 people generally relied on their version control software. Red Mine was recommended as an excellent tracking tool allowing tickets to reference commits and folks encouraged requiring and policing that no commit are made that do not reference a ticket id number. At the very least, people recommended that every commit should explain not just what was done, but *why* it was done, perhaps including a place on the site where the hack can be observed to facilitate testing after upgrade.

http://drupal.org/project/deadwood for (5.x -> 6.x only) and http://drupal.org/project/coder were both mentioned as invaluable in addressing items 4, 5, and 6.

Many folks approached major release upgrades as an opportunity to rebuild the sites in question and advocated using the Migrate module to move the data into the rebuilt site.

One workflow process suggested included:
Identify all the contributed modules installed and their version
Determine if there is a release for the new version
If yes, list the version in the spreadsheet and mark the cell green
If there's a dev version, list the version and mark the cell yellow
If there isn't a module, mark the cell red
All new modules need to be tested to see that they'll provide equivalent functionality.
Look for new ways to build the equivalent functionality. It could be in core now.

Running an upgrade to see what breaks was identified as another legitimate strategy.

My apologies in advance for what I missed. Check the audio for more detail.