Self Introduction: Otto Urpelainen
by Otto Urpelainen
I have been using Fedora since 2013 and started contributing in the
beginning of 2021 by adopting some orphaned packages, doing package
reviews and submitting patches for various tools.
I recently volunteered to move Fedora Package Maintainer docs from the
old wiki system  to docs.fedoraproject.org. Supposedly, I will also
be involved in maintaining the new system afterwards. Thus I decided to
join the docs mailing list, too.
My plan for Package Maintainer docs migration is to first reset the old,
unfinished attempt at pagure.io/fedora-docs/package-maintainer-docs to
use the fedora-docs/template, then convert existing material on the wiki
with pandoc. If anybody knows a better way, please let me know.
1 year, 10 months
Subject: Hema: Introducing myself
by Hema ranjan
Hi Doc team, I am Hema from India. I am currently working as an Academic writer for Evelyn learning systems, we Author solutions for CourseHero, both online and textbook. I also Freelance for Chegg.
I am currently pursuing my Ph.D. During the course of my research, I have extracted Bug reports from Bug repositories (Jira), Reviews from ReviewBoard, and user comments from YouTube using python-Jira, RBTools, and YouTube data API python packages respectively, Transformed these data into the desired format and loaded them into PostgreSQL database. Have built and manipulated PostgreSQL database. Have worked with Topic models, Statistical language models, and statistical information retrieval models. Have mined unstructured software artifacts such as IRC meetings log, Bug report, and Reviews using various statistical models, Processed data using preprocessing techniques, and visualized data using python packages.
I have been using Fedora all through my research. Now would like to contribute. I am currently going through ASCIIDoc and would like to contribute to the documentation part while sharpening my technical skills. Would love to start working. Thanks in advance.
docs.fpo editing link
by Francois Andrieu
I've noticed the "edit this page" on translated pages is incorrect/non-working, as it redirect to a non-existing local path (file:///tmp/tmphvbofl0 ...).
example here: https://docs.fedoraproject.org/es/fedora/f33/
I think it may be confusing for people desiring to translate or edit the documentation, so I propose to:
- remove this link on translated pages only. I think no link is better than a broken one.
- add a "translate this page" or "edit this translation" (or something like that) that redirect to translate.fpo
I haven't found any mention to translate.fpo in https://docs.fedoraproject.org/en-US/fedora-docs/, and I think this should be a valuable information for people willing to contribute to the documentation.
What do you think ?
by Tom Cummings
Hello everyone. I'm Tom Cummings. I'm from the US. I've recently retired
from a full-time corporate job in IT. I worked in many positions from help
desk to team and department management. I focused on infrastructure,
systems/server administration, and system design. I am not a developer, but
I have worked with dev teams and software development projects for
z-series, i-series, and distributed platforms. I have basic skills in Perl
and Python coding.
I have worked with international and remote teams across the world. I speak
and understand (very rusty) German. I have a BA in History, Germanic
Languages and Literature, MBA in IT Management.
I've been using Linux for +20 years - Red Hat, FreeBSD, Gentoo, Slackware,
Ubuntu, and, most recently, Fedora. The IT environment I worked in was
primarily MS/Windows, but with a significant Linux/Unix footprint.
Currently, I am working my way through the Linux Foundation Cloud
Engineering boot camp, but I don't have much practical experience in that
I'm working my way through the Fedora Docs team Contributing guide (
learning AsciiDoc. I'll also work on setting up a workspace with Git and
I'd like to contribute to documentation in a way that is most helpful to
the Fedora community while continuing to sharpen my technical capabilities,
especially with servers and cloud engineering. That said, I am ready to
help on whatever needs to be done.
by Peter W Smith
A short message to introduce myself. I'm Peter Smith, originally from
the UK but living in the Netherlands. I work as a Technical Writer for
a marine propulsion manufacturer, but don't get to do any software
writing as part of my work. Before I got this job I was studying for
the RHCSA exam and heading down a sysadmin path, so that's the area
where most of my software knowledge is. I have some experience with
using Go, Python and a little bit of Ruby as well. I also worked as a
linguist at universities in the USA and Germany for a decade and for my
academic publishing used LaTeX extensively, and from that I developed
an interest in many different content management systems.
I have been using Linux for a few years now, and Fedora for most of
that time so it's nice to be a part of the project.
I'll contribute in whatever way I can and keep my eye out for things
that I can pick up. I started recently with doing some of the release
notes for Fedora 34, and will watch the repo and quick-docs issue page.
Here's my gpg info:
gpg --fingerprint 0B12A0BB
pub rsa4096 2020-09-28 [SC]
565F 35FB 9642 5C92 C2CC BCD1 AE88 BC51 0B12 A0BB
uid [ unknown] Peter W Smith <peter.w.smith16(a)gmail.com>
All the best,
New version document (specifically 34),
does not contain additional guidelines to modify the installation to more
closely resemble the settings of a freshly installed one
by Alireza Haghshenas
Consider this scenario: I have installed 33 (KDE) and decided to upgrade to 34, in part to benefit from the change to pipewire.
After the upgrade, I discover that the system's audio stability is now much worse than before.
Also, it appears that pipewire is not my default audio server.
So most QAs regarding similar problems in 34 do not apply to me. My system is in an intermediate state between 33 and 34.
I don't have the statistics, but I expect that a non-negligible percentage of each version's users should be people who have upgraded from a previous version.
If there is no guideline for them, they will not benefit from these changes.
So here is my suggestion: A section be added to the "Upgrading Your Current System" document on how to enable some of the changes that will be default in the latest release.
## Setting Pipewire as the default audio service
In 34, pipewire is now the default audio service, you can read more about this change (here)[link] and follow (these)[link] steps to modify your current system to match these new defaults.
Or alternatively: You can run this command to modify your default: `command`
2 years, 1 month