Add details to CONTRIBUTING.md
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 80/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Read the current CONTRIBUTING.md file in the repository root. Review the linked OSGeo Committer Responsibilities Guidelines to understand the suggested additions. Draft text for the three missing sections: contributions on behalf of an employer, source of contributions (personal/public domain/compatible licenses), and preserving copyright/attribution from other projects. Ensure the changes align with the project's existing tone and license.
Written by the indexing model from the issue text.
Description
Problem
The OSGeo Committer Responsibilities Guidelines page has some suggestions for information to include that is currently missing from CONTRIBUTING.md. Specifically, the guidelines mention adding information about:
- contributions developed on behalf of an employer.
- information about contributions coming from the contributor themselves, or another valid source such as public domain code or projects with compatible licenses.
- Preserving the copyright and attribution information for code that comes from other projects
Improvement
Additional details could be added to CONTRIBUTING.md.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 397
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 8
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pgRouting/pgrouting
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 3 days
-
points_input Developers docPossibly taken @withaman69 claimed this 101 days ago. OpenC/C++ Developers Doc. good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pgRouting/pgrouting#973 · 10 comments ·
Maintainers usually reply within 3 days
-
get_check_data developers docPossibly taken @withaman69 claimed this 102 days ago. OpenC/C++ Developers Doc. good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pgRouting/pgrouting#972 · 7 comments ·
Maintainers usually reply within 3 days
-
pickdeliver: Create and use process/driver pairPossibly taken @cvvergara claimed this 6 days ago. OpenEnhancement Pick & Delivery
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 3 days
All issues in pgRouting/pgrouting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KLayout/klayout#2554 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
LaneDibello/Kotor-Patch-Manager#375 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day