├── .github ├── FUNDING.yml └── ISSUE_TEMPLATE │ ├── 01-metric-idea.md │ ├── 02-new-metric-release-candidate.md │ └── 03-major-revision-metric-candidate.md ├── .gitignore ├── CITATION.cff ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── focus-areas ├── README.md ├── academic-value │ ├── README.md │ └── academic-open-source-project-impact.md ├── communal-value │ ├── README.md │ ├── images │ │ ├── cncf Projects 7_1_2023 - 7_1_2024.png │ │ ├── contributor-recommendability_recommendability-scale.png │ │ ├── project-popularity_issues-and-reviews.png │ │ ├── project-popularity_kubernetes.png │ │ ├── project-recommendability_recommendability-scale.png │ │ ├── project-velocity_visualization.png │ │ ├── recommendability-scale.png │ │ ├── social-listening_circle2.png │ │ ├── social-listening_dashboard.png │ │ ├── social-listening_data-points-table-source.md │ │ ├── social-listening_data-points-table.png │ │ ├── social-listening_expanded-comment.png │ │ ├── social-listening_tool-example.png │ │ ├── social-listening_unified-codex-terms-table-source.md │ │ └── social-listening_unified-codex-terms-table.png │ ├── project-popularity.md │ ├── project-recommendability.md │ └── project-velocity.md ├── individual-value │ ├── README.md │ ├── images │ │ ├── organizational-project-skill-demand_google-trends.png │ │ ├── organizational-project-skill-demand_paper.png │ │ ├── organizational-project-skill-demand_stack-overflow.png │ │ ├── organizational-project-skill-demand_tech-radar.png │ │ └── organizational-project-skill-demand_tech-react.png │ ├── job-opportunities.md │ └── organizational-project-skill-demand.md ├── organizational-value │ ├── README.md │ ├── images │ │ └── labor-investment_csv.png │ ├── labor-investment.md │ └── organizational-influence.md └── social-value │ └── README.md └── metrics ├── CHANGELOG.md └── README.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2] 4 | patreon: # Replace with a single Patreon username 5 | open_collective: chaoss 6 | ko_fi: # Replace with a single Ko-fi username 7 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel 8 | community_bridge: # Replace with a single Community Bridge username 9 | liberapay: # Replace with a single Liberapay username 10 | issuehunt: # Replace with a single IssueHunt username 11 | otechie: # Replace with a single Otechie username 12 | custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2'] -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/01-metric-idea.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Metric Idea 3 | about: Have an idea for a new metric in the Working Group? Use this template to pitch your idea. 4 | labels: ['metric idea', '?: needs triage'] 5 | 6 | --- 7 | 8 | 9 | 10 | # Metric basics 11 | 12 | 13 | * **Metric title**: 14 | * **Metric summary** (1-2 sentences): 15 | * **Why should this metric be created?** (1-2 sentences): 16 | 17 | 18 | # Data collection and measurement 19 | 20 | 21 | **Are there existing tools that could collect this data?** If yes, list them: 22 | 23 | **If this metric involves a lot of raw data, what filters would you use to narrow down the metric?** If applicable, describe ways to filter the data into smaller segments: 24 | 25 | **How would you visualize this metric?** If you have an idea on how this metric should be visualized or displayed so it makes the most sense to a viewer, describe that here: 26 | 27 | 28 | # About you 29 | 30 | 31 | * **Are you interested in authoring this metric together with the Working Group?**: yes|no 32 | * **Have you attended a CHAOSS Working Group meeting before?**: yes|no 33 | * **If not, would you consider joining one to discuss your metric idea?**: yes|no 34 | * **Anything else you would like us to know?**: 35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/02-new-metric-release-candidate.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Metrics Release Candidate 3 | about: Use this template for new metrics 4 | labels: ['Metrics Candidate Release'] 5 | 6 | --- 7 | 8 | This issue is created to collect comments on the <> metric 9 | 10 | This metric can be found here: <> 11 | 12 | ## CHAOSS Metric Quality Checklist 13 | This checklist is used for new metrics to ensure we follow CHAOSS quality standards and processes. 14 | 15 | ### Process 16 | 17 | - [ ] Add the new metric to release notes issue in working group repo 18 | - [ ] Update the [Metrics Spreadsheet](https://docs.google.com/spreadsheets/d/1tAGzUiZ9jdORKCnoDQJkOU8tQsZDCZVjcWqXYOSAFmE/edit) to indicate that the metric is under community review. 19 | 20 | **When above steps are completed:** 21 | 22 | ### Content Quality 23 | 24 | - [ ] Required headings are filled in 25 | - [ ] If any, ensure links to other CHAOSS metrics work 26 | - [ ] Optional headings that have no content are removed 27 | - [ ] Contributors section lists those contributors that want to be named 28 | - [ ] The name of the metric is the same in all locations 29 | 30 | ### Technical Requirements 31 | 32 | - Message that the metric will be part of the next regular release is at top of page: 33 | 34 | ### This metric is a release candidate. To comment on this metric please see Issue [#[put the respective Issue Number here]](URL to issue). Following a comment period, this metric will be included in the next regular release. 35 | 36 | - Metric file name is the full metric name and only contains lower case letters and hyphens (“-”) for spaces 37 | - Images are included using markdown and absolute links (as described in the metrics template) 38 | - Images have at least one empty line above and below them 39 | - Ensure images are placed in image folder and followed [naming convention](https://github.com/chaoss/metrics/blob/master/resources/metrics-template.md) 40 | - Ensure tables within metric are converted as images and placed in the image folder (both original MD and screenshotted PNG format) and follow the naming convention 41 | - No HTML code in the metrics markdown. 42 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/03-major-revision-metric-candidate.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Major Revision to a Metric 3 | about: Use this template for revising a CHAOSS metric 4 | labels: 'Revising Metic' 5 | 6 | --- 7 | 8 | ### Name of the Metric Being Revised 9 | 10 | 11 | 12 | ### Metric Items that Were Revised 13 | 14 | 15 | - Item 1 16 | - Item 2 17 | - Item 3 18 | 19 | 20 | ### Checklist 21 | 22 | 23 | #### Process 24 | *MINOR CHANGES (e.g., copyediting, new image) DO NOT NEED TO BE REVIEWED BY THE COMMUNITY. If a metric is undergoing major changes (e.g., new objectives, new description), please use the following issue template. In both minor and major changes, it is assumed that a pull request has been created to suggest changes. If the metric is under a MAJOR REVISION, please address the following:* 25 | 26 | - [ ] Update the [Metrics Spreadsheet](https://docs.google.com/spreadsheets/d/1tAGzUiZ9jdORKCnoDQJkOU8tQsZDCZVjcWqXYOSAFmE/edit), if necessary, to indicate that the metric is under community review 27 | - [ ] Add the metric revision to release notes issue in working group repo 28 | - [ ] "Metric Candidate Release" label added to the metric release candidate issue when fully ready fo release 29 | 30 | #### Content Quality (check all that apply) 31 | 32 | - [ ] Date of last review has been added to the revised metric at the bottom of the markdown file (month/year) 33 | - [ ] Metric adheres to the current [metrics template](https://github.com/chaoss/community/blob/main/templates/metric-template.md) 34 | 35 | #### Technical Requirements for any Revisions 36 | 37 | - Metric file name is the full metric name (and the name is the same everywhere) and only contains lower case letters and hyphens (“-”) for spaces 38 | - Images are included using markdown and absolute path links (as described in the metrics template) 39 | - Images have at least one empty line above and below them 40 | - Images are placed in image folder and followed [naming convention](https://github.com/chaoss/community/blob/main/templates/metric-template.md) 41 | - There is no HTML code in the metrics markdown file 42 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Byte-compiled / optimized / DLL files 2 | __pycache__/ 3 | *.py[cod] 4 | *$py.class 5 | 6 | # C extensions 7 | *.so 8 | .DS_Store 9 | 10 | # Distribution / packaging 11 | .Python 12 | env/ 13 | build/ 14 | develop-eggs/ 15 | dist/ 16 | downloads/ 17 | eggs/ 18 | .eggs/ 19 | lib/ 20 | lib64/ 21 | parts/ 22 | sdist/ 23 | var/ 24 | wheels/ 25 | *.egg-info/ 26 | .installed.cfg 27 | *.egg 28 | 29 | # PyInstaller 30 | # Usually these files are written by a python script from a template 31 | # before PyInstaller builds the exe, so as to inject date/other infos into it. 32 | *.manifest 33 | *.spec 34 | 35 | # Installer logs 36 | pip-log.txt 37 | pip-delete-this-directory.txt 38 | 39 | # Unit test / coverage reports 40 | htmlcov/ 41 | .tox/ 42 | .coverage 43 | .coverage.* 44 | .cache 45 | nosetests.xml 46 | coverage.xml 47 | *.cover 48 | .hypothesis/ 49 | 50 | # Translations 51 | *.mo 52 | *.pot 53 | 54 | # Django stuff: 55 | *.log 56 | local_settings.py 57 | 58 | # Flask stuff: 59 | instance/ 60 | .webassets-cache 61 | 62 | # Scrapy stuff: 63 | .scrapy 64 | 65 | # Sphinx documentation 66 | docs/_build/ 67 | 68 | # PyBuilder 69 | target/ 70 | 71 | # Jupyter Notebook 72 | .ipynb_checkpoints 73 | 74 | # pyenv 75 | .python-version 76 | 77 | # celery beat schedule file 78 | celerybeat-schedule 79 | 80 | # SageMath parsed files 81 | *.sage.py 82 | 83 | # dotenv 84 | .env 85 | 86 | # virtualenv 87 | .venv 88 | venv/ 89 | ENV/ 90 | 91 | # Spyder project settings 92 | .spyderproject 93 | .spyproject 94 | 95 | # Rope project settings 96 | .ropeproject 97 | 98 | # mkdocs documentation 99 | /site 100 | 101 | # mypy 102 | .mypy_cache/ 103 | 104 | -------------------------------------------------------------------------------- /CITATION.cff: -------------------------------------------------------------------------------- 1 | cff-version: 1.2.0 2 | message: "If you use this software, please cite it as below." 3 | authors: 4 | - family-names: "CHAOSS Community" 5 | given-names: "Value-WG" 6 | title: "CHAOSS Value Working Group" 7 | version: 2021-03 8 | date-released: 2021-08-26 9 | url: "https://github.com/chaoss/wg-value" 10 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # How to Contribute 2 | 3 | ## Where can I contribute? 4 | 5 | Anyone can contribute to CHAOSS on any of our communication channels. See . 6 | 7 | **Every issue in this repository is seeking contribution**. Click on issues to find ways to contribute. See this [list of all issues](https://github.com/chaoss/wg-value/issues). 8 | 9 | ### We need activists, enthusiasts, community input, and more. Anyone, with any skill set, can find a way to pitch in. 10 | 11 | ## Contributing to the Chaoss Community 12 | 13 | Thank you for your interest in contributing :tada:! 14 | 15 | This document outlines a process of contributing. 16 | 17 | ## How to submit changes 18 | 19 | Once you've identified one of the issues above that you feel you can contribute to, you're ready to make a change to the project repository! 20 | 21 | 1. **[Fork](https://help.github.com/articles/fork-a-repo/) this repository**. This makes your own version of this project you can edit and use. 22 | 23 | ``` 24 | 25 | Example: 26 | 27 | git clone git@github.com:/.git 28 | 29 | ``` 30 | 31 | 2. **[Create a Branch](https://github.com/Kunena/Kunena-Forum/wiki/Create-a-new-branch-with-git-and-manage-branches)**. If you already have the repo, please be sure that you have upstream merged into your master branch. And then create the branch. There is some [info](https://help.github.com/articles/syncing-a-fork) available at about syncing repositories. 32 | 33 | ``` 34 | 35 | Example: 36 | 37 | git checkout -b 38 | 39 | ``` 40 | 41 | 3. **[Make your changes](https://guides.github.com/activities/forking/#making-changes)**! You can do this in the GitHub interface on your own local machine. Once you're happy with your changes. If there are a bunch of commits and those are adding things, fixing a couple of typos, etc, please consider merging some of those into a smaller set of commits. This helps to review the whole process. More [info](https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/). 42 | 43 | Make your change and commit the change (NOTE: with `-s` you sign-off on each commit, which is your [Developer Certificate of Origin](https://developercertificate.org/)): 44 | 45 | ``` 46 | 47 | Example: 48 | 49 | git add 50 | git commit -s -m "" 51 | 52 | ``` 53 | 54 | *If you forget to add the sign-off you can also amend a previous commit with the sign-off by running `git commit --amend -s`. If you have pushed your changes to GitHub already you'll need to force push your branch after this with `git push -f`.* 55 | 56 | If this step sounds a bit difficult, the maintainers of the repository can help with this process when merging the PR. 57 | 58 | 3. **Submit a [pull request](https://help.github.com/articles/proposing-changes-to-a-project-with-pull-requests/)**. This opens a discussion around your changes and lets the project lead know you are proposing changes. 59 | 60 | ``` 61 | 62 | Example: 63 | 64 | git push origin 65 | 66 | ``` 67 | 68 | 4. **[Document Commit](https://medium.com/@steveamaza/how-to-write-a-proper-git-commit-message-e028865e5791)** Start the sentences with a capital letter, write a short sentence (usually no more than ~70 characters) and use that as you use the subject of an email. 69 | If you want to add more information, leave a blank line 70 | And then start the paragraph you want to write down (please remember the limitation of 70 characters). 71 | 72 | First time contributing to open source? Check out this Blog, [Best practices in a collaborative environment](https://channelcs.github.io/best-practices-in-a-collaborative-environment.html). 73 | 74 | 5. **References** Please include links to resources elsewhere that may be helpful to others. Include the references inside the files you are editing. This is not a hard requirement, but we encourage you to provide references if you know what source informed your contribution. 75 | 76 | ## How to report bugs 77 | 78 | Notice a mistake? Please file any bugs, requests, or questions in [our issue tracker](https://github.com/CHAOSS/wg-value/issues) 79 | 80 | ## Who is a CHAOSS repository maintainer? 81 | 82 | The README.md of the repository contains a list of who is maintainer. Each CHAOSS repository brings together different people and they document in the repository specific CONTRIBUTING.md how somone becomes a maintainer on their repository. 83 | 84 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019-2022 CHAOSS 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Value Working Group {Not Active} 2 | 3 | 4 | ## Participate 5 | 6 | The Value Working Group no longer meets as all related discussions now happen in the [Common Working Group](https://github.com/chaoss/wg-common) 7 | 8 | [Archived Agenda and Meeting Minutes](https://drive.google.com/drive/u/1/folders/1fV9Pn078dfCyTdBEl8h_18IAcnDjgBEt) 9 | 10 | ## Background 11 | 12 | The Value Working Group was focused on developing metrics that describe value of open source engagement for individuals and organizations. 13 | 14 | ## Focus Areas 15 | 16 | [Value WG Focus Areas](https://docs.google.com/spreadsheets/d/1tAGzUiZ9jdORKCnoDQJkOU8tQsZDCZVjcWqXYOSAFmE/edit#gid=1609274801) 17 | 18 | ## Released Metrics 19 | 20 | Check out our released Value metrics at: [https://chaoss.community/metrics/](https://chaoss.community/metrics/) 21 | 22 | ## License 23 | 24 | The documents in this repository are released under the MIT License. See [LICENSE](https://github.com/chaoss/wg-diversity-inclusion/blob/master/LICENSE) for details. 25 | 26 | ## Copyright 27 | 28 | Contributors to the CHAOSS project. 29 | -------------------------------------------------------------------------------- /focus-areas/README.md: -------------------------------------------------------------------------------- 1 | # Value Metrics Focus Areas 2 | 3 | We are compiling dimensions of value that can be used in the following areas of analysis: 4 | 5 | Focus Area | Goal 6 | --- | --- 7 | [Social Value](social-value/) | Identify if a project reduces poverty and injustice, strengthens democratic values, improves health and mental wellbeing, promotes international cooperation, fosters economic equality, or advances human achievement. 8 | [Organizational Value](organizational-value/) | Identify if a project is monetarily valuable from an organization's perspective. 9 | [Individual Value](individual-value/) | Identify if a project is valuable to me as an individual user or contributor. 10 | [Communal Value](communal-value/) | Identify if a project is valuable to its community of users (including downstream projects) or contributors. 11 | [Academic Value](academic-value/) | Identify the degree to which a project is valuable to researchers and academic institutions. 12 | -------------------------------------------------------------------------------- /focus-areas/academic-value/README.md: -------------------------------------------------------------------------------- 1 | # Academic Value 2 | 3 | **Goal:** Identify the degree to which a project is valuable to researchers and academic institutions. 4 | 5 | | Name | Question | 6 | | --- | --- | 7 | | [Academic Open Source Project Impact](academic-open-source-project-impact.md) | What is the impact of open source projects that an academician or a team of academicians creates as an important part of a university reappointment, tenure, and promotion process? | 8 | -------------------------------------------------------------------------------- /focus-areas/academic-value/academic-open-source-project-impact.md: -------------------------------------------------------------------------------- 1 | # Academic Open Source Project Impact 2 | 3 | **Question:** What is the impact of open source projects that an academician or a team of academicians creates as an important part of a university reappointment, tenure, and promotion process? 4 | 5 | ## Overview 6 | 7 | This metric measures the impact of new open source projects created by academicians as part of their academic role, with the purpose of supporting reappointment, tenure, and promotion (RPT) cases. It focuses on contributions released as open source by a researcher or team to showcase scholarly impact and engagement. Understanding this metric can help gauge the reach, influence, and longevity of these open source projects by examining aspects like community growth, citation count, and downstream dependencies. 8 | This metric highlights the importance of open source software as a scholarly output, potentially equal to traditional publications in academia. It also promotes greater recognition of open source projects, which can contribute to sustainable, community-driven research software and transparency in academia. 9 | 10 | In terms of DEI, this metric encourages inclusive access to research through open source, making scholarly contributions accessible to a broader, global audience regardless of institutional affiliations or financial constraints. 11 | 12 | ## Want to Know More? 13 | 14 |
15 | 16 | Click to read more about this metric. 17 | 18 | ### Data Collection Strategies 19 | 20 | Data points to consider: 21 | 22 | * Publication in open access journals like the Journal of Open Source Software 23 | * Number of downstream dependencies of the software 24 | * Standardized citations via the CiteAs API 25 | * Number of downloads or stars (e.g., GitHub) 26 | * Number of contributors from outside the research team 27 | * Frequency and recency of project updates 28 | * Number of publications that cite the project or related software 29 | * Lines of code contributed over time 30 | * Number of preprints or journal articles referencing the software 31 | 32 | ### Filters 33 | 34 | Potential filters include: 35 | 36 | * Project type (e.g., software, library, dataset) 37 | * Academic discipline or field 38 | * Platform (e.g., GitHub, arXiv, JOSS) 39 | * Contribution types (e.g., internal vs. external contributors) 40 | 41 |

42 | 43 | ## References 44 | 45 | * [GitHub Citation Guidelines for Software](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files) 46 | * [arXiv.org code](https://blog.arxiv.org/2020/10/08/new-arxivlabs-feature-provides-instant-access-to-code/) 47 | * [ResearchStory](https://www.researchstory.com/) 48 | * [ACM Artifact Review and Badging](https://www.acm.org/publications/policies/artifact-review-and-badging-current) 49 | * [Altmetric](https://www.altmetric.com/) 50 | * [Related Metric: Project Popularity](https://chaoss.community/metric-project-popularity/) 51 | * [CiteAs](https://citeas.org/about) 52 | * Zhao, R., & Wei, M. (2017). Impact evaluation of open source software: An Altmetrics perspective. Scientometrics, 110(2), 1017–1033. https://doi.org/10.1007/s11192-016-2204-y 53 | * Moral-Muñoz, J. A., Herrera-Viedma, E., Santisteban-Espejo, A., & Cobo, M. J. (2020). Software tools for conducting bibliometric analysis in science: An up-to-date review. El Profesional de La Información, 29(1). https://doi.org/10.3145/epi.2020.ene.03 54 | * Searles, A., Doran, C., Attia, J., Knight, D., Wiggers, J., Deeming, S., Mattes, J., Webb, B., Hannan, S., Ling, R., Edmunds, K., Reeves, P., & Nilsson, M. (2016). An approach to measuring and encouraging research translation and research impact. Health Research Policy and Systems, 14(1), 60. https://doi.org/10.1186/s12961-016-0131-2 55 | 56 | ## Contributors 57 | 58 | * Stephen Jacobs 59 | * Vinod Ahuja 60 | * Elizabeth Barron 61 | * Matt Germonprez 62 | * Kevin Lumbard 63 | * Georg Link 64 | * Peculiar C. Umeh 65 | * Sean P Goggins 66 | * Johan Linaker 67 | * Yigakpoa L. Ikpae 68 | 69 | ## Additional Information 70 | 71 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/academic-value/academic-open-source-project-impact.md)
72 | To reference this metric in software or publications please use this stable URL: 73 | 74 | 78 | -------------------------------------------------------------------------------- /focus-areas/communal-value/README.md: -------------------------------------------------------------------------------- 1 | # Communal Value 2 | 3 | **Goal:** Identify if a project is valuable to its community of users (including downstream projects) or contributors. 4 | 5 | Name | Question 6 | --- | --- 7 | [Project Velocity](project-velocity.md) | What is the development speed for an organization? 8 | [Project Popularity](project-popularity.md) | How popular is an open source project? 9 | [Project Recommendability](project-recommendability.md) | How likely is it that you would recommend a community or project to other people? 10 | -------------------------------------------------------------------------------- /focus-areas/communal-value/images/cncf Projects 7_1_2023 - 7_1_2024.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/cncf Projects 7_1_2023 - 7_1_2024.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/contributor-recommendability_recommendability-scale.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/contributor-recommendability_recommendability-scale.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/project-popularity_issues-and-reviews.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/project-popularity_issues-and-reviews.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/project-popularity_kubernetes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/project-popularity_kubernetes.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/project-recommendability_recommendability-scale.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/project-recommendability_recommendability-scale.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/project-velocity_visualization.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/project-velocity_visualization.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/recommendability-scale.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/recommendability-scale.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_circle2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_circle2.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_dashboard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_dashboard.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_data-points-table-source.md: -------------------------------------------------------------------------------- 1 | | Data Points | Description | 2 | |---|---| 3 | | Date of entry| Date data was imported to Social Listening tool| 4 | | Date of comment| Date comment was made on original platform| 5 | | Comment Text| Qualitative data brought in. Decide on how large you want these chunks ported. Some may port an entire email while others will be broken into one row per sentence. It should only have one “sentiment”| 6 | | Data channel| Originating data channel the comment came from | 7 | | Tags (created on codex document below) | Based on the unified codex of terms, decide what tags to track. There can be two kinds of tags. On the one hand, tags can be based on “themes” or recurring sentiment that people voice (e.g., gamer gate, flamewar, or thank you notes). On the other hand, tags based on “categories” can describe different aspects of a community that members comment on (e.g., events, release, or governance). | 8 | | Social Currency Metric| The social currency being awarded or demerited in the system. This will directly affect numbers.| 9 | | Weighted Score | Once you’ve decided what your “weight” will be, you can assign a system of -3 to +3 to provide a weighted view of human-tagged metrics (AI will not assign a weight for several reasons). This enables the “most impactful comment” filter.| 10 | -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_data-points-table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_data-points-table.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_expanded-comment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_expanded-comment.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_tool-example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_tool-example.png -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_unified-codex-terms-table-source.md: -------------------------------------------------------------------------------- 1 | | Category Term | Definition | When to use | When not to use | 2 | |---|---|---|---| 3 | | [Custom Tags - themes and categories] | | | | 4 | | [Community specific jargon]| | | | 5 | | Social Currency Dimensions:| | | | 6 | | TRANSPARENCY | Do people recognize and feel a connection to your community? |When they have the "words" to pinpoint why they feel you are authentic or personable.|This is not about good customer service, or doing well. That is utility. This is about whether they understand who you are as a business and show they are onboard with it.| 7 | | UTILITY | Is your community doing something useful or is it contributing value? |Provide parameters that exclude when the term is used so that people know when the category tag should not be implemented.|This is not about good customer service, or doing well. That is utility. This is about whether they understand who you are as a business and show they are onboard with it.| 8 | | CONSISTENCY | Do you have a history of being reliable and dependable? |When they suggest they have used your brand, or interacted with you several times |If they've only provided their comment to suggest you were useful once, use utility instead.| 9 | | MERIT | Does your community merit respect and attention for your accomplishments? |When the social currency garnered from customers seems it will continue for a while, and will impact other people's opinions.|When they suggest they will use you again in the future use trust instead as that is a personal trust in the brand. Merit is external.| 10 | | TRUST | Can people trust that your community will continue to provide value and grow in the future? |When they suggest they trust you well enough to continue conversations with you in the future|When there is not substantial enough evidence to suggest they will continue to work with and trust you as a loyal customer or community member.| 11 | | INTERNAL REPUTATION [9] | Do people believe these things strongly enough to warrant conversation or action? | | | 12 | | EXTERNAL REPUTATION [9] | What amount of your reputation in your community is transferable to strangers outside of your community (cold audiences)? | | | -------------------------------------------------------------------------------- /focus-areas/communal-value/images/social-listening_unified-codex-terms-table.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/communal-value/images/social-listening_unified-codex-terms-table.png -------------------------------------------------------------------------------- /focus-areas/communal-value/project-popularity.md: -------------------------------------------------------------------------------- 1 | # Project Popularity 2 | 3 | **Question:** How popular is an open source project? 4 | 5 | ## Overview 6 | Project popularity measures the level of visibility and engagement around an open source project by tracking various data points, such as social media mentions, forks, stars, contributors, and downstream dependencies. These indicators reflect community interest and adoption rates, providing insights into a project's reach and potential impact. 7 | 8 | Measuring project popularity helps inform project health and sustainability by identifying growth trends, which may indicate an increase in active use and contributions. A popular project is often seen as more valuable, both for individual contributors looking to work on impactful projects and for organizations considering where to invest resources. Popularity also helps reveal underserved projects with growth potential, which may present valuable opportunities for contributors and stakeholders. 9 | 10 | ## Want to Know More? 11 | 12 |
13 | Click to read more about this metric. 14 | 15 | ### Data Collection Strategies  16 | To measure project popularity, collect data points from: 17 | - Social media mentions 18 | - Forks 19 | - Change requests 20 | - New Issues 21 | - Stars, badges, likes 22 | - New contributors 23 | - Organizational Diversity 24 | - Job postings requesting skills in project 25 | - Conversations within and outside of project 26 | - Clones 27 | - Followers 28 | - Downstream dependencies 29 | - People attending events that focus on a project 30 | 31 | Data can also be gathered through platforms like GitHub, GitLab, social media, and job sites. 32 | 33 | ### Filters  34 | - **Time Period:** Measure changes in popularity over specific intervals. 35 | - **Platform:** Compare popularity metrics across GitHub, GitLab, or other hosting services. 36 | - **Project Type:** Filter based on project categories, such as libraries, tools, or frameworks. 37 | 38 | ### Visualizations 39 | - **Example Visualization 1:** Issues and reviews visualization from Cauldron (GrimoireLab). 40 | ![Issues and reviews](https://raw.githubusercontent.com/chaoss/wg-value/main/focus-areas/communal-value/images/project-popularity_issues-and-reviews.png) 41 | *Figure 1: Issues and reviews (Cauldron, 2023)* 42 | 43 | - **Example Visualization 2:** Kubernetes project popularity statistics from DevStats. 44 | ![Kubernetes_project_popularity](https://raw.githubusercontent.com/chaoss/wg-value/main/focus-areas/communal-value/images/project-popularity_kubernetes.png) 45 | *Figure 2: Kubernetes project popularity statistics (DevStats, 2023)* 46 | 47 |

48 | 49 | ## References 50 | - [Popular Open Source Projects](http://blog.honeypot.io/most-exciting-open-source-projects-2018/) 51 | - [Is It Maintained?](https://isitmaintained.com/) 52 | - [Open Source Project Trends](https://github.blog/2018-02-08-open-source-project-trends-for-2018/) 53 | - [Kubernetes Salary](https://www.payscale.com/research/US/Skill=Kubernetes/Salary) 54 | 55 | ## Contributors 56 | - Kevin Lumbard 57 | - Justin W. Flory 58 | - Matt Germonprez 59 | - Elizabeth Barron 60 | - Matt Cantu 61 | - Lauren Phipps 62 | - Joshua Simmons 63 | - Vinod Ahuja 64 | - Georg Link 65 | - Sean Goggins 66 | - Yigakpoa L. Ikpae 67 | 68 | ## Additional Information 69 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/communal-value/project-popularity.md). 70 | To reference this metric in software or publications please use this stable URL: https://chaoss.community/?p=3573 71 | 72 | 76 | -------------------------------------------------------------------------------- /focus-areas/communal-value/project-recommendability.md: -------------------------------------------------------------------------------- 1 | # Project Recommendability 2 | 3 | **Question:** How likely is it that you would recommend a community or project to other people? 4 | 5 | ## Overview 6 | 7 | Project recommendability metric seeks to understand two components of community engagement: satisfaction and advocacy. Evaluating the contributors’ satisfaction within a community or project, helps a maintainer/community determine reasons contributors may leave a community or project or discourage others from joining in. The findings from this evaluation would assist your community or project in setting up a process to improve itself through the cultivation of a community member retention strategy. The project recomendability metric also identifies areas of an open source project where contributors are dissatisfied or discontinuing their contribution. This metric could indicate underlying diversity, equity, and inclusion concerns that may be present in a project. The project recommendability metric can be used to develop net recommendabilty. 8 | 9 | ## Want to Know More? 10 | 11 |
12 | 13 | Click to read more about this metric. 14 | 15 | ### Data Collection Strategies 16 | 17 | Implicit Data: 18 | 19 | * Community newcomer inclusion factors, such as responsiveness to issues and change requests. 20 | * Community health factors like change request acceptance rate and release cadence. 21 | 22 | Explicit Data: 23 | 24 | * Surveys focused on obtaining contributor perspectives on different communities and projects. Sample questions include: 25 | * Could you specify where you primarily contribute to the community/project? 26 | * What aspects of this project do you find exceptionally motivating? 27 | * What aspects of this project do you want to see improved in the future? 28 | * (optional) Please share your GitHub ID or email address if you wish to help us build some context around your answers as associated with your issues or change requests. This data will not be available to project maintainers or others in the project. 29 | * How likely is it that you would recommend this community/project to other people? (Likert scale 0-x scores) 30 | * Not at all likely 31 | * Neutral 32 | * Extremely Likely 33 | * As a result of “Not at all likely”: Why do you not recommend the community to your friends or colleagues? 34 | * As a result of “Neutral”: Is there anything we can improve? 35 | * As a result of “Extremely likely”: Which part of work or areas do you recommend the community to your friends or colleagues? 36 | 37 | ### Filters 38 | 39 | By location of engagement. For example, by asking from: 40 | 41 | * Code committer 42 | * Issue reporters 43 | * Issue responders 44 | * Reviewers (e.g., in change requests) 45 | * Event participants 46 | * Release cycle managers 47 | * Community members (e.g., committers, maintainers, board members) 48 | * Demographic segments of respondents 49 | * Length of time in the community, or time since the first contribution 50 | * Activity type (e.g., new contributors, core, regular, casual, episodic) 51 | 52 | ### Visualizations 53 | 54 | The following provides a way to consider net recommendability. 55 | 56 | 1. Individuals who provide low, moderate, or high individual scores on this metric are categorized along a continuum from Detractor, to Passive, and, finally, to Promoter through segmentation using a statistical answer distribution determined to be appropriate for the project (e.g., Figure 1). 57 | 2. The percentage of promoters can be subtracted from the percentage of promoters to produce a measure of net recommendability. 58 | 59 | *** 60 | 61 | ![recommendability-scale](https://github.com/chaoss/wg-value/blob/main/focus-areas/communal-value/images/project-recommendability_recommendability-scale.png) 62 | 63 | Figure 1: An example of one mapping between a 10-point likert scale and categorization of contributors. 64 | 65 | %Detractors-%Promoters = **Net Recommendability** 66 | 67 | *** 68 | 69 | Net recommendability is inspired by the [Net Promoter Score](https://www.surveymonkey.com/mp/net-promoter-score-definition-formula/). 70 | 71 |

72 | 73 | ## References 74 | 75 | * [Net Promoter Score Definition and Formula](https://www.surveymonkey.com/mp/net-promoter-score-definition-formula/) 76 | * https://www.ipsos.com/en-us/net-promoter-debate 77 | 78 | ## Contributors 79 | 80 | * Yehui Wang 81 | * Matt Germonprez 82 | * Sean Goggins 83 | * Vinod Ahuja 84 | * Benjamin Mako Hill 85 | * Elizabeth Barron 86 | * Peculiar C. Umeh 87 | 88 | ## Additional Information 89 | 90 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/communal-value/project-recommendability.md) 91 | 92 | To reference this metric in software or publications please use this stable URL: 93 | 94 | 98 | -------------------------------------------------------------------------------- /focus-areas/communal-value/project-velocity.md: -------------------------------------------------------------------------------- 1 | # Project Velocity 2 | 3 | **Question:** What is the development speed for an organization? 4 | 5 | ## Overview 6 | 7 | Project velocity measures the number of issues, the number of pull requests, volume of commits, and number of contributors as an indicator of innovation. It gives an Open Source Program Office (OSPO) manager a way to compare the project velocity across a portfolio of projects. 8 | Open Source Program Office (OSPO) manager can use the Project Velocity metric to: report project velocity of open source projects vs in-house projects, compare project velocity across a portfolio of projects, identify promising areas in which to get involved and highlight areas likely to be the successful platforms over the next several years 9 | 10 | ## Want to Know More? 11 | 12 |
13 | 14 | Click to read more about this metric. 15 | 16 | ### Data Collection Strategies 17 | 18 | * [issues closed](https://github.com/chaoss/wg-evolution/blob/main/focus-areas/issue-resolution/issues-closed.md) 19 | * [number of reviews](https://github.com/chaoss/wg-evolution/blob/main/focus-areas/code-development-process-quality/change-request-reviews.md) 20 | * [# of code changes](https://github.com/chaoss/wg-evolution/blob/main/focus-areas/code-development-activity/code-changes-commits.md) 21 | * [# of committers](https://github.com/chaoss/wg-risk/blob/main/focus-areas/business-risk/committers.md) 22 | 23 | ### Filters 24 | 25 | * Internal vs external contributors 26 | * Project sources (e.g., internal repositories, open-source repositories, and competitor open-source repositories) 27 | * Time 28 | 29 | ### Visualizations 30 | 31 | * X-Axis: Logarithmic scale for Code Changes 32 | * Y-Axis: Logarithmic scale of Sum of Number of Issues and Number of Reviews 33 | * Dot-size: Committers 34 | * Dots are projects 35 | [CNCF](https://github.com/cncf/velocity) 36 | ![cncf](https://raw.githubusercontent.com/chaoss/wg-value/main/focus-areas/communal-value/images/project-velocity_visualization.png) 37 | 38 |

39 | 40 | ## References 41 | 42 | * [Can Open Source Innovation work in the Enterprise?][l1] 43 | * [Open Innovation for a High Performance Culture][l2] 44 | * [CNCF][13] 45 | 46 | [l1]: https://www.threefivetwo.com/blog/can-open-source-innovation-work-in-the-enterprise 47 | 48 | [l2]: https://www.nearform.com/blog/want-a-high-performing-culture-make-way-for-open-innovation 49 | 50 | [13]: https://github.com/cncf/velocity 51 | 52 | ## Contributors 53 | 54 | * Elizabeth Barron 55 | * Georg Link 56 | * Matt Germonprez 57 | * Peculiar C Umeh 58 | 59 | ## Additional Information 60 | 61 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/communal-value/project-velocity.md) 62 | 63 | To reference this metric in software or publications please use this stable URL: 64 | 65 | 69 | -------------------------------------------------------------------------------- /focus-areas/individual-value/README.md: -------------------------------------------------------------------------------- 1 | # Individual Value 2 | 3 | **Goal:** Identify if a project is valuable to me as an individual user or contributor. 4 | 5 | Name | Question 6 | --- | --- 7 | [Organizational Project Skill Demand](organizational-project-skill-demand.md) | How many organizations are using this project and could hire me if I become proficient? 8 | [Job Opportunities](job-opportunities.md) | How many job postings request skills with technologies from a project? 9 | -------------------------------------------------------------------------------- /focus-areas/individual-value/images/organizational-project-skill-demand_google-trends.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/individual-value/images/organizational-project-skill-demand_google-trends.png -------------------------------------------------------------------------------- /focus-areas/individual-value/images/organizational-project-skill-demand_paper.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/individual-value/images/organizational-project-skill-demand_paper.png -------------------------------------------------------------------------------- /focus-areas/individual-value/images/organizational-project-skill-demand_stack-overflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/individual-value/images/organizational-project-skill-demand_stack-overflow.png -------------------------------------------------------------------------------- /focus-areas/individual-value/images/organizational-project-skill-demand_tech-radar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/individual-value/images/organizational-project-skill-demand_tech-radar.png -------------------------------------------------------------------------------- /focus-areas/individual-value/images/organizational-project-skill-demand_tech-react.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/individual-value/images/organizational-project-skill-demand_tech-react.png -------------------------------------------------------------------------------- /focus-areas/individual-value/job-opportunities.md: -------------------------------------------------------------------------------- 1 | # Job Opportunities 2 | 3 | **Question:** How many job postings request skills with technologies from a project? 4 | 5 | ## Overview 6 | 7 | This metric measures the demand for skills related to an open source project, as seen through job postings requesting those skills. By tracking mentions of specific projects or technologies in job listings, contributors can gauge how skills learned in an open source project impact job prospects and the broader job market demand for that expertise. 8 | This metric provides insight into how companies value skills associated with a project, which can inform contributors’ career development. It also highlights trends in the tech job market, helping individuals and organizations make informed decisions about skill development and project engagement. 9 | 10 | ## Want to Know More? 11 | 12 |
13 | 14 | Click to read more about this metric. 15 | 16 | ### Data Collection Strategies 17 | 18 | * **Job Search Platforms:**\ 19 | Search for the open source project’s name on platforms like LinkedIn, Indeed, or Dice. Record the number of job postings returned, indicating demand for skills related to the project. 20 | * **API Use:**\ 21 | Periodically collect data using APIs from job platforms to monitor job posting trends over time. Example of some platforms include: 22 | * [LinkedIn Job Search API](https://developer.linkedin.com/docs/v1/jobs/job-search-api#) 23 | * [Indeed Job Search API](https://opensource.indeedeng.io/api-documentation/docs/job-search/) 24 | * [Monster Job Search API](https://partner.monster.com/job-search) 25 | * [ZipRecruiter API (Requires Partnership)](https://www.ziprecruiter.com/zipsearch) 26 | 27 | ### Filters 28 | 29 | * **Posting Age:** Older postings may no longer be active, so filtering by posting date ensures more accurate, relevant data. 30 | 31 |

32 | 33 | ## References 34 | 35 | * [LinkedIn Job Search API](https://developer.linkedin.com/docs/v1/jobs/job-search-api#) 36 | * [Indeed Job Search API](https://opensource.indeedeng.io/api-documentation/docs/job-search/) 37 | * [Monster Job Search API](https://partner.monster.com/job-search) 38 | * [ZipRecruiter API (Requires Partnership)](https://www.ziprecruiter.com/zipsearch) 39 | 40 | ## Contributors 41 | 42 | * Matt Germonprez 43 | * Sean Goggins 44 | * Elizabeth Barron 45 | * Georg Link 46 | * Yigakpoa L. Samuel 47 | 48 | ## Additional Information 49 | 50 | To edit this metric, please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/job-opportunities.md).\ 51 | To reference this metric in software or publications, please use this stable URL: 52 | 53 | 57 | -------------------------------------------------------------------------------- /focus-areas/individual-value/organizational-project-skill-demand.md: -------------------------------------------------------------------------------- 1 | # Organizational Project Skill Demand 2 | 3 | **Question:** How many organizations are using this project and could hire me if I become proficient? 4 | 5 | ## Overview 6 | 7 | Organizational Project Skill Demand metric is aimed at determining downstream demand of skills related to an open source project. This metric looks at organizations that deploy a project as part of an IT infrastructure, other open source projects with declared dependencies, and references to the project through social media, conference mentions, blog posts, and similar activities. Developers, could invest their skills and time in a project that has a likelihood of getting them a decent paying job in the future. They can use the Downstream Organizational Impact of a Project Software metric to discover which projects are used by organizations, and they may, therefore, be able to pursue job opportunities with, possibly requiring IT support services. 8 | 9 | ## Want to Know More? 10 | 11 |
12 | 13 | Click to read more about this metric. 14 | 15 | ### Data Collection Strategies 16 | 17 | * Google search trends for a project 18 | * Other projects that are dependent on a project 19 | * Blog or tweet about a project 20 | * Number of organizations that mention a project in open hiring requests 21 | * Number of organizations that are represented at meetups about this project 22 | 23 | ### Visualizations 24 | 25 | The following visualization demonstrates the number of downstream projects 26 | dependendent on the project in question. While this visualization does not 27 | capture the entirety of the Downstream Organizational Impact of a Project 28 | Software metric, it provides a visual for a portion. 29 | 30 | ![paper image](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/images/organizational-project-skill-demand_paper.png) 31 | 32 | Other visualizations could include Google search trends (React vs. Angular vs. Vue.js) 33 | 34 | ![Google Trends](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/images/organizational-project-skill-demand_google-trends.png) 35 | 36 | ThoughtWorks publishes a series called 'Tech Radar' that shows the popularity of technologies. 37 | 38 | ![TechRadar](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/images/organizational-project-skill-demand_tech-radar.png) 39 | 40 | Tech Radar allows you to drill down on projects to see how the assessment has changed over time. 41 | 42 | ![Assessment](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/images/organizational-project-skill-demand_tech-react.png) 43 | 44 | StackOverview publishes an annual developer's survey 45 | 46 | ![StackOverflow](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/images/organizational-project-skill-demand_stack-overflow.png) 47 | 48 |

49 | 50 | ## References 51 | 52 | * [Open Source Sponsors][l1] 53 | * [Fiscal Sponsors and Open Source][l2] 54 | * [Large Corporate OpenSource Sponsors][l3] 55 | * [Google Trends API][l4] 56 | * [Measuring Open Source Software Impact][l5] 57 | * [ThoughtWorks Tech Radar][l6] 58 | * [Stack Overflow Developer's Survey][l7] 59 | 60 | [l1]: https://opensource.org/sponsors 61 | 62 | [l2]: https://opensource.com/article/19/1/fiscal-sponsors-open-source 63 | 64 | [l3]: https://www.networkworld.com/article/2867020/big-names-like-google-dominate-open-source-funding.html 65 | 66 | [l4]: https://www.npmjs.com/package/google-trends-api 67 | 68 | [l5]: https://aisel.aisnet.org/cgi/viewcontent.cgi?article=1496&context=amcis2018 69 | 70 | [l6]: https://www.thoughtworks.com/radar 71 | 72 | [l7]: https://insights.stackoverflow.com/survey/2019#technology 73 | 74 | ## Contributors 75 | 76 | * Matt Germonprez 77 | * Kevin Lumbard 78 | * Georg Link 79 | * Peculiar C Umeh 80 | 81 | ## Additional Information 82 | 83 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/individual-value/organizational-project-skill-demand.md) 84 | 85 | To reference this metric in software or publications please use this stable URL: 86 | 87 | 91 | -------------------------------------------------------------------------------- /focus-areas/organizational-value/README.md: -------------------------------------------------------------------------------- 1 | # Organizational Value 2 | 3 | **Goal:** Identify if a project is monetarily valuable from an organization's perspective. 4 | 5 | Name | Question 6 | --- | --- 7 | [Labor Investment](labor-investment.md) | What was the cost of an organization for its employees to create the counted contributions (e.g., commits, issues, and pull requests)? 8 | [Organizational Influence](organizational-influence.md) | How much influence does an organization have on an open source community? 9 | -------------------------------------------------------------------------------- /focus-areas/organizational-value/images/labor-investment_csv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chaoss/wg-value/902ba8412e9346623fd4015d273561193ef460cf/focus-areas/organizational-value/images/labor-investment_csv.png -------------------------------------------------------------------------------- /focus-areas/organizational-value/labor-investment.md: -------------------------------------------------------------------------------- 1 | # Labor Investment 2 | 3 | **Question:** What was the cost of an organization for its employees to create the counted contributions (e.g., commits, issues, and pull requests)? 4 | 5 | ## Overview 6 | Labor Investment tracks the monetary commitment organizations make in supporting open source projects through employee contributions. This metric assesses the labor costs incurred by organizations, providing transparency in the financial commitment tied to open source engagement. 7 | 8 | Measuring labor investment informs organizational health and sustainability by highlighting the level of resources committed to open source projects. For Open Source Program Office (OSPO) managers, this metric offers insights into prioritizing resources, justifying budgets, and understanding the return on investment (ROI) across a portfolio of projects. For example, the Labor Investment metric can be used to prioritize investment or determine return on investment such as: 9 | 10 | * Labor Investment as a means of evaluating OSPO priorities and justifying budgets 11 | * Labor Investment as a way to explain product/program management priority 12 | * Labor Investment as an argument for the value of continued investing in OSPOs 13 | * Labor Investment to report and compare labor costs of contributed vs in-house work 14 | * Labor Investment to compare project effectiveness across a portfolio of projects 15 | 16 | ## Want to Know More? 17 | 18 |
19 | Click to read more about this metric. 20 | 21 | ### Data Collection Strategies 22 | - **Quantitative Data:** 23 | - Count contributions by type (e.g., commits, issues, pull requests). 24 | - Break down contributions by contributor types (internal vs. external). 25 | - Track the average hours spent per contribution type and multiply by hourly labor rates to calculate total labor costs. 26 | 27 | - **Calculation:** 28 | Labor Investment = For each contribution type, sum (Number of contributions * Average labor hours per contribution * Average hourly rate). 29 | 30 | ### Filters 31 | - **Contributor Types:** Filter by internal vs. external contributors to understand organizational versus community labor. 32 | - **Contribution Types:** Focus on specific contribution types like commits, issues, or pull requests. 33 | - **Project Source:** Differentiate between internal, open-source, or competitor open-source repositories. 34 | 35 | ### Visualizations 36 | - **Example Visualization:** CSV export with parameterized metrics. 37 | ![CSV Export](https://github.com/chaoss/wg-value/blob/main/focus-areas/organizational-value/images/labor-investment_csv.png) 38 | *Figure 1: Labor investment visualization using CSV export (CHAOSS, 2023)* 39 | 40 |

41 | 42 | ## References 43 | - [Starting an Open Source Program Office](https://www.slideshare.net/caniszczyk/starting-an-open-source-program-office-ospo) 44 | - [Creating an Open Source Program Office](https://events19.linuxfoundation.org/wp-content/uploads/2018/07/OSLS_2019-untold-story-of-OSPO.pdf) 45 | - [Open Source in the Enterprise](https://d1.awsstatic.com/Open%20Source/enterprise-oss-book.pdf) 46 | 47 | ## Contributors 48 | - Matt Germonprez 49 | - Sean Goggins 50 | - Dawn Foster 51 | - Vinod Ahuja 52 | - Elizabeth Barron 53 | - Georg Link 54 | - Yigakpoa L. Samuel 55 | 56 | ## Additional Information 57 | To edit this metric, please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/organizational-value/labor-investment.md). 58 | To reference this metric in software or publications, please use this stable URL: [https://chaoss.community/?p=3559](https://chaoss.community/?p=3559) 59 | 60 | 64 | -------------------------------------------------------------------------------- /focus-areas/organizational-value/organizational-influence.md: -------------------------------------------------------------------------------- 1 | # Organizational Influence 2 | 3 | **Question:** How much influence does an organization have on an open source community? 4 | 5 | ## Overview 6 | 7 | Organizational Influence measures the influence that an organization has on an open source community. An organization may influence the direction and development trajectory of a project, signaling some level of control within a community. This metric can also help open source maintainers track and measure organizational influence to add legitimacy to their projects and monitor the level of control by [individual organizations](https://chaoss.community/metric-organizational-diversity/). 8 | An organization's influence may also serve as a signal of how easy or difficult it may be for new [contributors](https://chaoss.community/metric-contributors/) to contribute to an open-source project. It can also help an open-source advocate in an organization justify continued funding and support for engagement. 9 | 10 | ## Want to Know More? 11 | 12 |
13 | 14 | Click to read more about this metric. 15 | 16 | ### Filter 17 | 18 | Examples to consider when measuring organizational influence include: 19 | 20 | * How many organizational members are contributing to a project - [contributors](https://chaoss.community/metric-contributors/). It can be understood as a ratio of (number of contributors from each organization with more than one contributor)/(number of contributors) 21 | * Level and [types of contributions](https://chaoss.community/metric-types-of-contributions/) by organizational members 22 | * Organizations that are contributing change requests at a high rate in proportion to the community’s level of activity. For example, one standard deviation or less of other contributing organizations. Related to organizational diversity 23 | * Organizational members on the technical steering committee 24 | * Organizational members on governing board 25 | * Organizational members in project maintainer roles 26 | * Organizations sponsoring an open source project as a proportion of the total 27 | 28 |

29 | 30 | ## References 31 | 32 | * [Augur](https://augurlabs.io/) 33 | * [GrimoireLab](https://chaoss.github.io/grimoirelab/) 34 | 35 | ## Contributors 36 | 37 | * Sean Goggins 38 | * Matt Germonprez 39 | * Vinod Ahuja 40 | * Kevin Lumbard 41 | * Lawrence Hecht 42 | * Matt Snell 43 | * Dhruv Sachdev 44 | * Elizabeth Barron 45 | * Matt Broberg 46 | * Stephen Jacobs 47 | * Peculiar C. Umeh 48 | 49 | ## Additional Information 50 | 51 | To edit this metric please [submit a Change Request here](https://github.com/chaoss/wg-value/blob/main/focus-areas/organizational-value/organizational-influence.md) 52 | 53 | To reference this metric in software or publications please use this stable URL: 54 | 55 | 59 | -------------------------------------------------------------------------------- /focus-areas/social-value/README.md: -------------------------------------------------------------------------------- 1 | # Social Value 2 | 3 | **Goal:** Identify if a project reduces poverty and injustice, strengthens democratic values, improves health and mental wellbeing, promotes international cooperation, fosters economic equality, or advances human achievement. 4 | 5 | Name | Question 6 | --- | --- 7 | TBD | TBD 8 | -------------------------------------------------------------------------------- /metrics/CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # CHAOSS Value Metrics CHANGELOG 2 | 3 | ## 2020 June 4 | 5 | Building off the relaunch to include value as aligned with individuals, organizations, communities, and society. 6 | 7 | ## 2020 March 8 | 9 | Relaunching the Value group with the goal of centering on funding community initiatives. Specifically: 10 | 11 | - Aligning to **business value**. Metrics must center on an ability to receive or sustain funding. All other metrics will be archived. 12 | - Organizing files for ease of access, including adding a RESOURCES.md file for those who wish to share external recommendations outside of metrics. 13 | - Structuring the repository and guidelines (like code of conduct linking) based on other working groups. 14 | 15 | ## 2019 July 16 | 17 | This is our first release of CHAOSS value-metrics. In this context "value" refers to economic value, which typically is represented in a numeric/monetary form. 18 | 19 | ### Stakeholders 20 | 21 | Our work centers on corporate projects sponsored by "Open Source Program 22 | Offices" (OSPO). Within this segment, we focus on two types of stakeholders: 23 | 24 | * OSPO Managers * 25 | 26 | Profile: 27 | - full-time organization employee 28 | - coder / product manager / 29 | 30 | Activities: 31 | - outreach to outside developers 32 | - outreach to internal developers 33 | - release coordination 34 | - coordination and reporting with internal management 35 | 36 | Key value questions: How can I justify my OSPO budget to corporate managers? 37 | 38 | We believe that OSPO will be interested in metrics that supports two claims: 39 | - OSPO can reduce labor costs (labor costs) 40 | - OSPO can reduce the time that it takes to close issues (issue velocity) 41 | 42 | * Workers * 43 | 44 | Activities: 45 | - find an interesting project 46 | - learn the community and the tech 47 | - write code and submit a PR 48 | - decide wether to get more invested, or move on 49 | - leverage skills and reputation for economic opportunity 50 | 51 | Key value question: How can I make a living wage in open source? 52 | 53 | We believe that workers will be interested in metrics that show: 54 | - which projects are backed by corporate money? 55 | - which projects are growing rapidly? 56 | - which projects have an underserved developer community? 57 | - what types of salaries are being paid for specific technical specialties? 58 | 59 | ### Parametrized Metrics 60 | 61 | Many economic values are context-dependant. 62 | 63 | For example, we may wish to measure the $USD value of a closed issue. The 64 | formula to calculate the $USD value would be something like "number of issues * 65 | average labor hours to close an issue * fully-loaded average hourly labor 66 | rate". 67 | 68 | In this context, the number of closed issues is an objective measure. But the 69 | time-estimate to close issues varies from organization to organization, as does 70 | the hourly labor rate. 71 | 72 | To accommodate this context-dependency, we will introduce the idea of 73 | "parameterized value metrics". 74 | 75 | Terms: 76 | - base metric - an observed value like "number of closed issues" 77 | - parameters - like "hourly labor rate" or "hours labor to close issue" 78 | - computed metric - like "cost per closed issue" 79 | 80 | The initial implementation of "parameterized value metrics" is brutally simple: 81 | export CSV with base metrics, load CSV into a spreadsheet and apply formulas 82 | with your own context-specific parameters. 83 | 84 | -------------------------------------------------------------------------------- /metrics/README.md: -------------------------------------------------------------------------------- 1 | ## Metrics for Value Working Group 2 | 3 | Groups within the CHAOSS project each have their own objectives in mind. In the Value working group, our aim is focus on measurements that result in better understand the impact that a project can have on individuals, organizations, communities, and society. 4 | 5 | ## Intended audience 6 | 7 | All metrics are intended to be used by individuals looking to continue to understand how community work has an impact across a wide range of stakeholders. Stakeholders include people seeking funding for open source work, organizations seeking to understand the impact of the projects they support, communities hoping to understand how they support other community work, and communities hoping to understand how they are making the world a better place. 8 | 9 | ## Metric guidelines 10 | 11 | "Community work" is left open to self-selection. Some scenarios those working in Community could consider include: 12 | 13 | - Can I secure funding to start an event without focusing on lead generation? 14 | - Can I secure funding to sponsor or be sponsored as an event organizer? 15 | - How do I quantify the value of me attending (one or more) conferences? 16 | - How do I justify to my executive sponsor to fund my community-oriented team? 17 | - How did I receive funding from VCs for a community-oriented startup? 18 | - What is impact the projects that our organization supports? 19 | - How is our open source project helping improve the Internet as a social good? 20 | 21 | ### Advice for useful metrics 22 | 23 | The intention is to show that metrics positioned as relative different values can be infinitely more effective than arguing “it’s the right thing to do for our Community.” With that in mind: 24 | 25 | - Is the metric interesting to my exective sponsor or boss's boss? If not, it's more likely aligned to [another working group](https://github.com/chaoss/metrics#goals-of-chaoss-metrics). 26 | - Is the metric effective on its own (like a vanity metric) or as a comparison over time or both? 27 | - Is the metric most effective comparing to itself or to competitors? 28 | - Is the metric effective in a certain portion of an organizational chart in a corporation (Marketing, Product, Engineering, Human Resources)? 29 | - Is the metric helping reveal why people may want to engage with a project from career perspective? 30 | - Is the metric helping determine how an open source project is improving the lives of people? 31 | 32 | --------------------------------------------------------------------------------