Drupal

Purpose

The WIGG-Drupal group is intended to bring together those interested in deploying and developing Drupal websites at Illinois in order to create common practices, codebases, and support documentation.

Objectives

  • Create a standard Drupal installation that can be used across campus: The Illinois Drupal Framework
  • Create a community of practice around Drupal on campus to coordinate the development of new functionality
  • Raise awareness of Drupal and its uses

Deliverables

  • A regularly updated Drupal distribution that is available to all units.
  • Documentation for deploying this Drupal distribution to campus hosting options
  • End-user documentation for using the editing tools in the Drupal distribution
  • A community of Drupal developers and support people to further the usefulness of Drupal on campus

Out-of-scope items

  • Supporting individual units’ development and special-function needs within Drupal
  • Supporting individual Drupal sites and site administrators
  • Migrating sites to the new framework
  • Managing a campus “push button” Drupal service
  • Creating a new hosting option for Drupal sites

Join Us

Learn more about the WIGG-Drupal group by exploring the links below.

Team Lead Responsibilities

  1. Prepare agenda and lead regular meetings of the WIGG Drupal Group
  2. Provide updates from Steering and other WIGG committee meetings to the WIGG Drupal Group on topics that might impact the group
  3. Provide updates during WIGG Monthly Conversations
  4. Manage the Illinois Drupal Framework GitHub Repositories: Profile, Theme, and Core. Review issues, pull requests, and documentation. Assign issues to group members
  5. Coordinate group members in developing features for the Illinois Drupal Framework
  6. Be available for a majority of meetings, with the understanding there will be weeks or even months where a leader will be unavailable to attend due to vacations, work conflicts, etc.

Member Responsibilities

If you’d like to contribute to the WIGG Drupal group, here is what you can expect:

  1. Bring the needs and solutions of your unit or department to the group, and help us share your solutions with the rest of campus
  2. Collaborate with other group members come up with creative solutions
  3. Communicate with the team lead and rest of members of what you can help with based on vacations, work conflicts, etc.
  4. Be available for at least some meetings, with the understanding there will be weeks or even months where a member will be unavailable to attend due to vacations, work conflicts, etc.
    • We ask that you don’t take more than you can handle. 
    • If you find that you cannot devote any time to this group, it’s OK to leave. Let the team lead know. You can leave and come back as often as you need. 
  5. Contributing code to the project:
    • There is no expectation that this code is “yours” — you are donating this code to WIGG and it may be enhanced by you or others based on WIGG meetings
    • Please follow the Drupal coding standards
    • Any coding changes should be tied to an issue in the repository the changes are being made. The issue should have its own branch, with the changes committed to that issue branch. Finally, a pull request should be made when the changes are ready to be merged.