Skip to content

Commit a9f0b41

Browse files
committed
Copyedit of template and contributing docs
Signed-off-by: Stephen Augustus <[email protected]>
1 parent a345e20 commit a9f0b41

File tree

3 files changed

+84
-65
lines changed

3 files changed

+84
-65
lines changed

.github/pull_request_template.md

Lines changed: 30 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,71 +1,72 @@
1-
## Description
1+
# Description
22

3-
<!-- Briefly describe what this PR adds or changes -->
3+
<!-- Briefly describe what this pull request adds or changes. -->
44

5-
## Type of Change
5+
## Type of change
66

7-
<!-- Check all that apply -->
7+
<!-- Check all that apply. -->
8+
- [ ] Add a new tool/project
9+
- [ ] Add a new category
10+
- [ ] Documentation update e.g., fixing a broken link, updating an existing entry
11+
- [ ] Other (please describe above)
812

9-
- [ ] Adding a new tool/project
10-
- [ ] Adding a new category
11-
- [ ] Updating an existing entry
12-
- [ ] Fixing a broken link
13-
- [ ] Documentation update
14-
- [ ] Other (please describe):
15-
16-
## For New Tools/Projects
17-
18-
<!-- If you're adding a new tool or project, please complete this section -->
13+
<!-- If you're adding a new tool or project, please complete this section. -->
14+
## New tool/project
1915

2016
### Why is this tool/project needed?
2117

22-
<!-- Explain the problem it solves or the gap it fills. How does it help organizations manage open source projects or OSPOs? -->
18+
<!--
19+
Explain the problem it solves or the gap it fills.
20+
How does it help organizations manage open source projects or OSPOs?
21+
-->
2322

2423
### Category Selection
2524

2625
**Selected Category:** <!-- e.g., Code Reviews, GitHub Management, etc. -->
2726

2827
**Why this category?**
2928

30-
<!-- Explain why you chose this specific category. If the tool fits multiple categories, explain why this is the primary use case. -->
29+
<!--
30+
Explain why you chose this specific category.
31+
If the tool fits multiple categories, explain why this is the primary use case.
32+
-->
3133

3234
### Tool Uniqueness
3335

34-
<!-- If similar tools already exist in the list, explain what makes this tool unique or complementary -->
36+
<!-- If similar tools already exist in the list, explain what makes this tool unique or complementary. -->
3537

38+
<!-- If you're proposing a new category, please complete this section. -->
3639
## For New Categories
3740

38-
<!-- If you're proposing a new category, please complete this section -->
39-
4041
### Why is a new category needed?
4142

42-
<!-- Explain what gap the new category would fill -->
43+
<!-- Explain what gap the new category would fill. -->
4344

4445
### Example Tools
4546

46-
<!-- Provide at least 2-3 examples of tools that would fit in this category -->
47+
<!--
48+
Provide at least 2-3 examples of tools that would fit in this category.
4749
4850
1.
49-
2.
50-
3.
51+
1.
52+
-->
5153

5254
### Category Positioning
5355

54-
<!-- Suggest where the new category should be positioned in the list -->
56+
<!-- Suggest where the new category should be positioned in the list. -->
5557

5658
### Why existing categories are not suitable
5759

58-
<!-- Explain why existing categories don't work for these tools -->
60+
<!-- Explain why existing categories don't work for these tools. -->
5961

6062
## Checklist
6163

62-
<!-- Check all that apply -->
63-
64-
- [ ] I have read the CONTRIBUTING.md guidelines
64+
<!-- Check all that apply. -->
65+
- [ ] I have read the [CONTRIBUTING.md](https://github.com/todogroup/awesome-ospo/blob/main/CONTRIBUTING.md) guidelines
6566
- [ ] I have searched for duplicate suggestions
6667
- [ ] The pull request has a descriptive title
6768
- [ ] I have added the entry to the bottom of the relevant category (if adding a new tool)
6869
- [ ] I have checked my spelling and grammar
6970
- [ ] I have removed trailing whitespace
7071
- [ ] I have verified that all links work correctly
71-
- [ ] I have provided context on why this change is needed (above)
72+
- [ ] I have provided context on why this change is needed above

CONTRIBUTING.md

Lines changed: 28 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -2,60 +2,52 @@
22

33
We welcome improvements and suggestions! Please consider these guidelines:
44

5-
## General Guidelines
5+
## General guidelines
66

77
- Make an individual pull request for each suggestion using the provided template
8-
- The pull request and commit should have a useful title.
9-
- Search previous suggestions before making a new one, as yours may be a duplicate.
10-
- New links should be added to the bottom of their relevant category.
11-
- New categories or improvements to the existing categorization are welcome.
12-
- Make sure your text editor is set to remove trailing whitespace.
13-
- Check your spelling and grammar.
8+
- The pull request and commit should have a useful title
9+
- Search previous suggestions before making a new one, as yours may be a duplicate
10+
- New links should be added to the bottom of their relevant category
11+
- New categories or improvements to the existing categorization are welcome
12+
- Make sure your text editor is set to remove trailing whitespace
13+
- Check your spelling and grammar
1414

15-
## Adding a New Tool or Project
15+
## Add a new tool or project
1616

1717
When submitting a new tool or project, please provide context to help reviewers understand your suggestion:
1818

1919
### Why is this tool/project needed?
20+
2021
- Explain the problem it solves or the gap it fills in the current list
2122
- Describe how it helps organizations manage open source projects or OSPOs
2223
- If similar tools exist in the list, explain what makes this tool unique or complementary
2324

24-
### Choosing the Right Category
25-
26-
Our list includes the following categories:
27-
- **Code Reviews** - Tools for managing and automating code review processes
28-
- **Continuous Integration / Continuous Delivery** - CI/CD platforms and tools
29-
- **Contributor License Agreements / Developer Certificate of Origins** - CLA and DCO management tools
30-
- **GitHub Metrics and Dashboards** - Tools for tracking and visualizing GitHub activity
31-
- **GitHub Management** - Tools for managing GitHub organizations and repositories
32-
- **Governance** - Tools for project governance and community management
33-
- **Project Quality** - Tools for assessing and improving project quality
34-
- **Supply Chain Trust** - Tools for managing software supply chain security
35-
- **Licensing** - Tools for managing and tracking open source licenses
36-
- **Localization and Internationalization** - Tools for managing translations and i18n
37-
- **Websites and Documentation** - Tools for creating and managing project websites and documentation
38-
- **Security** - Security scanning and vulnerability management tools
39-
- **In-Kind Donations** - Resources for in-kind donations and support programs
25+
### Choose the right category
4026

4127
When adding a new tool:
42-
1. Review the category descriptions above
43-
2. Select the category that best fits the tool's primary purpose
44-
3. If the tool fits multiple categories, choose the one that represents its main use case
45-
4. In your pull request, explain why you chose that specific category
4628

47-
### Proposing a New Category
29+
1. Review the category descriptions in our [README](https://github.com/todogroup/awesome-ospo/blob/main/README.md)
30+
1. Select the category that best fits the tool's primary purpose
31+
1. If the tool fits multiple categories, choose the one that represents its main use case
32+
1. In your pull request, explain why you chose that specific category
33+
34+
### Propose a new category
4835

4936
If you believe a new category is needed:
37+
5038
1. Explain what gap the new category would fill
51-
2. Provide at least 2-3 examples of tools that would fit in this category
52-
3. Suggest where the new category should be positioned in the list
53-
4. Explain why existing categories are not suitable for these tools
39+
1. Provide at least 2-3 examples of tools that would fit in this category
40+
1. Suggest where the new category should be positioned in the list
41+
1. Explain why existing categories are not suitable for these tools
42+
43+
## Pull request template
5444

55-
## Pull Request Template
45+
When creating a pull request, please fill out the template completely.
46+
This helps maintainers review your contribution more efficiently and makes the review process smoother for everyone.
5647

57-
When creating a pull request, please fill out the PR template completely. This helps maintainers review your contribution more efficiently and makes the review process smoother for everyone.
48+
## Maintainer review
5849

59-
## Wait for a maintainer to review
50+
One of our maintainers will get back to you once they've had a chance to review the pull request.
51+
You can highlight the pull request in [`#project-todo-gh`](https://thetodogroup.slack.com/archives/C08AR66MQQ5) channel for a faster response.
6052

61-
A maintainer will get back to you in the following days. You can also raise the issue in <a href="https://join.slack.com/t/thetodogroup/shared_invite/zt-2w71kclgx-JOUB4LTXIuVEKehkJk7V0w">TODO slack</a> `#project-todo-gh`channel for quick response
53+
(If you are not already a member of our Slack workspace, you can join via [this invite link](https://thetodogroup.slack.com/join/shared_invite/zt-2w71kclgx-JOUB4LTXIuVEKehkJk7V0w#/shared-invite/email).)

README.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ members or found helpful for managing open source projects and offices.
2020

2121
## Code Reviews
2222

23+
Tools for managing and automating code review processes.
24+
2325
- [PullApprove](https://www.pullapprove.com) - Allows for fancier rules on how pull requests are approved.
2426
- [sentinel](https://github.com/habitat-sh/sentinel) - PR Test, review, and merge workflow bot
2527
- [pull-review](https://github.com/imsky/pull-review) - assign pull request reviewers intelligently, inspired by mention-bot
@@ -28,6 +30,8 @@ members or found helpful for managing open source projects and offices.
2830

2931
## Continuous Integration / Continuous Delivery
3032

33+
CI/CD platforms and tools.
34+
3135
- [GitHub Actions](https://github.com/features/actions) - Automate your workflow from idea to production.
3236
- [Jenkins](https://www.jenkins.io/) - open source automation server that provides hundreds of plugins to support building, deploying and automating any project.
3337
- [Jenkins X](https://jenkins-x.io/) - open source CI/CD solution for modern cloud applications on Kubernetes.
@@ -39,13 +43,17 @@ members or found helpful for managing open source projects and offices.
3943

4044
## Contributor License Agreements / Developer Certificate of Origins
4145

46+
CLA and DCO management tools.
47+
4248
- [CLA Assistant](https://github.com/cla-assistant/cla-assistant) - Streamline your workflow and let CLA assistant handle the legal side of contributions to a repository for you. CLA assistant enables contributors to sign CLAs from within a pull request.
4349
- [Dr CLA](https://github.com/salesforce/dr-cla) - GitHub bot for dealing with Contributor License Agreements
4450
- [DCO Bot](https://github.com/apps/dco) - GitHub App that enforces the Developer Certificate of Origin (DCO) on Pull Requests
4551
- [EasyCLA](https://github.com/linuxfoundation/easycla) - a Contributor License Agreement (CLA) service used in Linux Foundation's LFX platform which lets project contributors read, sign, and submit contributor license agreements easily
4652

4753
## GitHub Metrics and Dashboards
4854

55+
Tools for tracking and visualizing GitHub activity.
56+
4957
- [osstracker](https://github.com/Netflix/osstracker) - OSS Tracker is an application that collects information about a Github organization and aggregates the data across all projects within that organization into a single user interface to be used by various roles within the owning organization.
5058
- [devstats](https://github.com/cncf/devstats) - A toolset to visualize GitHub archives using Grafana dashboards used by the Cloud Native Computing Foundation and Kubernetes
5159
- [MeasureOSS](https://github.com/MeasureOSS/Measure) - A contributor relationship management system
@@ -56,6 +64,8 @@ members or found helpful for managing open source projects and offices.
5664

5765
## GitHub Management
5866

67+
Tools for managing GitHub organizations and repositories.
68+
5969
- [opensource-management-portal](https://github.com/microsoft/opensource-management-portal) - Microsoft's Open Source Portal for GitHub is a tool to help large organizations with GitHub management operations, onboarding and more. It is implemented in Node.js.
6070
- [hubcommander](https://github.com/Netflix/hubcommander) - A Slack bot for GitHub organization management
6171
- [GitHub Settings](https://github.com/apps/settings) - uses .github/config.yml as the source of truth, and any changes to that file in the default branch will update GitHub
@@ -75,10 +85,14 @@ members or found helpful for managing open source projects and offices.
7585

7686
## Governance
7787

88+
Tools for project governance and community management.
89+
7890
- [Minimal Viable Governance](https://github.com/github/MVG) - Currently in beta - is a repository-based approach for putting lightweight governance into free and open source projects that are run in version control systems. It provides an overall two-tier organizational governance structure for a set of free and open source projects.
7991

8092
## Project Quality
8193

94+
Tools for assessing and improving project quality.
95+
8296
- [OpenSSF Best Practices Badge](https://www.bestpractices.dev/) - The Open Source Security Foundation (OpenSSF) Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices. Projects can voluntarily self-certify, at no cost, by using this web application to explain how they follow each best practice. The OpenSSF Best Practices Badge is inspired by the many badges available to projects on GitHub. Consumers of the badge can quickly assess which FLOSS projects are following best practices and as a result are more likely to produce higher-quality secure software.
8397
- [Fosstars](https://github.com/SAP/fosstars-rating-core) - A framework for defining and calculating ratings for open source projects
8498
- [RepoLinter](https://github.com/todogroup/repolinter) - Lint open source repositories for common issues.
@@ -88,10 +102,14 @@ members or found helpful for managing open source projects and offices.
88102

89103
## Supply Chain Trust
90104

105+
Tools/frameworks for managing software supply chain security.
106+
91107
- [OpenChain Conformance](https://openchainproject.org) - The OpenChain Specification is a way for companies using Free/Libre and Open Source Software (FLOSS) to show that they meet the key requirements for quality compliance programs. Companies can voluntarily self-certify, at no cost, by using this web application.
92108

93109
## Licensing
94110

111+
Tools for managing and tracking open source licenses.
112+
95113
- [SPDX](https://spdx.dev/) - Set of standards for communicating the components, licenses and copyright associated with a software package.
96114
- [LicenseFinder](https://github.com/pivotal/LicenseFinder) - Find licenses for your project's dependencies
97115
- [ScanCode toolkit](https://github.com/aboutcode-org/scancode-toolkit) - Scan code for licenses, copyright and dependencies
@@ -113,22 +131,30 @@ members or found helpful for managing open source projects and offices.
113131

114132
## Localization and Internationalization
115133

134+
Tools for managing translations and i18n.
135+
116136
- [zanata](https://github.com/zanata/zanata-platform) - Zanata is a web-based system for translators to translate documentation and software online using a web browser.
117137
- [Weblate](https://weblate.org/) - Weblate is a free web-based translation management system.
118138
- [Respresso](https://respresso.io/localization-converter/) - Multiplatform localization converter for iOS (.strings + Objective-C getters), Android (strings.xml) and Web (.json).
119139

120140
## Websites and Documentation
121141

142+
Tools for creating and managing project websites and documentation.
143+
122144
- [Docusaurus](https://docusaurus.io) - Docusaurus is a React-based static site generator, specifically developed to more easily help create and maintain open source websites.
123145
- [GatsbyJS](https://www.gatsbyjs.com/) - Gatsby is a site generator that allows you to build fast websites and apps with React.
124146
- [VuePress](https://vuepress.vuejs.org/) - VuePress is a minimalistic Vue-based static site generator, optimized for writing technical documentation.
125147

126148
## Security
127149

150+
Security scanning and vulnerability management tools.
151+
128152
- [Eclipse Steady](https://github.com/eclipse-steady/steady) - Eclipse Steady, formerly known as "Vulnerability Assessement Tool" (Vulas), helps to discover, assess and mitigate known vulnerabilities in Java and Python projects.
129153

130154
## In-Kind Donations
131155

156+
Resources for in-kind donations and support programs.
157+
132158
The following organizations have formal or informal programs for offering in-kind donations to free and open source projects or foundations.
133159

134160
- [AWS](https://aws.amazon.com/opensource/) - AWS started a program in 2019 to provide promotional credits to open source projects. Details are in [this blog post](https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/) (Last Updated: April 14, 2021)

0 commit comments

Comments
 (0)