On Mon, Apr 2, 2018, at 8:45 PM, Aidan Kahrs wrote: > Matt, > First thank you for the response. I am somewhat surprised to recieve a > response to this thread from the FPL. In answer to your question, it will > likely be a collection of the various types of documents as you detailed in > the third option. Alternatively, I can see this taking the form of filling > in gaps in existing Fedora documentation that we have discovered in the > process of using it for TigerOS. One possible example that I can think of > is the lack of consistency in various versions and forms of the > documentation on building RPM packages. It is also relatively difficult to > find detailed information on how to reproduce the Fedora building and > hosting infrastructure inexactly, for example on a smaller scale. I have > also copied the rest of the TigerOS team on this message to get their > input. I believe we could move to a model where we had a shared content set in Fedora's pagure that would containt he content that is not remix specific. This would include docs about the infra components you mention which I believe are part of the Infrastructure teams' goals to document. If you all also adopted the Fedora tooling, you could maintain a content set of Tiger OS specific items as well. When you went to publish you would be able to construct a docs site that contained both sets of content. We could most likely even get this to the point that for something like the Installation Guide you could just selectively replace the content you need with the Tiger OS content and draw from Fedora for the rest. WDYT? regards, bex > Thank you. > Sincerely, > > Aidan Kahrs > abkahrs@xxxxxxxxxxxxxxxxx > > On Mon, Apr 2, 2018 at 12:02 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> > wrote: > > > On Mon, Mar 26, 2018 at 05:48:09PM -0400, Aidan Kahrs wrote: > > > For the last year or so, I have been the lead of a project to develop a > > > Fedora remix and in this process the team and I have learned many things > > we > > > feel may be useful to the upstream Fedora community. We have created our > > > own custom RPM packages, are in the process of automating our build > > > infrastructure(not using Koji as it is too large scale for us), and have > > > setup an RPM and ISO download mirror. Much of this process was fumbling > > > around in the dark trying to find the right way to do it. I have > > included a > > > number of links to various resources about the remix below. > > > > > > Please let me know if there is interest in this. The team and I would be > > > glad to work with you. > > > > I'm super-interested. We recently updated our mission to focus more on > > exactly this, and better documentation would really, really help. > > > > I'd love for this to be on https://docs.fedoraproject.org. I'm not sure > > exactly where in the structure it would belong, but we're still in the > > process of figuring that out anyway. > > > > Do you see this as: > > > > - a kind of book-like guide? > > - a series of short howtos? > > - a collection of various types of documents (howtos, reference > > material, examples) > > > > This might help us figure out where to put it. :) > > > > -- > > Matthew Miller > > <mattdm@xxxxxxxxxxxxxxxxx> > > Fedora Project Leader > > _______________________________________________ > > docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > _______________________________________________ > docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx
