search

openwallet-foundation / governance

Apache License 2.0
0 stars 4 forks source link

Please add instructions on the mechanics and best practices in updating the config.yaml #23

Open swcurran opened 1 day ago

swcurran commented 1 day ago

As we move to a more self-serve model, it would be good to have at least a README in this repo with instructions on how to maintain the config.yaml -- both pointers to governance around elevated github privileges and the mechanics around updating the file.

The lack of instruction was OK in Hyperledger where things were all created based on existing data and it was more tweaking the lists. Here, where projects, repos and lists all have to be added, guidance would be very helpful.

ryjones commented 1 day ago

@swcurran does this help? I defer to @tkuhrt and the TAC over here on group structure, etc.

swcurran commented 1 day ago

A little bit, but its more about the tool being used then the file. There are definite parts of that which help, but the grains for project maintainers using this in the OWF context get lost in the details of the tool. I would think a readme that pointed to specific parts of that would be helpful, but the rest should be written for that audience, since the goal is they will do this work, vs. OWF staff.

A big thing would be OWF recommendations on what each project and each repo within each project should have for teams (names, GitHub roles, purpose), and if there are any default teams that should be added (in Hyperledger there were a bunch of those, but in OWF, none). For example, I might suggest teams “project-admins/maintainers/contributors” (per project), and “repo-admins/maintainers/contributors” (optional per repo) are needed , where the “*-contributors” are those that can be assigned tasks but can’t do more. Such minimum guidance is needed for those that don’t know, and sophisticated users can come up with their own schemes if needed.