Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSGeo Graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions #407

Closed
dstenger opened this issue Jun 4, 2019 · 3 comments
Assignees

Comments

@dstenger
Copy link
Contributor

dstenger commented Jun 4, 2019

Please also see #393.

@dstenger
Copy link
Contributor Author

dstenger commented Jun 4, 2019

Pull requests are the common way to contribute code to project.

TODO: Create wiki page.

@dstenger dstenger assigned ghobona and unassigned bermud Jan 7, 2020
@dstenger dstenger changed the title OSGEO graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions OSGeo graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions Jan 7, 2020
@dstenger dstenger changed the title OSGeo graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions OSGeo Graduation: Create documentation providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions Jan 7, 2020
@jodygarnett
Copy link

jodygarnett commented Jun 19, 2020

A CONTRIBUTING.md file is the usual GitHub convention to communicate how to contribute a patch, this has the advantage of being shown to potential contributors when they make a pull request.

This is a good place to document or link to your expectations on matters such:

  • as code formatting
  • any documentation or quality assurance expectations
  • communicate that the work being contributed will be distributed by the OGC using an open source license (this is annoying enough that many projects end up with a contributor license agreement just to be sure).

Examples from a few OSGeo projects:

See GitHub community checklist here for your project.

@ghobona
Copy link
Contributor

ghobona commented Nov 17, 2020

2020-11-17 OSGeo Sprint

The page describing how to contribute to the project has been created at https://github.com/opengeospatial/teamengine/blob/master/CONTRIBUTING.md

@ghobona ghobona closed this as completed Nov 17, 2020
@dstenger dstenger added this to CITE Aug 1, 2024
@dstenger dstenger moved this to Done in CITE Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

5 participants