...
When new versions of ArchivesSpace are released, review release notes and update tech-docs repository, as needed, providing edits/suggested changes to developers.
Identify documentation maintained by other sub-teams, link to it as appropriate, and avoid duplication of effort.
Review community-submitted issues and pull requests to the repository.
Perform yearly surveys of old documentation to provide edits/updates.
Review and manage Awesome ArchivesSpace.
Solicit feedback and contributions from the community
...
All TechDocs sub-team members should have write permissions to the tech-docs repository and assigned to the archivesspace/tech-docs team. Before the beginning of each term, the sub-team lead should email Christine DiBella with the Github handles of the sub-team members to facilitate access.
Adding subteam members to Repository:
Select the menu icon in the upper left-hand corner, and select archivesspace/tech-docs under the “Teams” section:
...
2. Select the green “Add member” button.
...
3. Type ahead for the person’s GitHub username. Only people already added to the archivesspace team in GitHub can be added here. Email Christine if anyone is not already a member of that team.
4. Subteam members are encouraged to enable notifications from the repository via the Watch functionality.
...
5. Subteam members responsible for overall repository maintenance (i.e., subteam Leads and Vice Leads) should be assigned to the “Maintainer” level role. Within the techdocs Team page, select the user(s) with the checkbox, click the “1 member selected” icon, and “Change role.”
| View file | ||
|---|---|---|
|
...
Pull Requests
In the context of Git repositories, a pull request is an event where a contributor asks the repository’s maintainer to review changes on an independent line of development that they want to merge into the main branch.
...