Hello, I would like to start the conversation about what we might be able to contribute to Fedora that will be mutually beneficial for both projects. 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.
TigerOS ------------ Website: https://tigeros.ritlug.com
GitHub: https://github.com/RITlug/TigerOS
#rit-tigeros on irc.freenode.net
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On 03/26/2018 05:48 PM, Aidan Kahrs wrote:
Hello, I would like to start the conversation about what we might be able to contribute to Fedora that will be mutually beneficial for both projects. 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.
TigerOS
Website: https://tigeros.ritlug.com
GitHub: https://github.com/RITlug/TigerOS https://github.com/RITlug/TigerOS
#rit-tigeros on irc.freenode.net http://irc.freenode.net
Hi Aidan!
As I understand it, you want to contribute new, original documentation specific to creating a Fedora Remix or derivative work based on upstream Fedora.
I see this as helpful and useful to include in upstream Fedora; however, I am unable to answer where this type of content should live.
Do you have any existing documentation already written as a reference? If so, it is helpful to see what you have so far. If not, do you have a bullet-point list of topics you could share, to help us understand what topics you want to cover? This helps us understand where your topics could fit in the new system.
In the meanwhile, check out AsciiDoc. AsciiDoc is the markup language we use for our documentation. Until you get an answer on where this belongs, you and the TigerOS community can work on writing documentation in AsciiDoc. This will make it easier to "plug in" to the right place, once we know where it belongs.
https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/
https://asciidoctor.org/docs/asciidoc-recommended-practices/
Check out examples here for how we are doing docs now:
https://pagure.io/fedora-docs/quick-docs
Do you have any questions for us?
All, We currently have some existing documentation written and still being worked on. It can be found at https://github.com/RITlug/TigerOS/wiki. Much of this documentation is specific to TigerOS and may or may not be useful to the wider Fedora community. If however there are things that you would find useful, please let me know and we can edit or update them as necessary to be useful to both projects. As far as a list, I was able to brainstorm some challenges that the team faced in the course of developing TigerOS that may have solutions in documentation. I have included the list below.
mock failing
koji not scaleable to small projects. Much of the details of how to set it up confusing
RPM docs not centralized
GRUB and anaconda installclass
no established procedure for replicating Fedora build system
not sure who to ask about how fedora does building, how fedora handles signing keys, etc. no sense of who to ask what
automating builds biggest issue...
This is a very rough list so it may be missing things. Please let me know if anything is unclear. I have also copied the rest of the TigerOS team on this email so that we are all on the same page.
Thank you. Sincerely
Aidan Kahrs abkahrs@fedoraproject.org
On Thu, Mar 29, 2018 at 1:32 PM, Justin W. Flory jflory7@gmail.com wrote:
On 03/26/2018 05:48 PM, Aidan Kahrs wrote:
Hello, I would like to start the conversation about what we might be able to contribute to Fedora that will be mutually beneficial for both projects. 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.
TigerOS
Website: https://tigeros.ritlug.com
GitHub: https://github.com/RITlug/TigerOS https://github.com/RITlug/TigerOS
#rit-tigeros on irc.freenode.net http://irc.freenode.net
Hi Aidan!
As I understand it, you want to contribute new, original documentation specific to creating a Fedora Remix or derivative work based on upstream Fedora.
I see this as helpful and useful to include in upstream Fedora; however, I am unable to answer where this type of content should live.
Do you have any existing documentation already written as a reference? If so, it is helpful to see what you have so far. If not, do you have a bullet-point list of topics you could share, to help us understand what topics you want to cover? This helps us understand where your topics could fit in the new system.
In the meanwhile, check out AsciiDoc. AsciiDoc is the markup language we use for our documentation. Until you get an answer on where this belongs, you and the TigerOS community can work on writing documentation in AsciiDoc. This will make it easier to "plug in" to the right place, once we know where it belongs.
https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/ https://asciidoctor.org/docs/asciidoc-recommended-practices/Check out examples here for how we are doing docs now:
https://pagure.io/fedora-docs/quick-docsDo you have any questions for us?
-- Cheers, Justin W. Flory jflory7@gmail.com
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. :)
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. Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Mon, Apr 2, 2018 at 12:02 PM, Matthew Miller mattdm@fedoraproject.org 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@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
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@fedoraproject.org
On Mon, Apr 2, 2018 at 12:02 PM, Matthew Miller mattdm@fedoraproject.org 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@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
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
3. This is a university and we have high turnover - we will not necessarily be able to maintain full documentation ourselves long-term
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@fedoraproject.org
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:
- 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)
- 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.
- 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@fedoraproject.org _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
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 Cc: tigeros@ritlug.com
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@fedoraproject.org > _______________________________________________ > docs mailing list -- docs@lists.fedoraproject.org > To unsubscribe send an email to docs-leave@lists.fedoraproject.org _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
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.
I also noticed your comment about remixes being desktop centric. That makes me think that you could possibly be confusing a remix with a spin. If this is not the case, I apologize for the misinterpretation.
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Fri, Apr 6, 2018 at 2:05 PM, Shaun Assam thebeardedhermit@hotmail.com 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 Cc: tigeros@ritlug.com
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: >
- 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@fedoraproject.org > _______________________________________________
docs mailing list -- docs@lists.fedoraproject.org > To unsubscribe send
an email to docs-leave@lists.fedoraproject.org _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
Hi Aidan,
Thank you for your response to my email and I appreciate your time to further clarify your project's goals with me.
I apologize as I've misused the term 'centric'. I think 'oriented' may be the better word. It seems that most, but not all, Fedora remixes focus on a "ready to use out-of-the-box" desktop system.
I figured if the TigerOS team, or other remix team, had relatable desktop documentation based from Fedora Workstation that they found missing from Fedora Docs, and wanted to add, having a centralized point would make it easy for future contribution. I understand that your focus at-this-time is in regards to remixes.
Thanks again.
Regards,
Shaun Assam
On Fri, 2018-04-06 at 14:36 -0400, Aidan Kahrs wrote: 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.
I also noticed your comment about remixes being desktop centric. That makes me think that you could possibly be confusing a remix with a spin. If this is not the case, I apologize for the misinterpretation.
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.orgmailto:abkahrs@fedoraproject.org
On Fri, Apr 6, 2018 at 2:05 PM, Shaun Assam <thebeardedhermit@hotmail.commailto:thebeardedhermit@hotmail.com> 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 Cc: tigeros@ritlug.commailto:tigeros@ritlug.com
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@fedoraproject.orgmailto:abkahrs@fedoraproject.org > _______________________________________________ > docs mailing list -- docs@lists.fedoraproject.orgmailto:docs@lists.fedoraproject.org > To unsubscribe send an email to docs-leave@lists.fedoraproject.orgmailto:docs-leave@lists.fedoraproject.org _______________________________________________ docs mailing list -- docs@lists.fedoraproject.orgmailto:docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.orgmailto:docs-leave@lists.fedoraproject.org
_______________________________________________ docs mailing list -- docs@lists.fedoraproject.orgmailto:docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.orgmailto:docs-leave@lists.fedoraproject.org
On Sat, Apr 07, 2018 at 02:36:45PM +0000, Shaun Assam wrote:
I apologize as I've misused the term 'centric'. I think 'oriented' may be the better word. It seems that most, but not all, Fedora remixes focus on a "ready to use out-of-the-box" desktop system.
There are definitely some others, like CloudRouter https://fedoraproject.org/wiki/List_of_Fedora_remixes#CloudRouter
Hello,
Just wanted to give an update on this. I wrote some draft documentation on the process we use for build automation as that may be useful to other remixes. It can be viewed at https://gist.asciidoctor.org/?97fa8728a54be679d1d34475b233cd09 The page also has two associated Ansible playbooks. These have not yet been generalized to remove TigerOS specific things and as such I did not link to them. I will work on doing that next. Please let me know what you think so far.
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Sat, Apr 7, 2018 at 9:13 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Apr 07, 2018 at 02:36:45PM +0000, Shaun Assam wrote:
I apologize as I've misused the term 'centric'. I think 'oriented' may be the better word. It seems that most, but not all, Fedora remixes focus on a "ready to use out-of-the-box" desktop system.
There are definitely some others, like CloudRouter https://fedoraproject.org/wiki/List_of_Fedora_remixes#CloudRouter
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader
On Mon, Apr 9, 2018 at 4:33 PM, Aidan Kahrs abkahrs@gmail.com wrote:
Hello,
Just wanted to give an update on this. I wrote some draft documentation on the process we use for build automation as that may be useful to other remixes. It can be viewed at https://gist.asciidoctor.org/? 97fa8728a54be679d1d34475b233cd09 The page also has two associated Ansible playbooks. These have not yet been generalized to remove TigerOS specific things and as such I did not link to them. I will work on doing that next. Please let me know what you think so far.
I like where this is headed. Would you like me to create a repository to contribute this too? I also wonder if this should be coordinated with the documentation that the Infrastructure team is working?
Matthew is at the FAD perhaps he can chime in.
regards,
bex
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Sat, Apr 7, 2018 at 9:13 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Apr 07, 2018 at 02:36:45PM +0000, Shaun Assam wrote:
I apologize as I've misused the term 'centric'. I think 'oriented' may be the better word. It seems that most, but not all, Fedora remixes focus on a "ready to use out-of-the-box" desktop system.
There are definitely some others, like CloudRouter https://fedoraproject.org/wiki/List_of_Fedora_remixes#CloudRouter
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
Bex,
Yes. Please create a repo for these docs to live in. If this is something you need, I would like FAS users ctmartin and tjzabel to be granted access to the repository as well. They are members of the TigerOS team and will be taking over primary maintenance of TigerOS soon.
As far as the second question, I am not sure as I do not know the exact aims of the infrastructure team's documentation efforts. I will look into it more but from my limited understanding the CI effort being undertaken by fedora infrastructure is focused on testing and gating.
Please let me know if you need anything else.
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Tue, Apr 10, 2018 at 4:12 AM, Brian (bex) Exelbierd bexelbie@redhat.com wrote:
On Mon, Apr 9, 2018 at 4:33 PM, Aidan Kahrs abkahrs@gmail.com wrote:
Hello,
Just wanted to give an update on this. I wrote some draft documentation on the process we use for build automation as that may be useful to other remixes. It can be viewed at https://gist.asciidoctor.org/? 97fa8728a54be679d1d34475b233cd09 The page also has two associated Ansible playbooks. These have not yet been generalized to remove TigerOS specific things and as such I did not link to them. I will work on doing that next. Please let me know what you think so far.
I like where this is headed. Would you like me to create a repository to contribute this too? I also wonder if this should be coordinated with the documentation that the Infrastructure team is working?
Matthew is at the FAD perhaps he can chime in.
regards,
bex
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Sat, Apr 7, 2018 at 9:13 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Apr 07, 2018 at 02:36:45PM +0000, Shaun Assam wrote:
I apologize as I've misused the term 'centric'. I think 'oriented' may be the better word. It seems that most, but not all, Fedora remixes focus on a "ready to use out-of-the-box" desktop system.
There are definitely some others, like CloudRouter https://fedoraproject.org/wiki/List_of_Fedora_remixes#CloudRouter
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
-- Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org
Hi Matt, Aidan I can do some writing and I am able to edit and assist the author in organizing the chapters of each of his documents.
Regards Leslie Leslie Satenstein Montréal Québec, Canada
From: Matthew Miller mattdm@fedoraproject.org To: For participants of the Documentation Project docs@lists.fedoraproject.org Sent: Monday, April 2, 2018 12:04 PM Subject: Re: Contributing docs for maintaining and creating a Fedora remix
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. :)
Leslie,
I just realized I never followed up on this. Our contribution will be more of a one time contribution that will be a few pages rather than a full book. I believe Bex is going to give us a repo to house the in progress docs soon. Keep an eye on this list and we(TigerOS) will let you know if and where you can assist.
Thank you. Sincerely,
Aidan Kahrs abkahrs@fedoraproject.org
On Mon, Apr 2, 2018 at 10:44 PM, Leslie S Satenstein lsatenstein@yahoo.com wrote:
Hi Matt, Aidan
I can do some writing and I am able to edit and assist the author in organizing the chapters of each of his documents.
Regards
- Leslie*
*Leslie Satenstein* *Montréal Québec, Canada*
*From:* Matthew Miller mattdm@fedoraproject.org *To:* For participants of the Documentation Project < docs@lists.fedoraproject.org> *Sent:* Monday, April 2, 2018 12:04 PM *Subject:* Re: Contributing docs for maintaining and creating a Fedora remix
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@fedoraproject.org Fedora Project Leader _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org
-
Aidan Kahrs -
Brian (bex) Exelbierd -
Brian Exelbierd -
Justin W. Flory -
Leslie S Satenstein -
Matthew Miller -
Shaun Assam