Proposing a code of conduct #5
Assignees
Labels
Comments
theathorn
added a commit
to theathorn/dcp-community
that referenced
this issue
Sep 28, 2019
Add a Data Operations team User Story. Update the Acceptance Criteria for Stories HumanCellAtlas#5 and HumanCellAtlas#6 accordingly.
Merged
theathorn
added a commit
that referenced
this issue
Oct 4, 2019
* Create 0000-data-citation-plan.md Initial draft. * Tidy up prior to first review * Rephrased Summary Resolve comment on scientific publications. * Revised Summary Adopted Laura's alternative suggestion for scientific publications. * Updated Phase 1 Explicitly state "stable non-versioned project URL". Add redirect page for re-ingested projects. Do not require a DOI for Phase 1. * Update Phase 2 Specific that specific versions of projects are citable. Add requirement for a DOI. * Update Phase 3 Users can create versioned collections of data that are citable via a DOI. * Update external DOI website Add "may DOI resolve to an external website?" to Unresolved Questions. * Clarify meaning of DOI repositories * Minor updates to DOI section * Added Acceptance Criteria * Stable URLs for projects only Stable URLs are for projects only. Separate citation links are not provided for bundles or files within a project. * Updated Unresolved Questions * Clarify "Release View" question Clarify the desirable functionality of the Data Browser providing a view of a particular Data Release and allowing further faceted searches within that view. * Minor grammar fixes * Added Shepherd * Updates rarely affect primary data * Clarify decision process for DOI assigning entity * Add summary titles to the 3 phases * Clarify use of matrix output files * Update User Stories and Acceptance Criteria Add a Data Operations team User Story. Update the Acceptance Criteria for Stories #5 and #6 accordingly. * Clarify Ingest DOI update suggestion * Delete unused optional sections * Remove unnecessary implementation note * Change Data Release to Data Distribution * Define Authorized User * Clarify "cited data" in Phase 2 * Remove dependencies on Data Distribution features * Remove all references to Data Dsitribution * Spelling corrections * Approved as rfc14
diekhans
pushed a commit
to diekhans/dcp-community
that referenced
this issue
Oct 31, 2019
* Create 0000-data-citation-plan.md Initial draft. * Tidy up prior to first review * Rephrased Summary Resolve comment on scientific publications. * Revised Summary Adopted Laura's alternative suggestion for scientific publications. * Updated Phase 1 Explicitly state "stable non-versioned project URL". Add redirect page for re-ingested projects. Do not require a DOI for Phase 1. * Update Phase 2 Specific that specific versions of projects are citable. Add requirement for a DOI. * Update Phase 3 Users can create versioned collections of data that are citable via a DOI. * Update external DOI website Add "may DOI resolve to an external website?" to Unresolved Questions. * Clarify meaning of DOI repositories * Minor updates to DOI section * Added Acceptance Criteria * Stable URLs for projects only Stable URLs are for projects only. Separate citation links are not provided for bundles or files within a project. * Updated Unresolved Questions * Clarify "Release View" question Clarify the desirable functionality of the Data Browser providing a view of a particular Data Release and allowing further faceted searches within that view. * Minor grammar fixes * Added Shepherd * Updates rarely affect primary data * Clarify decision process for DOI assigning entity * Add summary titles to the 3 phases * Clarify use of matrix output files * Update User Stories and Acceptance Criteria Add a Data Operations team User Story. Update the Acceptance Criteria for Stories HumanCellAtlas#5 and HumanCellAtlas#6 accordingly. * Clarify Ingest DOI update suggestion * Delete unused optional sections * Remove unnecessary implementation note * Change Data Release to Data Distribution * Define Authorized User * Clarify "cited data" in Phase 2 * Remove dependencies on Data Distribution features * Remove all references to Data Dsitribution * Spelling corrections * Approved as rfc14
theathorn
added a commit
that referenced
this issue
Nov 4, 2019
* Create 0000-data-citation-plan.md Initial draft. * Tidy up prior to first review * Rephrased Summary Resolve comment on scientific publications. * Revised Summary Adopted Laura's alternative suggestion for scientific publications. * Updated Phase 1 Explicitly state "stable non-versioned project URL". Add redirect page for re-ingested projects. Do not require a DOI for Phase 1. * Update Phase 2 Specific that specific versions of projects are citable. Add requirement for a DOI. * Update Phase 3 Users can create versioned collections of data that are citable via a DOI. * Update external DOI website Add "may DOI resolve to an external website?" to Unresolved Questions. * Clarify meaning of DOI repositories * Minor updates to DOI section * Added Acceptance Criteria * Stable URLs for projects only Stable URLs are for projects only. Separate citation links are not provided for bundles or files within a project. * Updated Unresolved Questions * Clarify "Release View" question Clarify the desirable functionality of the Data Browser providing a view of a particular Data Release and allowing further faceted searches within that view. * Minor grammar fixes * Added Shepherd * Updates rarely affect primary data * Clarify decision process for DOI assigning entity * Add summary titles to the 3 phases * Clarify use of matrix output files * Update User Stories and Acceptance Criteria Add a Data Operations team User Story. Update the Acceptance Criteria for Stories #5 and #6 accordingly. * Clarify Ingest DOI update suggestion * Delete unused optional sections * Remove unnecessary implementation note * Change Data Release to Data Distribution * Define Authorized User * Clarify "cited data" in Phase 2 * Remove dependencies on Data Distribution features * Remove all references to Data Dsitribution * Spelling corrections * Approved as rfc14 * Formatting updates Use U.S. English spellings. Fix minor formatting errors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation: most large and diverse OSS projects have eventually required a code of conduct to explicitly define cultural and behavioral norms.
Proposed: create a very lightweight Code of Conduct providing defined standards of behavior and conduct, a well-defined moderation process, and a team tasked with moderation and implementation of enforcement policies.
This area requires further discussion.
Code of Conduct examples:
The text was updated successfully, but these errors were encountered: