The development that has been done recently and that is being done now brings us in a better situation than we’ve had a couple of weeks ago. We’ve reduced the massive backlog of issues in various repos, and it looks like we’ve managed to take the Zotero-bits repo out of the equation—finally!
Nevertheless, I still have the feeling that CSL development is a bit rough, not as smooth as it could be. It’s too easy to feel lost sometimes. We’ve introduced the new project board to remedy that situation, but I think with moderate success only.
I think there are a few open questions:
How many repos do we need? Can we consolidate everything into one repository? If not, do we need evolution besides schema and documentation? It’s not really clear what the purpose of this repo is next to the others. I think there are basically two options: Either we get rid of it, or we give it a real purpose and start to use it for that. That could mean adding issues only to evolution, while PRs go to schema or documentation.
How to keep track of all issues and their status? We’ve tried to use a project board for this, but yeah… I’ve had a look again at what Github offers in terms of project management tools, and there seem to be three useful features:
- project boards
I suggest we start looking into labels again. Perhaps we can add something like the sane github labels. I suspect that would already give us some filtering possibilities and a bigger picture just by looking at the labels. Of course, we would have to label issues consequently. But that’s probably easier than managing the project board. I can make a proposal regarding this if that is of interest.
Concerning milestones and project boards: They seem to have a quite similar purpose. The advantage of project boards is that they can be used across repositories.