One approach here would be to have several repos (i.e. documents). For
example, we could break up this document:
https://fedora-infra-docs.readthedocs.io/en/latest/ into

* Fedora Infra Developers Guide
* Fedora Infra Sysadmin's Guide (i.e. the SOPs)

We would probably have to create a new section on this page:
https://docs.fedoraproject.org/en-US/docs/
There is an "Engineering Teams" section that contains a couple links
to our docs (https://docs.fedoraproject.org/en-US/engineering/)
but a whole separate category on the main page is probably a good idea
here IMHO.

This new section would probably list documents like the newish Fedora
Accounts document
(https://docs.fedoraproject.org/en-US/fedora-accounts/) and any other
user-facing documents about our apps too.

For the structure of the sources, something simple like repos labelled
"Documentation" in the fedora-infra github org might be the way to go,
like the source for the Fedora Accounts docs:
https://github.com/search?q=topic%3Adocumentation+org%3Afedora-infra&type=Repositories

cheers,
ryanlerch

On Wed, May 5, 2021 at 9:49 PM Ryan Lerch <rle...@redhat.com> wrote:
>
> Count me in. I'm keen to help out with this initiative!
>
> cheers,
> ryanlerch
>
> On Wed, May 5, 2021 at 7:44 PM Mark O'Brien <marko...@redhat.com> wrote:
>>>
>>>
>>> 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@lists.fedoraproject.org
>> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
>> 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@lists.fedoraproject.org
>> Do not reply to spam on the list, report it: 
>> https://pagure.io/fedora-infrastructure
_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to