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.
#rit-tigeros on irc.freenode.net
Hello Docs' Team!
As part of the last meeting (last I attended) I took the task of create a
when is good to everyone choosing an hour in their week to work writing
docs. The idea behind this is to have a dedicated time to work with the
docs' and move the work forward consistently.
The link to vote for the hour you can take is this:
The deadline for voting on this will be one week (Until Next Monday).
Please vote for your preferred time.
GNU/Linux User #589060
Ubuntu User #8749
Fedora Ambassador Latam
Has anyone considered a request for a DuckDuckGo bang for Fedora Docs?
Bangs are one of the unique features of DuckDuckGo. With an alias, you
can search thousands of websites from DuckDuckGo.
For example, it would be cool if `!fdocs rpm` searched the Docs site for
RPM documentation. If I knew there were a DuckDuckGo bang, I would use
it all the time.
There is a form to submit a request for a new bang, but not sure if
someone with more awareness of how search works on docs would want to
fill this out.
I wanted to throw it out there, since Eduard and I had a conversation
about DDG bangs on Twitter. :-)
Justin W. Flory
Thanks for joining the Fedora Docs community. I've CC'd this reply to
the docs mailing list to let the community in on your questions. This
will ensure that we provide you with the best answers and quickly get
you up and running on the ideas and contributions you would like to
make to the Docs project.
The links I sent to the mailing list were git pull-requests for edits
I've made to a few documents. It was to let the Doc admins know the
files I edited were ready for review. The admins will either provide
feedback for further edits, or, if everything is good, merge them to
the master for publication to the docs.fedoraproject.org site.
There are various sub-projects to the Docs project such as Quick Docs (
https://pagure.io/fedora-docs/quick-docs), Security Related
Documentation (https://pagure.io/fedora-docs/securityguide), Install
Guides (https://pagure.io/fedora-docs/install-guide), and more. To see
a list of these sub-projects go to https://pagure.io/projects/fedora-do
For new users I would recommend editing one of the Fedora Quick Docs
pages as the best place to start. You can clone and fork the project
via git. Check out the "_topic_map.yml" file for pages marked "FIX ME!"
as those are the ones that would need attention. There is a "How to
Help" section at https://docs.fedoraproject.org/quick-docs/en-US/index.
html with instructions on how to get started.
The only tools you would need to contribute are: asciidoc (which can be
installed from the Fedora repos with 'dnf install asciidoc'), and any
text editor. The "How to Help" page I referenced above has a link to a
quick reference guide for asciidoc syntax. Also, https://pagure.io/fedo
ra-docs/quick-docs has instructions for local testing. If you use Atom
or Visual Studio Code, there are extensions available that can display
the formatted output of the asciidoc (.adoc) file you are working on.
I too do not see any links in the Fedora Docs site for cloud computing,
but I believe documentation for Fedora Cloud is currently in progress
at https://github.com/fedora-cloud/docs. I'm not acquainted with this
section of the docs project, but I'm sure someone in the community
would be able to guide you along that path.
I hope this email provided you with the answers you were seeking. If
you have any questions don't hesitate to send an email to the docs
mailing list (docs(a)lists.fedoraproject.org), or you can use the
#fedora-docs IRC channel (https://webchat.freenode.net/?channels=#fedor
a-docs). You will get a faster and direct response if the community
gets your message.
Good luck and happy writing.
> Do you have a pointer to a new user guide for contributing to the
> project? What tools I need. What repo I should download. IA am an
> DevOps SysAdmin familiar with git and markdown. I am thinking of
> something small. DNF seems like a good start to figure out the tool
> chain I need. See if working on documentation works for me.
> I joined the doc list because I am upgrading my desktop and server
> cluster to Fedora 27 and wanted to know about the Cloud Server
> group. There seems to be no documentation about it. I found the
> of packages it installed which was minimal. No OpenStack. It has
> 5 years since I have looked at OpenStack and I understand OpenStack
> their own documentation. What I do not find is a Fedora Cloud
> guide. Not extensive in-depth documentation but an overview of the
> parts and pieces (software groups and packages) and how they fit
> together. Does Fedora have a doc like this? Where should I look?
> Living on the ops side of DevOps.
I have some updates in our Modularity Docs repo , how can I trigger a
rebuild of the docs so it shows up?
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 28
Beta Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, March 22, 2018 at 19:00
UTC. Please check the  link for your time zone.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 28. Please note that this meeting is going to be
held even if the release is delayed at the Go/No-Go meeting on the
same day two hours earlier.
You may received this message several times, but it is by purpose to
open this meeting to the teams and to raise awareness, so hopefully
more team representatives will come to this meeting. This meeting
works best when we have representatives from all of the teams.
For more information please check the  link.
Thank you for your support,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
I'd like to direct your attention to the following issue about the
Release Notes workflow:
In days of yore, we kept master in the Release Notes repo "clean" and
branched before we started pushing separate notes for each release,
which saved us some work cleaning the document up after each release.
However, I think it's worth considering a change, now that we have a
publishing toolchain that doesn't involve a F18 VM and a 10 gig git repo
with a million files in it. Details are in the link above. I'd like to
hear your thoughts.