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 wiki.
I’m looking forward to getting to know the Fedora docs project.
Thanks.
-Stephen
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]
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx
