How We Work
At a high level LocalGov Drupal has:
- a product group of product and service owners which determines the overall direction of feature development
- a technical group of developers which maintains the technical integrity and manages core releases.
The work is then carried out by individual working groups.
When a council wants to add a new feature to LocalGov Drupal they make a suggestion in a meeting or on Slack.
If there's enough interest in the feature, a working group is created. A working group is a collection of councils, at least two, but preferably more. Having multiple councils involved helps with understanding the problem from different angles.
At the first meeting of the working group they set create an aim for the project, and decide how it will get done. For example they may decide to hold meetings or to run it entirely via Slack.
Once the feature has been developed, tested and accepted, it usually goes straight into the main LocalGov Drupal distribution, available to be used by everyone.
For an inside view of the process read this great Medium post by Oliver Hannan of London Councils about working on the 'content lifecycle and workflow group', taking the proposed features through to sprint planning and onto discrete tasks for developers.
Active Working Groups
All of the working groups have Slack channels which you can join if you have an interest. It's not just developers and product owners who are involved, content designers are encouraged to join to provide advice and testing.
The current working groups are:
- content lifecycle
Proposed groups that already have some discussion on Slack or actual development work include:
- microsites/ headless CMS
- directories (using Open Referral)
- html publications (replacing PDFs)
- internal search
If you would like to find out more or have any questions just drop us a line at email@example.com. We are always happy to chat about LocalGov Drupal, provide a demo of the platform, or show how councils are using it.