Collaboration

This note describes how we imagine other researchers and developers could use and extend our workflow.

Benefit to other researchers

We hope that other researchers can use this research project as a template.
We believe these applications could serve humanities researchers exploring concepts without specific outcomes.
- Features such as Dendron's Note Graph reveal links between notes that researchers might miss.

The developers for Dendron and Obsidian create their applications for note-taking. They may lack awareness of unusual use cases such as ours.
Our project demonstrates that this use case can benefit other research communities. A concise summary of our project's goals can support discussion with developers, who may be unfamiliar with humanities research.
- The open-source model encourages interaction between users and software developers. Developers adjust their software in response to feedback.
- Open-source software invites users to contribute to its development, although this requires technical knowledge.

Changes are accessible to everyone.
Approved collaborators can contribute.
Anyone can fork the project and propose changes.
History facilitates learning (generative conflict/agonism).
Website reflects changes to internal documents, allowing observers to follow our progress and become involved.

GitHub means change history is tracked and accessible to anyone.
- Contributors can resolve change conflicts together.
GitHub Issues enables users to debate changes.
New Relic CodeStream allows users to comment on documents and see GitHub issues in context.

Digital gardening
- History of the concept by Maggie Appleton
- Loosely organised/hierarchical collections of notes that serve as knowledge bases for users.

Visual Studio Code and git/GitHub can challenge inexperienced users.
- Instructions that simplify this procedure could smooth this learning curve, allowing users to contribute quickly.

Backlinks