Hi everyone, I would like to briefly introduce myself as a potential contributor to Fedora Magazine, and I hope this is the right way of doing so.
I'm a master of Journalism and Communication and an experienced researcher in media. I'm skilled in statistics and data analysis, writing and editing. I have a pending publication in the Journal of Chinese Media Studies and focus mainly on computer-mediated communication. I am bilingual but have an adequate command of English language in order to be able to convey useful knowledge to your audience.
I've been a Linux user for about 7 years and a full-time user for about 4 (mostly Debian). I see myself as an advanced user and have a working knowledge of software from many different categories; I'd had pleasure (and displeasure) of using the OS for many of my personal mini projects.
I'm looking forward to writing with you, everyone, and thank you for reading this.
PS: I'm 26 and currently residing in China
I'd like to start writing on Fedora Magazine.
My first subject is about installing and using Jupyter notebook server on a
Whats the next step ?
Thank you in advance
*AVI* ALKALAY @*avibrazil* +55(11)99659-9059 <+5511996599059> *digital
business card* <https://avi.alkalay.net/card/>
I am currently working on the article for wednesday the 5th June. It is one
that covers the basics of changing and installing themes on Fedora
Workstation. I am intending on including how to change the icon theme,
gtk/appliucation theme, and the gnome shell theme.
If there are any major objections to this topic, please let me know, and i
will come up with a different one!
I was wondering if any one was interested in joining me to writing a
series of "Fedora: under the hood" posts (if the editorial team permits,
of course) with the aim being to:
- show that Fedora is a FOSS community with the OS being our mode of
choice to work towards the community mission.
- discuss the work that goes into the creation of each release:
including programme management, design, rebuilds, QA, websites,
announcements---all of it.
The hope is that by speaking actively about why, who, and how we do
things, we improve the general understanding of how we tick. In
addition, that improved understanding will hopefully encourage more
"users" (to use the "vendor <-> user" terminology explained later) to
join the community and contribute to FOSS---in whatever way they choose.
Finally, it will also make people aware of the resources that the
community has or does not have access too, and why some things are done
and others aren't.
Based on my personal experiences, so this is anecdotal evidence, it
seems that most people outside the community have little or no
understanding of how the Fedora community does things. They seem to
apply the "vendor <-> user" development model to Fedora too: someone,
somewhere, for some reason, is doing all of this for "users" instead of
the "community" paradigm: where there isn't a clear distinction between
"developers" and users---all contributors are also users, and we're all
part of the community and contribute in whatever ways we can often in
our free time.
Mostly, the magazine includes posts on how to use software: "to do
things with Fedora". The new website also says "Make the most of using
Fedora" next the Fedora magazine bit. So, users get to learn about all
using the tools and the software, and not much about why, who, how, all
of this software (and the accompanying information) is
developed/integrated/provided to them.
PS: Of course, the primary aspect of the "vendor <-> user" paradigm is that
the user pays in exchange for the service. This enables the "vendor" to
maintain the resources required to continue providing the service and
further improve it. How users "pay" to use Fedora if we also follow this
model does not seem to come up often somehow.
Ankur Sinha "FranciscoD"
Time zone: Europe/London
I'd like to propose we use a Taiga kanban board to track the state of our
articles and the publishing schedule.
Having a board will have multiple benefits, including:
- Quick overview of the current state and the publishing schedule
- Writing comments to the articles — things to remember when editing, etc.
- Ability to move some of our activities from the meeting to the board,
such as +1's on the pitches, assigning edits and images, or even scheduling
in some cases — that could give us more time in the meeting for other
discussions that need to happen real-time
- A board will be also more intuitive and accessible to newcomers
What do you think? Do we wanna give this a try? To give people a better
idea I've created an example board  in the teams.fp.o Taiga.
Senior Software Engineer
There's a thread on Discussion about Magazine articles that are out
of date (e.g. due to orphaned packages). I know it can't really be
done automatically, but do we have a process for marking outdated
articles in a way that's obvious to readers? If not, what might that
He / Him / His
Fedora Program Manager