-
Notifications
You must be signed in to change notification settings - Fork 34
Contribution Guide
The DPVCG is the primary forum for contributions and participations regarding the DPV. As such, all decisions and resolutions will be conducted through the group's meetings and call. Membership in DPVCG is not necessary to contribute to DPV, but is recommended for participating in the group's decision making process. Contributions and questions can be sent to the group's public mailing list or expressed as GitHub issues.
To suggest a new term, we request following information:
Please ensure the terms follow the Style Guide
- term
- description of the term
- whether it should be a class or a property
- relation to existing term(s) in DPV e.g. through sub-classes
- source (where applicable)
- justification or relevance of why this term should be added (where not obvious)
Suggestions are welcome via the group's meetings, mailing list, and GitHub issues.
Before submitting an issue, please see the whether the issue has been addressed on GitHub. If not, please raise the issue via the group's public mailing list or expressed as GitHub issues.
Fixes, corrections to the terms are considered as issues and can be submitted similarly. For minor changes, we may prefer to incorporate them directly rather than through pull requests and patches. For larger issues, please check with the group before submitting a pull-request to ensure its appropriate and efficient incorporation.
DPVCG strongly suggests discussing proposals (e.g. via mailing list or github issues) before submitting code or PRs. This is to ensure proposals are well-defined, and no time is spent on outputs that are difficult to integrate or are potentially outdated. Attribution is provided via git co-authoring for proposals irrespective of their origin or whether code/PRs were submitted or not. Therefore, 'contributors' are not recognised solely through PRs, and are also be added through discussions and proposals.
(1) DO NOT change the outputs (HTML, RDF) directly - they are autogenerated from a different set of inputs
(2) DO NOT make changes over the
masterbranch - use thedevbranch to make changes or raise PRs
For info on how to generate the outputs, see Documentation-Generation
If you're unsure about something, or would like clarifications, or suggestions - please communicate with us or open an issue. We would be happy to help.