tmdinosaurcenter
/
dwc
mirror of https://github.com/tdwg/dwc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Darwin Core Maintenance Frequently Asked Questions (markdown)

John Wieczorek 2021-08-06 22:53:54 -03:00
parent 7359726b32
commit 311b360b6f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Darwin-Core-Maintenance-Frequently-Asked-Questions.md

@ -38,11 +38,11 @@ The Darwin Core Maintenance Group monitors and actively engages in discussions a
Given the number and diversity of changes that might be proposed, the Darwin Core Maintenance Group will monitor the commentaries and try to steer the proposals toward consensus, with the goal of being able to create a coherent updated release of the standard with as little delay as possible.
No given proposal has to reach a consensus for a release to be made. To avoid a potentially never-ending review the Maintenance Group will assess the state of proposals in the milestone after the first thirty days and decide whether to make a release of those proposals that had no controversy, or to wait long enough to include all of those that appear to have viable solutions to any problems that are identified in public review.
No given proposal has to reach a consensus for a release to be made. To avoid a potentially never-ending review the Maintenance Group will assess the state of proposals in the milestone after the first thirty days and decide whether to make a release of those proposals that had no controversy, or to wait long enough to include all of those that appear to have viable solutions to any problems that are identified in public review. The Maintenance Group may recommend that particularly complex or controversial issues to be solved within a Task Group chartered under the Darwin Core Maintenance or another Interest Group, either before public review, or as a result of public review.
## How can I best contribute to a public review?
Constructive comments and questions are welcome. These should be included in the relevant proposal (issue in Github) or through tdwg-content@lists.tdwg.org. Providing assent is considered constructive. The best way to do this, so as not to clutter the conversation, is to use an emoticon reaction to the first comment in the issue. We can use this to gauge the relative level of interest in a proposal. Dissenting opinions must be explained in a comment and must not be anonymous in order to be considered in the revision of the proposal and for the purpose of assessing consensus.
Constructive comments and questions are welcome. These should be included in the relevant proposal (issue in Github) or through tdwg-content@lists.tdwg.org. Providing assent is considered constructive. One way to do this is to use an emoticon reaction to the first comment in the issue. We can use this to gauge the relative level of interest in a proposal. Comments saying who you are and who you represent in your shared opinion are particularly useful. Dissenting opinions MUST be explained in a comment and MUST NOT be anonymous in order to be considered in the revision of the proposal and for the purpose of assessing consensus.
## What happens after the public review?