Self-Introduction: Patrick
by Patrick Pace
Hello!
My name is Patrick Pace, and I'm an English student from the United States (UTC-5). I've been using Linux since about 2007 (7.10 Gutsy Gibbon), though I've since fallen for Fedora. The first Fedora release I ever used was 22.
I'd like to contribute to Fedora's documentation. I've done quite a bit of writing over the past four years, though that has mostly been about English literature; I don't have any professional technical writing experience, sadly. :) I also have some hobbyist programming experience from fiddling with personal projects over the years--I won't overstate that experience, but it's there. I aim to at least help improve Fedora's current documentation and eventually move toward writing some basic documentation, guides and the like. There are a few issues on Pagure that I can start working on.
Here's my GPG fingerprint:
[pqp@pfed ~]$ gpg --fingerprint 714A97F7
pub rsa3072 2021-02-10 [SC] [expires: 2022-02-10]
B556 F0AD 29FE 4921 8FB8 188A C9B2 AD92 714A 97F7
uid [ultimate] Patrick Pace <pqp(a)pondero.org>
sub rsa3072 2021-02-10 [E] [expires: 2022-02-10]
Hope all of you are well,
Patrick Pace
3 years, 2 months
Present to a Linux Users Group?
by Ben Cotton
Hi Docs team,
I got a request from the organizer of a Linux Users Group in Columbia,
Maryland to see if someone could present about Fedora's use of
Asciidoc and Antora as a documentation pipeline. Specifically: focus
on the publishing pipeline of Antora is used to take the Asciidoc
files in a git repo and publish them to a web page. What does the
contribution process look like? What does an Antora configuration look
like? What makes Antora the solution for documentation at a project
the size of Fedora?
Their meetings are on the second Wednesday of the month at 7pm Eastern
(0000 UTC Thursday). Anyone feel comfortable doing this? If not, I'd
be happy to make the presentation with some help assembling the
content (asamalik, pbokoc, and bex, I'm looking at you). I have some
context for how it works, but I wasn't around for the decision to
switch, so I'd need some help there.
Thanks,
BC
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 2 months
How to improve the docs contribution for Changes
by Ben Cotton
Hi Docs team,
Matthew Miller and I were discussing the Changes process recently and
he brought up that the documentation side of the proposals is often
under-appreciated. I file release notes issues for all of the
externally-facing Changes, but that's not necessarily sufficient. The
specific Change that brought this up is the "Strong Crypto Settings 2"
change[1] that went into F33. It caused a lot of user questions.
So I'd like your ideas on how we can preemptively cover some of the
documentation aspects of the Changes in a way that isn't overly
burdensome on Change owners or the Docs team. One thing I've added is
that I'll review the accepted proposals at the Code Complete (100%)
deadline to see which changes have implemented the docs they said they
would. Are there other things we can do to be more proactive?
[1] https://fedoraproject.org/wiki/Changes/StrongCryptoSettings2
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 2 months
