For my idea it is not going to be worse than it is, i.e. compare access control to whatever you have on developers.hive.io, if you want to edit that you go to code repository and you can make your change, submit PR, maintainer then can accept it. Same here, even using mostly what we already have (community, tags, etc.).
Auditing is just extending UI to have history of edits etc.
I was hoping to start with those https://github.com/openhive-network/hive/tree/develop/doc/devs/operations for MVP, but again, lack of bandwidth and higher priorities related to upcoming new version.
You are viewing a single comment's thread from: