1 / 11

EERE Web Coordinators

EERE Web Coordinators Meeting: July 21, 2011. EERE Web Coordinators. Hosted by Drew Bittner. July 21, 2011 Phone: +1 (312) 878-0211 Access Code: 382-746-699. Monthly Meeting. Agenda. Around the Room (15 minutes) – Drew Drupal Update (30 minutes) – Michael, Mike, and Alex

fabienne-kael
Download Presentation

EERE Web Coordinators

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EERE Web Coordinators Meeting: July 21, 2011 EERE Web Coordinators Hosted by Drew Bittner July 21, 2011 Phone: +1 (312) 878-0211 Access Code: 382-746-699 Monthly Meeting

  2. Agenda • Around the Room (15 minutes) – Drew • Drupal Update (30 minutes) – Michael, Mike, and Alex • Content Reviews (10 minutes) – Drew • Standards Tip (5 minutes) – Elizabeth

  3. Adding a New Module or New Functionality • Make a proposal for the new functionality to the PRT. • Create your developers’ GitHub account(s) (individual developers). • Contact EES (Alex Clayborne) to request access to the eere.energy.gov codebase in GitHub. • Install the eere.energy.gov installation profile on your development server. • Develop/test against the EERE codebase. • Request a code merge (back to GitHub). Note: EES will be responsible for managing the overall codebase and will act as the EERE Technical Representative for Drupal development.

  4. Continuous Integration • We are using Jenkins Continuous Integration software. • All code will be merged/tested against the latest stable build of eere.energy.gov codebase. • Code will also undergo a code style review. (http://drupal.org/coding-standards) • Code that fails either way will not be pushed to production.

  5. Staging • Your site code will be staged in the ECWHE environment. • Your code will be scanned for vulnerabilities. • Your developer(s)/team content provider(s) will be provided account information to log into the staged drupal instance.

  6. Production • Once tests and code review are passed a production push can take place. • Your developer(s)/team content provider(s) will be provided account information to log into the production site.

  7. How to access Drupal Environment • If you don’t already have an account in OpenText: • Complete Rules of Behavior and Account Authorization forms • You’ll receive account credentials for the site.

  8. Questions Contact: Alex Clayborne 301-903-8819 Alexander.clayborne@hq.doe.gov

  9. Content Reviews • About 18 months after your project goes live, we’ll ask you to reassess your project and its content and confirm: • The content is approved as still current and valid. • The content needs updating (with notes on what specifically must be updated) or extensive modification. • The content may be archived and taken down.

  10. Communication Standards Tip We have two new updates this month! • Graphic Guidelines: Includes graphic requirements for the old and new templates • Testing Suite: Now includes IE9, Firefox 4, and Google Chrome 12.

  11. Wrap Up • Next meeting: August 18

More Related