CHAOSS Evolution Working Group

Formerly known as the Growth Maturity and Decline Working Group

Join our Mailing List

This CHAOSS working group is using the general CHAOSS mailing list.

Join our Weekly Calls

The Evolution Working Group meets every Monday from 7:30am - 8:30am Pacific Time every other Wednesday. Our next meeting will be on 10th, 2019. All are welcome.

The videoconference URL is https://unomaha.zoom.us/j/720431288.

You can also read our meeting notes.

Introduction

Purpose

Evolution is a working group focused on the lifecycle of open source projects. We do not valence the stages, but seek to build awareness of those stages among consumers of these metrics. Decline can be ok when a project's utility is waning; or terrible if 20% of the entire internet relies on that project. Context matters, and we are not the arbiters of your context. The "valence" of "good/bad" emerges from use cases and YOUR context.

Goal

Currently, the goals are structured in the following focus areas : Issue Resolution, Code Development and Community Growth.

Process

For each area of interest, we're following the goal-question-metric methodology defining questions and metrics that help to answer them.

Introduction
Roadmap for 2019
Metrics
Usage
Implementations
Use Cases
Contributing
Communications
Contributors
License

Roadmap for 2019

Our key focus areas for 2019 are summarized here.

Metrics

The evolution metrics dealt with in this working group are organized in focus areas:

Focus Area	Description
Code Development	Scope: Aspects related to how the source code changes over time, and the mechanisms that the project has to perform and control those changes.
Community Growth	Goal: Identify the size of the project community and whether it is growing, shrinking, or staying the same.
Issue Resolution	Goal: Identify how effective the community is at addressing issues identified by community participants.

NOTE: Please see that the work in the focus_areas is still in progress.

Usage

This is a repository for the Evolution working group. When this working group decides to "release" a version of its metrics, the relevant files will be dumped to the chaoss/metrics repository, as a pull request for updating the CHAOSS metrics with "Evolution metrics release x.y".

Implementations

Example for implementaions can be found here.

Use Cases

The details for the Evolution Working Group are present in use_cases.

Contributing

A few steps as good starting points for contributing to the GMD Working group:

Introduce yourself on the CHAOSS mailing list explaining your interest.
Then, you can have a look at the archives of the mailing lists, at the minutes of past meetings, and at the
By proposing new goals for a focus area, or new questions for learning about those goals, or new metrics for answering those questions. Or by helping to refine goals, and questions.

You can contribute See more details in the contributing file.

Communications

Meetings

The Evolution working group meets frequently. Check details on when we meet, and minutes of past meetings in the meetings document.

Usually, we try to make decisions mainly during the last meeting of each month, so that decisions can be brought when convenient to the monthly main CHAOSS meeting, which is the first meeting of each month. In all the meetings we may have an agenda, but random issues can be raised if time allows, after we're done with the agenda. Whenever possible, and specially if a decision needs to be made, ensure that issues / pull requests about the subject matter were opened some time before the meeting, so that anyone had the opportunity of commenting on them, and make up their mind about that subject matter.

Mailing list

We use the CHAOSS mailing list. Please prefix the message subject with [wg-gmd] if it is specific to this working group.

Contributors

Maintainers

Core Contributors

The criteria for becoming a core contributor is to participate at least once per month over a period of 3 months. Participation could include providing feedback in the Evolution working group meetings, providing feedback on docs, or making other contributions on GitHub (commits / issues). People not participating over a 3 month period may be removed as core contributors.

If you'd like to be on our squad, an easy way to start is by going through the issue list and fixing some or adding to the conversation.

License

The documents in this repositories are released under the MIT License. See LICENSE for details.

parthsharma2/wg-evolution