FreeIPA project is already for some time without sufficient resources to revive
and maintain our former long upstream user guide. We did not find enough
manpower either in FreeIPA developer nor our users community, so we decided to
stop maintaining it.
Detailed justification including links to mail threads in:
I would like to avoid leaving any loose ends on Fedora Documentation project
side, do you have any recommendation for us? I already closed respective
Bugzillas and upstream Trac tickets with explanation. Should we also orphan the
or on any other locations? For starters, I think we should close the
"freeipa-guide" component of "Fedora Documentation" as nobody from our team
would be responding there.
Thanks for any advise.
Martin Kosek <mkosek(a)redhat.com>
Supervisor, Software Engineering - Identity Management Team
Red Hat Inc.
I'm looking at getting involved in the project as I have been a long
time user of Fedora (e.g. since Core 1) and would like to start
contributing. My name is Ryan, I'm from Western Australia (GMT+8). I
am an IT technician and have been using linux as a hobby since 2k4
(using RH9). I have also had the opportunity to work with RHEL in my
job during a project as well as having worked with a couple of other
distros. In my line of work I have often needed to produce
documentation to a professional standard and I feel I can contribute
this way currently. I believe I should be able to contribute 4 hours a
week at this point in time.
Your experience is a lot of the motivation behind the work the fedora-docs folks are doing to fix onboarding, editing, and building of docs. Unfortunately it is slow work, but it is important. If you'd like to help, please join us on the docs list (docs(a)lists.fedoraproject.org) and at our IRC meetings on Mondays from 14:00:00 to 15:00:00 UTC at fedora-meeting(a)irc.freenode.net .
> On Aug 31, 2015, at 4:37 AM, Ian Kelling <ian(a)iankelling.org> wrote:
> I've tried fedora a few times over the years. I recently met Remy
> (fedora community lead) at oscon and he convinced me to give it
> another try and give some feedback. This is meant to be constructive,
> just my impression, I could be missing things.
> I google "fedora firewall", because I'd like to learn generally about
> it, how to do a few common things like opening a port, or forwarding
> something. I see links to official fedora docs. So I think, yes, lets
> link 2:
> 2.8.2. Basic Firewall Configuration - Fedora Documentation
> (click link, it's fedora 11 doc)
> link 3:
> 3.8.13. Configuring the Firewall - Fedora Documentation
> (click link, it's fedora 19 doc)
> link 4:
> 3.8.9. Disabling firewalld - Fedora Documentation
> (click link, it's fedora 20 doc)
> link 6:
> 16.7. Firewall Configuration - Fedora Documentation
> (click link, its fedora 20 doc)
> So... now I really want to know if fedora 22 doc has a section on
> I see the url's all look like this:
> so I try changing the 19 to 22, but it takes me to
> So then I look for a search feature. I don't see one. So then I expand
> the fedora 22 drop down, and I see 7 high level categories with no
> obvious right place, so now I'm fairly confused as to how to find
> So I search firewall on google
> site:https://docs.fedoraproject.org/en-US/Fedora/22. And the closest
> thing I see is the #1 link, 14.15. Configure the Firewall to Allow
> Incoming NTP Packets. But I'm wondering if there is a general section
> like link 2 or link 3 from the original google search, so I click around
> some more, I figure there are 4 of the 7 sections in the sidebar which
> could cover firewall: installation guide, networking guide, selinux
> users and administrators guide, and system administrators guide. So I
> click on administrators guide, (and I'm slightly surprised to find a
> comprehensive table of contents, as the ui design of left menu sort of
> implied that it was THE table of contents, not that there was more
> useful list of sections within. Why couldn't I see those things in the
> expandable menu?). I do a word search, find the ntp related link I saw
> before, repeat for the other 3 sections, find one in the installation
> section which looks generic, only learn that installation has a limited
> set of firewall configuration options and this is not what I'm looking
> for. So I'm deciding there is no general firewall documentation for 22.
> So now I look back at the best link I originally found,
> and I think, yes, I'm confirming my original impression that this is
> really the kind of documentation I was looking for, but I'm really
> confused and frustrated: does any of this still apply? did they abandon
> firewall-config? What's the story?
> I've had this same experience several times with fedora, and at this
> point I've mostly given up frustrated and annoyed.
> Once, when I was feeling a bit more ambitious, I thought. Hmm, maybe I
> can help out on docs, cuz I have noticed the new links like "click to
> contribute to fedora!" So click through, quickly get to this page:
> Well, after 15 minutes of reading lots of stuff I'm not interested in, I
> can't find the source code to the fedora 22 official docs, or anything
> about how to improve them, and I think, I'd have gotten way more done
> by just going to the arch wiki firewall page, and I could have just hit
> edit and improved the thing.
> Suggestions: make previous fedora version documentation link to the
> relevant current documentation because google links to old docs are the
> reality for most fedora searches, or if there is no newer, say that, and
> say whether this is still relevant to newer distros. And port
> documentation forward, it seems there is lots of good documentation
> sections which only exist for older fedora versions. Make contributing
> to the official docs possible in some short amount of time. Make a
> search feature (this is 2015), even if it's just to some 3rd party
> search engine (google site search gave me good results).
> Oh, and how about filing a bug? First google link: "How to file a bug
> report - FedoraProject"
> https://fedoraproject.org/wiki/How_to_file_a_bug_report It's like a
> horribly bad novel when I wanted a tldr for any reader who's filed bugs
> before for free software projects and wants to file one for fedora:
> Up top, "Documentation Summary:", doesn't try whatsoever to summarize
> "how to file a bug report", but just talks about meta things about the
> document, complete waste of my time.
> 1st section after the fake summary: "How to File a Bug Report", first
> sentence: "This page describes a procedure for reporting software bugs
> to Fedora developers." Well, I'm not a fedora developer, so this isn't
> for me? Well, I don't see any other way to file a bug sooo, does fedora
> accept bug reports from it's users? And it's redundant, making it just
> bad quality writing, leaving a bad impression, and making me think no
> one actually reads or improves this page. Significant chunk of new users
> are giving up at this
> Ok, this is a wiki, so let's try and edit this page. Click log in, which
> leads to this page this page:
> which is a novel length page which as far as I can see does not actually
> lead to getting a wiki account! No wonder no one edited the page,
> creating a wiki account if a total nightmare! Suggestion: fix that.
> Ok, flash back to the filing a bug wiki page. Next sentence: 'A bug is
> defined as "an error, flaw"'..., am I doing a homework assigment? This
> document is called "how to file a bug report", not spend an hour reading
> wikipedia. Ok, next sentence says this is about
> https://bugzilla.redhat.com/, let's skip to the chase and try using
> that, because the rest of this document looks pretty useless.
> Go there, and see from the 1st sentence.: "Thank you for visiting Red
> Hat Bugzilla. Red Hat Bugzilla is the Red Hat bug-tracking system and is
> used to submit and review defects that have been found in Red Hat
> distributions." Ok, so am I at the wrong place? This is confusing. Is
> fedora a "a red hat distribution"? I skim
> a bit more... "If you are a Fedora Project user and require assistance,
> please consider using one of the mailing lists we host for the Fedora
> Project. " Well, I'm filing a bug to get "assistance" in it being fixed,
> so it seems I should post it on the mailing list instead?
> So, wondering if fedora is a red hat distribution, I remember that there
> is a link on the main fedora page "Learn more about the relationship
> between Red Hat and Fedora »." So I go there. It's not very helpful, its
> not well written to stand on it's own. The first section goes like this
> "jill makes pizza for anyone. John makes pizza for big companies. People
> go to jill in order to collaborate with john. Businesses love john's
> pizza. The end. (notice a gaping hole? Why would someone go to john in
> order to collaborate with jill? And tt's pretty relevant title of the
> page.). Anyways, this one is a minor gripe compared to the rest, but my
> suggestion is to replace it with a higher quality fedora domain page,
> which includes a link to the red hat page.
> websites mailing list
-----BEGIN PGP SIGNED MESSAGE-----
I just joined the list and I'm excited about being able to contribute to Fedora's documentation! Kushal Das pointed me in this direction after I did some writing about systemd-networkd.
I work on all things virtualization and OpenStack at Rackspace and I write regularly for our company blog and my personal blog. I enjoy writing more comprehensive, functional documentation that shows people how to connect a few different technologies or tools to accomplish something. As an example, I've written some things around systemd-networkd that helps users make sense of the disparate systemd documentation on freedesktop.org. I'd like to do more of this formally for Fedora if possible.
As far as more formal writing goes, I've recently completed a peer-reviewed research paper about Linux container security. This is really fun for me, too.
I'll be in the 5PM session here at Flock today to learn more about how I can contribute!
pub 4096R/C1011FB1 2015-06-11
Key fingerprint = 1BF9 9264 9596 0033 698C 252B 7370 51E0 C101 1FB1
uid Major Hayden (Personal) <major(a)mhtx.net>
uid Major Hayden (Rackspace) <major.hayden(a)rackspace.com>
uid Major Hayden (Fedora) <mhayden(a)fedoraproject.org>
uid Major Hayden (Keybase) <mhayden(a)keybase.io>
sub 4096R/B322E6F0 2015-06-11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
Hey all, I’d like to introduce myself as a newcomer to Fedora docs.
I'm Stephen Gilson and I work on the RHEL documentation team for Red Hat as
a Sr. Content Strategist. I’m based in the US, in Massachusetts.
Late last year, I started getting involved in RHEL.next planning
discussions. As part of that process, the RHEL doc team reviewed its
approach to upstream and in February, while I was in Brno, CZ for planning
meetings and DevConf.cz, we decided to make this a reality and to step up
our engagement with the Fedora docs project officially. Now we just have to
figure out how.
Fedora.next, with its three editions and modularity will certainly affect
RHEL as an upstream. So it makes sense for us to increase our
collaboration with the Fedora team on documentation that could cover
portions of the product that Red Hat ships.
We hear you guys talking about making doc contributions easier and also
targeting end-users with specific, right-sized content. Last month’s
“Fedora Publishing” thread on the docs project list was a great
introduction for me to some of the issues the community faces relating to
contributions, tools, and publishing. Our own process has been undergoing a
transformation to simplify and speed up the publishing process as well.
The perspective we’re working to develop (with a long way still to go) is
to start from use cases, letting these drive decisions on topics,
priorities, interfaces and even content navigation on our customer portal.
I saw some of this in the Fedora Publishing thread -- a strong desire to
simplify the authoring experience without sacrificing the kind of serious
content management features not typically found in your average open source
I’m looking forward to getting to know the Fedora docs project.
Stephen Gilson, Sr. Content Strategist, Platform documentation
Customer Content Services
Red Hat, Inc.
As a [user role], I want to [goal], so I can [reason]
I've been reading the guides for new contributors and I'm slightly
confused. If I want to proof read a text, how do I know which one
should I pick? Where are the texts to be read?
There's a list of tasks for new contributors but I can't understand
how does it works...
I'm sorry to annoy with these surely silly questions, but I don't know
what else to do.
Cheers and thanks,
#259: Fedora Cookbook Contributions
Reporter: | Owner:
immanetize | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 0
Concept approved (reviewers only): |
Badge definition status: |
Full, needs review |
Manually awarded: |
What the badge should be granted for:
Contributing "recipes" to the Fedora Cookbook:
1 submission: Cookbook I: Commis
- "You had a recipe published in the Fedora Cookbook. Appetizing!"
5 submissions: Cookbook II: Tournant
- "You have published 5 recipes in the Fedora Cookbook. Tasty!"
15 submissions: Cookbook III: Grillardin
- "You have published 15 recipes in the Fedora Cookbook. Delicious!"
30 submissions: Cookbook IV: Saucier
- "You have published 30 recipes in the Fedora Cookbook. Scrumptious!"
50 submissions: Cookbook V: Sous Chef
- "You have published 50 recipes in the Fedora Cookbook. Delectable!"
100 submissions: Cookbook VI: Chef de cuisine
- "You have published 100 recipes in the Fedora Cookbook. Decadent!"
150 submissions: Cookbook VII: Gourmand
- "You have published 150 recipes in the Fedora Cookbook. Beefy!"
Badge names borrowed from http://en.wikipedia.org/wiki/Brigade_de_cuisine
, suggestions for improvement on names and patter are welcome. Some
dining-related artwork would be greatly appreciated.
Submissions are reviewed and committed manually, so the badges will have
to be manually awarded as well. Anyone in docs-writers should be able to
award these badges.
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/259>
A place to collect and debate badge ideas for the Fedora Badges app
I'm one of the contributors of the translation team.
I had difficulties to translate some technical parts of f23' release notes.
The most difficult one, Perl :
The other programming language were ok, keeping it to the minimum or
with fedora context, plus a link to the place to have technical details.
Kickstart part was also a little bit tough :
In my understanding :
* if it is not for end user
* or if it everything is duplication of other release notes
=> we should only give a link to the pertinent documentation
I image it is a huge work to produce release notes, but can you please
make it a little bit easier for Fedora 24 ?
Thank you for your work and your help to make translation easier.
You are kindly invited to the meeting:
Docs Office Hours ( Americas ) on 2016-02-25 from 12:00:00 to 13:00:00 US/Mountain
The meeting will be about:
Office hours for Fedora Docs contributors. Stop in to #fedora-docs for help with writing documentation or just to schmooze with the Docs community. Bring your own cake.