Skip to content

Latest commit

 

History

History
117 lines (74 loc) · 5.92 KB

README.md

File metadata and controls

117 lines (74 loc) · 5.92 KB

CHAOSS App Ecosystem Working Group

Introduction

The mission of this working group is to build a base set of metrics that is focused on the needs of open source communities that are part of the FOSS app ecosystem.

Table of Contents

Background

Problem Statement

The diversity of FOSS is vast and there are many different kinds of communities out there. Some projects are modest with 5-6 contributors working on something in their spare time. Some are the foundation of a company where hundreds or thousands of developers are working on them. This working group is focused on communities that are a combination of both. Aspirational projects that scale to hundreds or thousands of contributors that require community management that have different goals and decision making than a corporate backed or inner source project but still requires sophisticated metrics.

Opportunity

This is a gap that we believe should be filled by building an alliance amongst major stakeholders to build a metrics standard amongst a class of communities that have never actually built the level of sophistication before. As these tech communities migrate to more sophisticated development platforms like Gitlab - it's possible to start building foundational technologies that we can build on.

Goal

The goals of the working group is to build a base set of metrics that can shared amongst a set of communities (today that is GNOME and KDE) that we can then build upon for other communities.

Objectives

A few key objectives:

  • Document and explore the decisions that we make that we need metrics to explore
  • Build a set of metrics from those decisions
  • Present those metrics to the CHAOSS community for feedback

Reports and progress

Backlog

In-Progress

Completed

Other outputs

Workflow

Contributing

  • GitHub PR workflow
  • Commits require DCO-sign-off (e.g., git flag "-s")
  • Each PR requires two (2) sign-offs (i.e., approved reviews) from maintainers, other than the submitter. (socially enforced)

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 regular 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.

All Contributors (ordered by first name) Georg Link, Neofytos Kolokotronis, Nuritzi Sanchez, Shaun McCance, Sri Ramkrishna

Are you eligible to be on this list? You are if you helped in any capacity, for example: Filed an issue. Created a Pull Request. Gave feedback on our work. The team will try to update this list monthly, but please open an issue or post on the mailing list if we've missed anyone.

If you find yourself missing, please create a pull request or reach out to a maintainer. If you find yourself listed here and want to be removed, please create a pull request or ask a maintainer.

License

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

Copyright © 2018-2020 CHAOSS Project