Drumbeat/website/developers

Background

• http://drumbeat.org
• Building a better Drumbeat.org. Together.

People

• Gerv
• Carlo
• Jamey Boje Drupal Developer | Front End Developer | Visual Designer.
• Ned
• Matt
• Paul Booker (Drupal Developer | Wiki maintainer ) (Sponsored by Ian Hayward @ Appcoast)
• plus many others -- please add

Bugs

• These are the links drumbeat uses to report & fix bugs.
• Gerv or Paul: What's the process for Drumbeat? How do we make it easy for our community to report bugs?
  • on the drumbeat website?

• Bug List
• Submit a New Bug

Bespoke modules and derivative theme

• Do we need this for Drumbeat? .. Our approach on Spreadthunderbird is to keep only our own bespoke modules / theme in SVN
• Spreadthunderbird examples below:

• SVN: http://svn.mozilla.org/drumbeat.org/trunk/sites/all/modules/drumbeat  ?
• SVN: http://svn.mozilla.org/drumbeat.org/trunk/sites/all/themes/drumbeat  ?

Notes: External checkout of a subversion repository can be done as follows ..

• svn checkout <PROTOCOL>://<USER>@<IP|DOMAIN>/subversion/<REPOSITORY>/trunk .
  • protocol could be svn+ssh (READ / WRITE) , http (READ ONLY) , https (READ / WRITE)

Meetings

• QUESTION: Should we have weekly meetings just for Drumbeat web dev on Mondays right after the community call? A half-hour each week just to talk about web & social media stuff?

Every Monday at 8am PST https://wiki.mozilla.org/Drumbeat/WeeklyUpdates

• Mozilla Drumbeat | IRC channel
• Mozilla Drumbeat Google Groups
  • New Google Group Tied to Mailserve.

Getting Started

GERV: Can we draft our own set of step-by-step instructions here?

Want to help out with testing?

1. Download the drumbeat archive & sanitized database here

Want to help out with improving our bespoke modules or theme?

1. Download the drumbeat archive & sanitized database here (which excludes bespoke modules or theme)
2. Checkout from SVN our bespoke modules and our drumbeat theme

For more specific detailed instructions on how to setup a local MAMP server for development , please click here to read our tutorial. For generic instructions on setting up a local server on different OS's please click here

How to develop Drumbeat

1. Request svn access if you don't already
2. Find a bug to work on
3. Fix the bug
4. If the bug fixes a problem with a contributed module on drupal.org then create a patch and submit to the module maintainer for review on its project page on drupal.org. As soon as the patch is accepted and the module updated on drupal.org then update the bug on mozilla.org with the name of the module and the tag attached to the new release so that the module can be updated on Drumbeat. If the bug fixes a problem with bespoke code that is in SVN on mozilla.org then create a patch upload to Bugzilla and request a review by Paul. Once the patch has been reviewed/accepted, commit to SVN with the bug # in the commit message and a brief description of what the patch does or the bug title. Add a comment to Bugzilla with the revision number of the commit: 'rXXXX'.
5. Mark the bug as fixed
6. QA verifies bug and marks as VERIFIED if it's really been fixed
7. Please commit changes back to drupal.org wherever possible as it's important that we don't fork our distribution

Basic Functionality Testing

(Coming soon)

Do's and Don'ts

• Use PEAR coding style
• Always comment your code.
  • Function definition blocks at the least
  • Inline comments for complex code, use your best judgment
• Always put a bug # and comment in your commit messages.
• Don't embed HTML code in module files.
  • Define templates and keep presentation separate from logic code.
• Don't touch the Drupal core.
• Don't touch the Drupal core. (Yes, worth repeating!)
• Don't push on Fridays or when you won't be around to verify the changes.

Staging Server

• http://stage.drumbeat.org/
• https://stage.drumbeat.org/ (points to the same location) Have we purchased the SSL certificate for drumbeat.org?
• Bespoke code committed to SVN will automatically be pulled onto stage server from trunk every 10 minutes ?
• Updates to drupal core and contributed modules will be pulled directly from drupal.org CVS servers
• All pages are served behind a caching reverse-proxy which sometimes gives rise to problems accessing the site?

Deployment

• File an IT bug requesting that changes on stage be synchronised with production
• When IT closes the bug, verify the fixes/features are working.

Scheduled work for this year

• Upgrade Drumbeat to D7

• Other ideas for discussion
  • How to sanitize the database for development on a local server