https://github.com/chaoss/wg-evolution
Working Group focused on Evolution metrics (for software development projects)
Science Score: 36.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
✓Committers with academic emails
2 of 34 committers (5.9%) from academic institutions -
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.6%) to scientific vocabulary
Keywords from Contributors
Repository
Working Group focused on Evolution metrics (for software development projects)
Statistics
- Stars: 39
- Watchers: 15
- Forks: 61
- Open Issues: 1
- Releases: 7
Metadata Files
README.md
CHAOSS Evolution Working Group
Table of Contents
Introduction
Goals
The goal of the Evolution working group is to develop metrics to assess the lifecycle of the open source projects.
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. The 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.
Who should join this working group?
All contributors are welcome to participate in the Evolution Working Group. The areas of interest include Code Development Activity, Code Development Efficiency, Code Development Process Quality, Issue Resolution, and Community Growth.
Background
Formerly known as the Growth Maturity and Decline Working Group. This working group focuses on activity metrics.
Participate
How to Join Us?
You can start by joining and introducing yourself on the CHAOSS mailing list explaining your interest.
Further, you are welcome to participate in our video conferences. The details of these meetings can be found here
Read the agenda and meeting minutes to know the discussions of the previous meetings and find out more about the next one.
As a contributor, you can help us keep our community open and inclusive. We request you to adhere to the guidelines mentioned in the CHAOSS Community: Code of Conduct
Contributing
See the CONTRIBUTING.md for more information.
Metrics
Metrics Focus Areas
The evolution metrics dealt with in this working group are organized in focus areas:
Focus Area | Goal --- | --- Code Development Activity | Learn about the types and frequency of activities involved in developing code. Code Development Efficiency | Learn how efficiently activities around code development get resolved. Code Development Process Quality | Learn about the processes to improve/review quality that are used (for example: testing, code review, tagging issues, tagging a release, time to response, CII Badging). Issue Resolution | Identify how effective the community is at addressing issues identified by community participants. Community Growth | Identify the size of the project community and whether it is growing, shrinking, or staying the same.
Please note that the work in the focus areas is still in progress.
Released Metrics
We are involved in the release of CHAOSS metrics. Check out our published work at https://chaoss.community/metrics/
The translations of these metrics are available at chaoss/translations
Contributors
Chairs
Please feel free to contact our chairs in case you require any sort of assistance.
Amazing CHAOSS Project Contributors
We greatly appreciate our contributors at CHAOSS and look forward to your joining us as well. All CHAOSS Project contributors are listed here
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 regularly, but please open an issue or post on the mailing list if we've missed anyone.
License
The documents in this repository are released under the MIT License. See LICENSE file.
Copyright © 2021 - CHAOSS, a Linux Foundation Project
Owner
- Name: CHAOSS
- Login: chaoss
- Kind: organization
- Website: https://chaoss.community/
- Twitter: chaossproj
- Repositories: 64
- Profile: https://github.com/chaoss
GitHub Events
Total
- Watch event: 1
- Delete event: 9
- Issue comment event: 4
- Push event: 41
- Pull request review comment event: 2
- Pull request review event: 33
- Pull request event: 66
- Create event: 11
Last Year
- Watch event: 1
- Delete event: 9
- Issue comment event: 4
- Push event: 41
- Pull request review comment event: 2
- Pull request review event: 33
- Pull request event: 66
- Create event: 11
Committers
Last synced: about 1 year ago
Top Committers
| Name | Commits | |
|---|---|---|
| Aniruddha Karajgi | a****0@g****m | 105 |
| Matt Germonprez | g****z@g****m | 98 |
| Kevin Lumbard | k****d@g****m | 81 |
| Sean P. Goggins | s@g****m | 77 |
| Jesus M. Gonzalez-Barahona | j****b@g****s | 61 |
| Carter Landis | c****s@g****m | 61 |
| Georg J.P. Link | l****g@g****m | 42 |
| peculiaruc | p****2@g****m | 26 |
| Elizabeth Barron | e****h@n****t | 24 |
| Vinod K. Ahuja | v****a@u****u | 20 |
| Yigakpoa Samuel | 9****a | 19 |
| CMPerniciaro | 4****o | 11 |
| Yash Prakash | y****9@g****m | 11 |
| Tom Mens | t****s | 9 |
| Valerio Cosentino | v****s@b****m | 9 |
| Venu Vardhan Reddy Tekula | v****8@g****m | 9 |
| Dawn M. Foster | d****n@d****m | 9 |
| ilam56 | 5****6 | 8 |
| Alberto Pérez García-Plaza | a****a@b****m | 6 |
| Harshal Mittal | h****4@g****m | 6 |
| Xavier Bol | x****l@s****e | 5 |
| lucasgonze | l****s@g****m | 3 |
| Yehui Wang | y****h@g****m | 2 |
| sarvesh211999 | s****9@g****m | 2 |
| Foundjem | f****m | 2 |
| ritik-malik | r****6@i****n | 1 |
| Seunfunmi Adegoke | 5****a | 1 |
| Saloni Garg | s****0@g****m | 1 |
| Parth Sharma | p****2 | 1 |
| Matthew Tift | m****t@l****m | 1 |
| and 4 more... | ||
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 11 months ago
All Time
- Total issues: 32
- Total pull requests: 124
- Average time to close issues: about 1 year
- Average time to close pull requests: 3 months
- Total issue authors: 13
- Total pull request authors: 32
- Average comments per issue: 7.38
- Average comments per pull request: 0.49
- Merged pull requests: 99
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 50
- Average time to close issues: N/A
- Average time to close pull requests: 19 days
- Issue authors: 0
- Pull request authors: 4
- Average comments per issue: 0
- Average comments per pull request: 0.06
- Merged pull requests: 46
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- klumb (11)
- germonprez (4)
- ElizabethN (3)
- sgoggins (2)
- GeorgLink (2)
- lucasgonze (2)
- vinodkahuja (2)
- king-gao (1)
- emmairwin (1)
- geekygirldawn (1)
- yash-yp (1)
- jgbarah (1)
- li-clement (1)
Pull Request Authors
- peculiaruc (30)
- yigakpoa (22)
- ElizabethN (18)
- geekygirldawn (17)
- germonprez (12)
- vinodkahuja (6)
- sgoggins (4)
- lucasgonze (4)
- yash-yp (4)
- GeorgLink (3)
- klumb (3)
- eyehwan (2)
- pboek99 (1)
- jman793 (1)
- atomo15 (1)