Commit d495ad54 authored by Clayton Dewey's avatar Clayton Dewey

Add working group info to documentation

parent a8c956cf
......@@ -57,3 +57,122 @@ Any member is welcome to request becoming a technical lead by
* a current tech lead then nominates them
* One other tech lead must approve the person
* Once approved, that person's gitlab account is elevated to the Owner role
Working Groups
Working groups are a way for members to work in a modular way. They are semi-autonomous, checking in with the larger cooperative when appropriate.
User experience working group
Team lead: Clayton Dewey
The user experience working group is focusing at the moment on laying the foundation for a fantastic user experience for both contributors and supporters of Drutopia as well as the end user of the Drutopia tools we are building.
To do this we are doing the following -Contributor UX
* Expanding on the current README.MD (done)
* Writing a CONTRIBUTING.MD (done)
* Defining a Code of Conduct (done)
End User UX
* Conducting user research through surveys and interviews (ongoing)
* Adding the survey to (done)
* Filing user experience issues at
* Testing user experience tickets ready for review
We are looking for help in the following ways:
* Completing the survey -
* Being interviewed
* Sharing the survey
* Interviewing people
Project management working group
Team lead: Leslie Glynn
Goal: to help the Drutopia project through
* tracking the objectives/issues of each of the working groups
* documenting and tracking the project schedule and milestones
* assisting the leadership team through reporting on project status
Users working group
Team lead: Leslie Glynn
Goal: to help the Drutopia project through
* communicating with potential users of Drutopia to identify features of interest
* finding commonality of desired features among the various users
* assisting the leadership team in defining features and priorities in the Drutopia roadmap
Documentation working group
Team lead: Rosemary Mann
`Documentation issues <[]=Documentation>`_
We’ll be tackling all areas of documentation including end user documentation for non-technical users. While some of these tasks will not happen until we’re further along in the development cycle, we want to ensure that solid documentation goes hand in hand with development.
Outreach/marketing working group
Team lead: Ben Melançon
Outreach/marketing seeks to ensure that every web designer, styler, developer, and site builder knows of Drutopia’s goals and approaches, and knows how to participate in Drutopia if they are interested. We also work to communicate the potential of Drutopia to organizations who need websites, and to distill the membership offering so they can make the decision to join.
Development working group
Team lead: Nedjo Rogers
The development working provides technical guidance and support to the Drutopia initiative.
Development issues
`Development issues <>`_.
**Technical specifications**
* Produce and maintain technical specifications of Drutopia-compatible features and distributions.
* Evaluate and make recommendations on specific solutions to be used in Drutopia. Example: will there be a standard base theme?
**Code development**
* Contribute to and maintain Drutopia extensions. See the list of extensions used in Drutopia.
**Current priorities**
Looking to get involved? Here are some current priorities and gaps.
* Review of the `technical guide <>`_.
* Open issues in the `Configuration Sync module <>`_.
* Lead development for planned `Configuration Merge <>`_ and `Block Theme Sync <>`_ modules.
Co-op working group
Interim team lead: Rosemary Mann
One of the core aims of Drutopia is to create a different kind of economic model. To this end we’re are envisioning the creation of a platform co-op where end user groups are members. We have also explored the idea of a multi-stakeholder co-op so that worker members are also included. This working group will tackle the research, business planning, and organizational work to create a new co-op.
Features working group
Interim team lead: Nedjo Rogers
At its most basic, a distribution is a set of features that will work seamlessly together but that can also be used separately or, ideally, in other distributions. Building out those features is much like site building but with the extra complexity of each being a generic solution and with challenges of interoperability and consistency. The Features working group will take on the concrete work of developing and fine-tuning the features that will become Drutopia.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment