Re: Contributing docs for maintaining and creating a Fedora remix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

-- 
Cheers,
Justin W. Flory
jflory7@xxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux