| @fungicide:matrix.org | when it comes to automating infrequently performed tasks, this always comes to mind: https://xkcd.com/1205/ | 13:34 |
|---|---|---|
| @jreed:matrix.org | I don't want to automate creating a new repo. Maybe at minimum just documented better. | 14:29 |
| @brunomuniz:matrix.org | Chiming in a little, as someone who spent a lot of time automating things, I agree there's no reason to automate this. | 14:33 |
| But a **good**, **up-to-date**, **centralized** and **public** documentation is very important for this. | ||
| @tcervi:matrix.org | Agree with jreed , my original comment was about enhancing the documentation for this "not frequent" task of creating new repos, such that when someone needs to do it again the info is centralized and not relying in 2 or 3 community members. | 14:52 |
| @fungicide:matrix.org | right. from the opendev collaboratory perspective, we document the technical aspects of project creation in our infrastructure manual. the starlingx community will need to document any specific additional steps or requirements they have, but are also welcome to copy documentation from the opendev manual (it's published under an open license) | 15:23 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!