Contribution agreements

Open
#124 12 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Review the linked email thread from the OSGeo incubator list to understand past discussions on contributor agreements. Research OSGeo's current policies and templates for contribution agreements. The issue asks to define a policy for the pgRouting project, which involves legal and project governance considerations, not a code change.

Written by the indexing model from the issue text.

Description

Administrative

Think about if and how to manage contributor agreements: past present future:
http://lists.osgeo.org/pipermail/incubator/2013-June/002181.html

  • Does a small pull request require a contribution agreement?
  • Ask Jody (OSGeo incubation) for some template
Dominant language
C++
Stars
1.4k
Forks
397
Avg merge
2d 16h
Merged PRs (30d)
8

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pgRouting/pgrouting

All issues in pgRouting/pgrouting

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.