Shaun,
That may be something for the future. At this time, the TigerOS team is mostly interested in documenting the process of creating and maintaining a remix and how that differs from the process of maintaining Fedora(e. g. remixes are smaller and may not have the same amount of infrastructure available, smaller team sizes, etc.). We want to create documentation to help others interested in creating a remix do so in a scalable and sustainable way.On Fri, Apr 6, 2018 at 2:05 PM, Shaun Assam <thebeardedhermit@xxxxxxxxxxx> wrote:
I was wondering, if we had a section in the docs that is focused on the Desktop (Fedora Workstation) would this help remixes like TigerOS and Korora have a central place to contribute documentation? From my understanding, the remixes are desktop-centric. Is this correct?
Would something like this be feasible to also allow other remixes to contribute base documentation in the future?
Regards,
Shaun Assam
From: Brian Exelbierd
Sent: Thursday, April 5, 7:01 AM
Subject: Re: Contributing docs for maintaining and creating a Fedora remix
To: Aidan Kahrs, For participants of the Documentation Project
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@xxxxxxxxxxxxxxxxx > _______________________________________________ > docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to docs-leave@lists. fedoraproject.org _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@lists. fedoraproject.org
_______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
