I think the idea of user specifications is good, but the method chosen is too vague. Defining the user by what they might know is not very helpful for deciding what Pijul should be.
What if the users had defined roles in various content production environments?
There would be
a part-time user who doesn’t do much but add to small repos at home
a collaborator on open-source projects that are often in other VCSs
a debugger who uses history to find where bug was introduced
a reviewer/tester that has to get specific changes onto a stable base
a release manager that has to document and package a release
automated build system
These users have definitive demands of the tool, and one need not guess as to what they already know.
I think the idea of user specifications is good, but the method chosen is too vague. Defining the user by what they might know is not very helpful for deciding what Pijul should be. What if the users had defined roles in various content production environments? There would be
These users have definitive demands of the tool, and one need not guess as to what they already know.