search

CatalogueOfLife / backend

Complete backend of COL ChecklistBank
Apache License 2.0
15 stars 11 forks source link

Consider forking workflow #1057

Open mdoering opened 3 years ago

mdoering commented 3 years ago

We need a way for projects to allow work to be done in a fork that does not create inconsistent states of the main project. The goal would be that the main project should always be in a releasable state. This is needed for both higher frequency in releases, e.g. weekly, more involvements from more people and also an extended catalogue which automatically augments data more frequently.

A forking workflow with check ins and outs would also allow us to record smaller "commits" that document the changes applied to a project. This could replace the manually created, singular whats new document in our metadata for a release. Instead every "commit" would be documented (e.g. updated ITIS to version xyz, added new sector, etc).

mdoering commented 1 year ago

@olafbanki @dhobern @thomasstjerne we should discuss/design in this issue a better workflow for projects with multiple editors. It is important to start this, I don't see that the current state can be scaled to multiple editors!