...
 
Commits (10)
=================
Drutopia Partners
=================
A great way to serve grassroots organizations is by becoming a Drutopia Partner. Partnership is available to both agencies and freelancers.
As a Drutopia Partner you and your client(s) receives
* membership to the Drutopia Software Cooperative
* a local, test and live environment with continuous integration for each client site
* membership to MayFirst/PeopleLink, which includes the following for each client site:
* Web hosting
* Email
* Email lists
* NextCloud accounts
* Discourse accounts
* same day Drupal and Drutopia updates applied by the Drutopia team
* a Git repository with full control over your client's theme and certain configuration settings
* Support forum to ask questions and report bugs.
* Public recognition on drutopia.org
To become a Drutopia Partner,
* read and agree to the :doc:`Points of Unity <goals.html#points-of-unity>` and :doc:`Code of Conduct <drutopia-code-of-conduct.html>`
* sign up each of your :doc:`Platform Cooperative <platform-cooperative.html>` clients up
* commit to supporting the client's theme and configuration
* pay Drutopia Platform Cooperative membership dues on time
* contribute improvements back to the Drutopia project when possible
* serve as a helpful intermediary between your clients and the Drutopia project
# Hosted (SaaS) Drutopia Standards
To be recommended by Drutopia as a host, these qualifications—at
minimum—must be met:
* All people or organizations hosted on the platform are members of the Drutopia cooperative, and the membership fee is passed on to the cooperative.
* The resources dedicated to each site meet the Drupal 8 system requirements.
* The host must support SSL (https://)
* Drupal core must be supported with security updates
* All approved Drutopia contributed modules must be supported with security updates (supporting additional is allowed of course)
* All approved Drutopia configuration sets must be available for use (supporting additional is allowed of course)
* All approved Drutopia install profiles must be available on new site launch (supporting additional is allowed of course)
......@@ -35,10 +35,9 @@ The code is open source, and `available on GitLab`_, as are `our issues`_.
:maxdepth: 2
:caption: Organization & Structure
decision-making
working-groups
hosted-drutopia-standards
platform-cooperatives
software-cooperative
platform-cooperative
drutopia-partners
.. _contributing:
......
==================================================
Platform Cooperative (Libre Software as a Service)
==================================================
Drutopia is built to support the proliferation of Libre Software as a Service offerings, organized as <a href="https://en.wikipedia.org/wiki/Platform_cooperative">platform cooperatives</a>. A platform cooperative is an online platform owned collectively by its members.
The first of these platform cooperatives is designed by grassroots organizers to help one another act, mobilize and support one another.
People and organizations can join the platform coop and have a hosted website for $50/month. This gives you:
* membership to the Drutopia software cooperative
* a local, test and live environment with continuous integration
* membership to MayFirst/PeopleLink, which includes the following:
* Web hosting
* Email
* Email lists
* NextCloud accounts
* Discourse accounts
* same day Drupal and Drutopia updates applied by the Drutopia team
* a Git repository with full control over your theme and certain configuration settings
* Support forum and <a href="https://chat.drutopia.org/">Mattermost channel</a> to ask questions and report bugs
* Public recognition on drutopia.org
Hosted (SaaS) Drutopia Standards
================================
Right now we partner with MayFirst/PeopleLink for hosting. However, we have an intentionally open and distributed model for hosting to allow other providers to be involved.
To be recommended by Drutopia as a host, these qualifications—at minimum—must be met:
* All people or organizations hosted on the platform are members of the Drutopia cooperative, and the membership fee is passed on to the cooperative.
* The resources dedicated to each site meet the Drupal 8 system requirements.
* The host must support SSL (https://)
* Drupal core must be supported with security updates
* All approved Drutopia contributed modules must be supported with security updates (supporting additional is allowed of course)
* All approved Drutopia configuration sets must be available for use (supporting additional is allowed of course)
* All approved Drutopia install profiles must be available on new site launch (supporting additional is allowed of course)
If you are interested in becoming a recommended Drutopia host contact the Drutopia leadership team at info@drutopia.org
# Platform Cooperatives
Drutopia is built to support the proliferation of [platform cooperatives](https://en.wikipedia.org/wiki/Platform_cooperative), online platforms owned collectively by its members.
The first of these platform cooperatives is designed by grassroots organizers to help one another act, mobilize and support one another.
If you are interested in joining an existing platform coop or starting your own using the Drutopia architecture, contact the Drutopia leadership team at info@drutopia.org
## Solidarity Libre Software as a Service
A hosted option is available for $50/month which provides the following:
* Platform Cooperative membership
* Security updates
* Email aliases
* NextCloud (and other MayFirst services)
* Hosting Support
* Training & Documentation
* Mattermost Support Channel
* One hour "ask anything" each month
=============================
Drutopia Software Cooperative
=============================
The Drutopia project is governed cooperatively, with a leadership team providing strategic guidance, technical leads deciding technical decisions and members driving forward the roadmap.
Membership
----------
Membership is open to all, simply -
* Pay an annual membership due of $10-100 ($50 recommended) or one time lifetime membership of $100
* Agree to the :doc:`Drutopia Code of Conduct >drutopia-code-of-conduct.html>` and :doc:`Points of Unity <goals.html#points-of-unity>`
Members are encouraged to request and vote up/down features, report bugs and contribute to the project.
Leadership Team
---------------
The Leadership Team makes strategic decisions regarding Drutopia. This includes vision, mission, goals, outreach strategy and target audiences, and licensing. Decisions are made by consensus.
Joining the Leadership Team
The current leadership team is:
* Ben
* Clayton
* Leslie
* Nedjo
* Rosemary
We are currently looking for a representative for front-end development. Open positions will be filled by consensus from the current leadership team.
Once the project has been established for a longer time a democratic process driven by Drutopia members at large will be implemented.
Leadership Team Elections
=========================
Elections of the Leadership Team will happen annually, with our first election to be held November 2018. Each member gets on vote.
Technical Leads
---------------
Technical leads make the final call on technical decisions.
Current technical leads are:
* <a href="https://gitlab.com/mlncn">Ben</a>
* <a href="https://gitlab.com/cedewey">Clayton</a>
* <a href =https://gitlab.com/nedjo">Nedjo</a>
* <a href="https://gitlab.com/rosemarymann">Rosemary</a>
Any member is welcome to request becoming a technical lead by
* asking a current tech lead to become one
* 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
clayton@drutopia.org
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 drutopia.org (done)
* Filing user experience issues at gitlab.com/drutopia/drutopia
* Testing user experience tickets ready for review
We are looking for help in the following ways:
* Completing the survey - https://www.drutopia.org/survey
* Being interviewed
* Sharing the survey
* Interviewing people
Project management working group
=================================
Team lead: Leslie Glynn
leslie@drutopia.org
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
leslie@drutopia.org
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
rosemary@drutopia.org
`Documentation issues <https://gitlab.com/groups/drutopia/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name[]=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
ben@drutopia.org
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 nedjo@drutopia.org
The development working provides technical guidance and support to the Drutopia initiative.
Development issues
`Development issues <https://gitlab.com/groups/drutopia/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name%5B%5D=Development>`_.
**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 <http://docs.drutopia.org/en/latest/technical-guide.html>`_.
* Open issues in the `Configuration Sync module <https://www.drupal.org/project/issues/config_sync>`_.
* Lead development for planned `Configuration Merge <https://www.drupal.org/project/config_merge>`_ and `Block Theme Sync <https://www.drupal.org/project/block_theme_sync>`_ modules.
Co-op working group
===================
Interim team lead: Rosemary Mann
rosemary@drutopia.org
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
nedjo@drutopia.org
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.
# Working Groups
## User experience working group #UX
Team lead: Clayton Dewey clayton@drutopia.org
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**
1. Expanding on the current [README.MD](https://gitlab.com/drutopia/drutopia-distribution/issues/20)
2. Writing a [CONTRIBUTING.MD](https://gitlab.com/drutopia/drutopia-distribution/issues/19)
3. Defining a [Code of Conduct](https://gitlab.com/drutopia/drutopia-distribution/issues/17)
**End User UX**
1. Conducting user research through [surveys](https://gitlab.com/drutopia/drutopia-distribution/wikis/survey) and [interviews](https://gitlab.com/drutopia/drutopia-distribution/wikis/interview)
2. Adding the survey to [drutopia.org](http://drutopia.org/)
I am looking for both help in the following ways
1. Joining the working group in a regular or semi-regular way
2. Completing the survey (for now answer the questions and email them to me)
3. Being interviewed (email me letting me know and we can set up a time!)
4. Sending me contact info for folks you think would be down to fill out the survey or be interviewed
5. Share the survey directly with folks (again have them email me their answers for now)
6. Interview people directly (email me and we can walkthrough what that looks like, which shouldn't take long to do)
7. Adding the survey as a form on Drutopia (if you can do this, let me know and I'll add you as a contributor to the project)
## Project management working group
Team lead: Leslie Glynn leslie@drutopia.org
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 leslie@drutopia.org
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 rosemary@drutopia.org
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.
[Documentation issues](https://gitlab.com/groups/drutopia/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name[]=Documentation)
## Outreach/marketing working group
Team lead: Ben Melançon ben@drutopia.org
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 nedjo@drutopia.org
The development working provides technical guidance and support to the Drutopia initiative.
[Development issues](https://gitlab.com/groups/drutopia/issues?scope=all&state=opened&utf8=%E2%9C%93&label_name%5B%5D=Development)
### 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](http://www.drutopia.org/drutopia-drupal-extensions).
### Current priorities
Looking to get involved? Here are some current priorities and gaps.
* Review of the draft technical guide.
* Open issues in the [Configuration Sync](https://www.drupal.org/project/issues/config_sync) module.
* Lead development for planned [Configuration Merge](https://www.drupal.org/project/config_merge) and [Block Theme Sync](https://www.drupal.org/project/block_theme_sync) modules.
## Co-op working group
Interim team lead: Rosemary Mann rosemary@drutopia.org
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 nedjo@drutopia.org
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.
\ No newline at end of file