Backlog Refinement

[cubap]

Across multiple repos, create issues and identify backlog items that specifically target community building.

[cubap]

Rerum Website Repository (this one)

The goals here are to make the website accurate, usable, and impressive–in that order. Issues that need to be organized or created fall into the following categories... probably.

Marketing

Focus on the text content of the blocks of the site and consider any major areas for addition/removal or overhaul. Look for incomplete lists of projects, outdated lists of tools, and clear semantic separation between the SLU-owned platform and the community products.

Documentation

This is the place for more generalized community information, contribution guides, style guides, etc. Top-level architecture charts and explainers can be added to documentation in the repo and/or rendered in the website. If any information is duplicated in more than one place make sure there is a plan for keeping the truth in sync.

Implementation and Maintenance

Ensure that the website can deploy reliably, is simple to maintain and update, and invites others to contribute to the broader community. Design a roadmap for the future of the communication for the community as appropriate–forums for discussion, schedules for events or meetings, open lists for contributions and related projects.

Repository Maintenance

Some of the issues may be old or unclear enough to wontfix. There may be rules or files that don't need to be around still. Several issues may ask for relocation to other repositories.

[cubap]

Rerum Community Server

This is based on the rerum_server_nodejs repository and may borrow some of the existing issues for them. Some issues, like CenterForDigitalHumanities/rerum_server_nodejs#203 can be completed and carried over or completed in the new repository first. The order is not as important until both exist.

Setup and Contribution

These issues identify items needed for contributing. Also included here would be the human interfaces of setting up a discrete server or connecting an external application to the SLU (or indeed any) RERUM instance.

CI/CD, Testing

Setting up and refining the development and deployment harnessing for the repository server. Ensure tests exist and run, deployments are efficient and regular, and design a release structure for community products.

Code Cleanup

This repository is from a few older cobbled together repositories and has been 'maturing' for almost a decade. There is definitely room for the review of existing code for conformity and cleanliness.

Automated Documentation

Design a build process for API documentation when changes are made to certain files.

Extensions and New Services

There is a call for new things in RERUM, such as specific standards or content type services. This may not ultimately belong within the community server, though, so it is prioritized last.