On Wed, Apr 4, 2018, at 10:49 PM, Aidan Kahrs wrote:
Bex,
Our goal is to contribute updated and new generic documentation for making
a remix, but we want to keep our project-specific documentation in our
GitHub wiki; we want to know where to put the updated and new generic remix
documentation.
The overall idea is to add what we found missing when working on TigerOS.
This should help to make the process of making a remix easier. We are
specifically interested in contributing things that we have developed for
and discovered through TigerOS upstream to Fedora where useful.
I have included some notes from our team meeting below:
1. We plan to make a "drive-by contribution" to the upstream Fedora docs
- We want to make sure our project-specific documentation is accessible to
our community (which at this time is located on GitHub)
2. We are interested in contributing documentation that applies to
downstream Fedora remixes
- Builder infra, etc
Ok, this makes more sense to me now. Thank you for the explanation. My answer is that
the docs.fp.o site is the right place to do this. When you have some asciidoc formatted
material you're ready to contribute, I'll help you establish a repo. If you want
a repo to work in now, I can set you up with that too. Let me know.
3. This is a university and we have high turnover - we will not
necessarily
be able to maintain full documentation ourselves long-term
I respect this situation a lot. This is why I was wondering if having your docs built
partially from our docs for Fedora Workstation would help you focus your efforts solely on
what differed for TigerOS.
regards,
bex
>
> I hope this is helpful. Please let us know where the best place to put the
> generic remix documentation is and how to proceed.
>
>
> Thank you.
> Sincerely,
> Aidan Kahrs
> abkahrs(a)fedoraproject.org
> _______________________________________________
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org