This project is not covered by Drupal’s security advisory policy.
This is the project page for the code and issue tracking for Greater Los Angeles Drupal Camp 2013 and future GLADCamp conferences.
Conference Website: http://gladcamp.org
Twitter: https://twitter.com/GLADCamp
Working Group: http://groups.drupal.org/gladcamp
Issue Queue: http://drupal.org/project/issues/gladcamp
Best practices for getting involved:
- We're using a basic Kanban-style approach with tasks in our issue queue. You're welcome to chime in on any existing issues that match your interest or expertise as well as open new ones;
- Each task should be owned by someone and no issues should be unassigned;
- There's no need to include "GLADCamp" in the name — all issues are already about GLADCamp;
- Update your email notification settings at https://drupal.org/project/issues/subscribe-mail/gladcamp
- When mentioning other issues or linking to them, use
[#000]notation; - Try to use a "3 email rule" — if an email between individuals turns into a thread of 3 or emails, get on the phone, Google+ hangout, etc. and work it out more quickly;
- Are you stuck on something? Ask for help! Use the GLADCamp issue queue at http://drupal.org/project/issues/gladcamp, the working group at http://groups.drupal.org/gladcamp or the text chat at https://web.groupme.com/groups/3335823
- For more discussion of shared best practices for managing this project, post a comment at http://drupal.org/node/1908834
Project information
- Created by christefano on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.






