On Thu, Jun 25, 2020 at 3:27 PM Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > Good Morning Everyone, > > Just like every team we have technical debt in our work. > I would like your help to try to define what it is for us. > > So far, I've come up with the following: > - python3 support/migration > - fedora-messaging > - fedora-messaging schema > - documentation > - (unit-)tests > - OpenID Connect > > What else would we want in there? > These are all good things, especially the documentation one. I'd like to zero in on a particular aspect of documentation, though: getting to hack on it. A lot of our projects are surprisingly difficult to get up and running for someone to play with and hack on, and this is increasingly true as we adopt OpenShift-style deployments. One way we solved this in Pagure is by providing some quick start processes in the documentation and a fully working Vagrant based process to boot up and have a working environment to hack on the code. I'm not necessarily going to specify it needs to be Vagrant for everything, but I think this is something we should have for all of our projects, so that people *can* easily get going to use and contribute. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
