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

Condensate all policies into one page #2

Closed
pcav opened this issue Dec 4, 2019 · 5 comments
Closed

Condensate all policies into one page #2

pcav opened this issue Dec 4, 2019 · 5 comments
Assignees
Projects

Comments

@pcav
Copy link
Member

pcav commented Dec 4, 2019

We have various policies (e.g for unit tests, documentation etc.) but apparently not a central place to see them all.
From old PSC meeting:

@mbernasocchi mbernasocchi added this to ToDo in Todo Dec 12, 2019
@pcav pcav self-assigned this Dec 16, 2019
@pcav
Copy link
Member Author

pcav commented Dec 16, 2019

Last link apparently broken. Current one:
https://docs.qgis.org/testing/en/docs/developers_guide/index.html (https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/developers_guide)
The content of https://issues.qgis.org/projects/qgis/wiki/Contributor_Guidelines is:

Contributor Requirements and Responsibilities

In order to contribute code, patches, or documentation to the QGIS project, all developers/team members must:

  • Abide by the Social Contract.
  • Be familiar with the development process and the reference material available in the Development Corner, and the CODING document in the root of the QGIS Sources.
  • Ensure that all code committed to the repository is unencumbered and compatible with the QGIS license, GPL version 2
  • Not use or include any code that will cause a trademark or patent infringement. If you are unsure, ask on the developer mailing list or contact a Project Steering Committee member.
  • Join the qgis-developer mailing list and contribute to discussions
  • Agree to these requirements by sending an email to the qgis-developer mailing list stating agreement.

These requirements apply to both developers desiring commit privileges and those that submit patches.

@pcav
Copy link
Member Author

pcav commented Dec 16, 2019

What other policies are there around?

@pcav
Copy link
Member Author

pcav commented Dec 18, 2019

The only other I found is: https://plugins.qgis.org/publish/
IMHO the current situation is better than expected, and I do not see much room for improvements.

@pcav
Copy link
Member Author

pcav commented Dec 18, 2019

I add:

  • policies for approving local groups
  • po0licies for approval of certifying QGIS trainers

@pcav
Copy link
Member Author

pcav commented Jan 8, 2020

IMHO the current situation is satisfactory. Feel free to reopen if you have a proposal to improve it.

@pcav pcav closed this as completed Jan 8, 2020
Todo automation moved this from Todo to Done Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Todo
  
Done
Development

No branches or pull requests

1 participant