Skip to article frontmatterSkip to article content

GitHub - Asynchronous Communications

Central to our information storage and sharing, our GitHub repositories serve as the primary hub for project-related documents, community resources, and collaborative outputs from Working Groups, community events, and different kinds of events, offering transparency and collaboration for both synchronous and asynchronous communication.

All Technical Partners and Pathfinder teams use the GitHub organisation for sharing and maintaining their projects and project management resources.

Established by the OSPO Now team in collaboration with the APHRC team, the GitHub organisation enables the DSWB community to share their work as it develops, rather than only at the end. Open-source GitHub repositories (shared under a permissive license) allow all members to view, refer to, and reproduce resources even when they are not directly involved in the development of the original work. This accelerates problem-solving and the reuse of resources developed within DSWB.

Repositories created under the DSWB GitHub organisation are maintained by the repository owners and managers. All public resources will be shared under a permissive license and follow the DSWB Data Sharing Agreement.

Introductory References

If you are new to Github, you can follow this short video from GitHub for creating your first repository and other basic features you can use.

For details, please refer to these resources for introduction to GitHub:

Using GitHub Issues and Pull Requests

GitHub issues and GitHub discussions serve as a dynamic space where updates, queries, and discussions take place. The GitHub issues and project boards allow the project delivery team to share information related to specific topics, maintaining transparency among community members. These features ensure that even individuals not actively participating in a conversation can stay informed about ongoing developments and contribute where they can. Contributors can respond in real-time, but the system is mainly used to accommodate varying time zones, allowing participants to engage at their convenience.

When soliciting feedback, adding clear titles, mentioning the relevant people, and indicating timelines helps improve engagement. These issues can be cross-posted on other communication channels to boost their visibility.

Some examples of when issues and discussions can be used for communication purposes are the following:

To indicate the specific nature of the issue/discussion, we also use words such as [TALK], [INVITATION], and [FEEDBACK NEEDED] (in square brackets) before writing the full title.

You can learn about other cool features when using issue in this video.

Organising Issues in Project Boards

Projects boards on GitHub is a good way to organise and prioritise different issues (task lists) either related to a single GitHub repository, or from across different repositories such as demonstrated in the DSWB organisation](https://github.com/orgs/aphrc-dswb/projects).

Main steps for creating a project are the following that you can follow by watching this video tutorial:

You can follow more GitHub’s YouTube videos for additional features.

References for Project Management

References
  1. Community, O. (2024). Open Seeds OLS-9 Week-5 Content - Version Control and GitHub for Collaboration - Skill Up. Zenodo. 10.5281/ZENODO.14268644
  2. The Turing Way Community. (2025). The Turing Way: A handbook for reproducible, ethical and collaborative research. Zenodo. 10.5281/ZENODO.15213042
  3. Sharan, M. (2025). Project Management tips and tools. 10.5281/ZENODO.14775653