Re: Infrastructure and release engineering Documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I think it's a good idea to centralize them like this.

Some things are kind of hazy if they are Infrastructure or Release
engineering, but otherwise I think the two areas could go well together.

Probibly the first thing we should do is work on moving and reworking
the contribution/getting started stuff out of the wiki and into docs. :)

This would be a good starting point as it is possibly our most important doc.
 

Then, perhaps it might make sense to do a pass and mark/note all the
docs we want to just drop (no longer relevent, etc).

The bulk of the work would be in this task I imagine, between deciding
what we don't need and rewriting what is out of date.
 

Thanks for working on this!

kevin
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux