source commit: 537b87e

CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+---
+title: "Contributor Code of Conduct"
+---
+As contributors and maintainers of this project,
+we pledge to follow the [Carpentry Code of Conduct](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html).
+
+Instances of abusive, harassing, or otherwise unacceptable behavior
+may be reported by following our [reporting guidelines][coc-reporting].
+
+[coc-reporting]: https://docs.carpentries.org/topic_folders/policies/incident-reporting.html

GOVERNANCE.md

@@ -0,0 +1,130 @@
+# Project Governance
+This document describes the roles and responsibilities of people who manage the
+carpentries/lesson-development-training curriculum
+and the way they make decisions about how the project develops.
+For information about how to contribute to the project, see [CONTRIBUTING.md](./CONTRIBUTING.md).
+For information about the project's Code of Conduct
+and its reporting and enforcement mechanisms, see [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
+
+## Roles
+
+### Maintainers
+A team of 3-5 Maintainers is responsible for the lesson repository
+and makes decisions about changes to be incorporated into the default branch.
+Changes to the default branch can only be made by pull request,
+and all pull requests to the default branch require
+review and approval from at least one Maintainer before merging.
+
+Responsibilities of Maintainers include:
+
+* Reviewing and responding to new issues and pull requests in a timely manner
+* Attending [Maintainer meetings](#maintainer-meetings) where availability allows
+* Voting asynchronously on decisions where needed
+
+#### Lead Maintainer
+The Maintainer team includes one person in a Lead role,
+who is responsible for coordinating the activity of the group.
+In addition to the responsibilities listed for all Maintainers above,
+the Lead Maintainer:
+
+* schedules Maintainer meetings
+* prepares [the agenda for Maintainer meetings](#meeting-agenda)
+* shares the agenda with all Maintainers at least 24 hours before the meeting
+* [assigns roles at the start of each meeting](#meeting-roles)
+* acts as a point of contact for the Maintainer team
+* invites other community members to Maintainer meetings as non-voting participants
+
+Where needed e.g. due to absence,
+the Lead Maintainer may defer any of these responsibilities to another member of the Maintainer team.
+
+The Lead Maintainer has a term length of 12 months,
+and it is expected that the role will rotate among members of the Maintainer team.
+If a Maintainer is up next in the rotation and wishes to decline the role of Lead 
+e.g. due to a lack of capacity,
+they should communicate that with the other Maintainers at the earliest opportunity
+to help the team plan accordingly.
+
+#### Current Maintainers
+See [README.md](./README.md) for a list of the current project Maintainers.
+
+#### Joining/Leaving the Maintainer Team
+Maintainers volunteer to take on the role, and should be active Lesson Developer Trainers.
+A Trainer may volunteer to join the Maintainer team at any time,
+or be invited by the existing Maintainers.
+Additions to the Maintainer team will be discussed and approved by the current membership.
+No formal onboarding exists for new Maintainers,
+but some informal onboarding can be expected from the existing Maintainers.
+
+Maintainers may step away from the role at any time,
+but are expected to communicate the decision to the whole Maintainer team
+and to coordinate with other Maintainers to transfer responsibilities, e.g.
+re-assign issues, resolve outstanding pull requests, etc.
+
+### Trainers
+_Trainers_ are defined here as the group of community members who
+have been certified to teach the curriculum by The Carpentries
+(usually referred to as "Lesson Developer Trainers").
+
+The Maintainer team occasionally consults with the larger Trainer community,
+where they judge that a wider range of perspectives is desirable
+or a potential change would have particularly far-reaching consequences.
+
+### Contributors
+Anyone who opens or comments on an issue or pull request,
+or who provides feedback on the curriculum through another means,
+is considered to be a Contributor to the project.
+
+Maintainers are responsible for ensuring that all such contributions are credited,
+e.g. on the curriculum site and/or when a release of the curriculum is made to Zenodo.
+
+## Maintainer Meetings
+The Maintainer team meets frequently,
+at minimum for at least 30 minutes four times per year.
+Meetings provide an opportunity for Maintainers to
+discuss outstanding issues and pull requests
+and co-work on the project where necessary.
+
+### Meeting schedule
+See [README.md](./README.md) for details of the current Maintainer meeting schedule.
+
+### Meeting agenda
+The agenda for Maintainer meetings will be prepared as a collaborative document,
+with (at least) sections to record the following information:
+
+* lists of Maintainers attending and absent from the meeting
+* a list of items for discussion and, if necessary, amount of time assigned to each item
+  * wherever possible, the list should include a link to the relevant issue/pull request/discussion
+
+### Meeting roles
+Each meeting will have a Facilitator, a Notetaker, and (if needed) a Timekeeper:
+
+* Facilitator:
+  introduces agenda items (or delegates this responsibility to another participant)
+  and controls the flow of discussion by keeping track of who wishes to speak
+  and calling on them to do so.
+  The meeting Facilitator is responsible for keeping discussion on-topic,
+  ensuring decisions are made and recorded where appropriate,
+  and giving every attendee an equal opportunity to participate in the meeting.
+  They also act as backup Notetaker, taking over when the Notetaker is speaking.
+* Notetaker:
+  ensures that the main points of discussion are recorded throughout the meeting.
+  Although a full transcript of the discussion is not required,
+  the Notetaker is responsible for ensuring that the main points are captured
+  and any decisions made and actions required are noted prominently.
+* Timekeeper (if needed):
+  the Maintainer Lead or meeting Facilitator may choose to assign a Timekeeper,
+  whose responsibility is to note the time alloted for each item on the agenda
+  and communicate to the Facilitator where that time has run out.
+  The decision to move from one agenda item to the next belongs to the meeting Facilitator.
+
+### Decision-making
+Decisions within the Maintainer Team will be made by [lazy consensus](https://medlabboulder.gitlab.io/democraticmediums/mediums/lazy_consensus/)
+among all Team members,
+with fallback to simple majority vote only in cases
+where a decision must be made urgently and no consensus can be found.
+
+Decisions will preferably be made during Maintainer meetings with every
+member of the team present.
+Where this is not possible, decision-making will happen asynchronously via
+an issue on the curriculum repository.
+Decisions made asynchronously must allow at least one week for Maintainers to respond and vote/abstain.

LICENSE.md

@@ -0,0 +1,83 @@
+---
+title: "Licenses"
+---
+## Instructional Material
+
+All Software Carpentry, Data Carpentry, and Library Carpentry instructional material is
+made available under the [Creative Commons Attribution
+license][cc-by-human]. The following is a human-readable summary of
+(and not a substitute for) the [full legal text of the CC BY 4.0
+license][cc-by-legal].
+
+You are free:
+
+* to **Share**---copy and redistribute the material in any medium or format
+* to **Adapt**---remix, transform, and build upon the material
+
+for any purpose, even commercially.
+
+The licensor cannot revoke these freedoms as long as you follow the
+license terms.
+
+Under the following terms:
+
+* **Attribution**---You must give appropriate credit by:
+  - mentioning that your work is derived from work that is
+    Copyright © Software Carpentry, Data Carpentry, Library Carpentry,
+    or The Carpentries.
+  - where practical, linking to the respective lesson program website
+    (https://software-carpentry.org/, https://datacarpentry.org, https://librarycarpentry.org, or
+    https://carpentries.org), provide a [link to the license][cc-by-human]
+  - and indicate if changes were made. You may do so in any reasonable manner, but not in any way
+    that suggests the licensor endorses you or your use.
+
+**No additional restrictions**---You may not apply legal terms or
+technological measures that legally restrict others from doing
+anything the license permits.  With the understanding that:
+
+Notices:
+
+* You do not have to comply with the license for elements of the
+  material in the public domain or where your use is permitted by an
+  applicable exception or limitation.
+* No warranties are given. The license may not give you all of the
+  permissions necessary for your intended use. For example, other
+  rights such as publicity, privacy, or moral rights may limit how you
+  use the material.
+
+## Software
+
+Except where otherwise noted, the example programs and other software
+provided by Software Carpentry and Data Carpentry are made available under the
+[OSI][osi]-approved
+[MIT license][mit-license].
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+## Trademark
+
+"The Carpentries", "Software Carpentry" and "Data Carpentry" and their respective logos are
+registered trademarks of [Community Initiatives][CI].
+
+[cc-by-human]: https://creativecommons.org/licenses/by/4.0/
+[cc-by-legal]: https://creativecommons.org/licenses/by/4.0/legalcode
+[mit-license]: https://opensource.org/licenses/mit-license.html
+[ci]: http://communityin.org/
+[osi]: https://opensource.org