Hi, I am Alain, FAS: avigne
As discussed today in #fedora-devel, here is some feedback about my
experience trying to join Fedora as a contributor -> packager.
TLDR: Adding a new package and become a Fedora packager is NOT easy.
I am not a computer scientist, but as an Integrated Circuit designer, I am
using eCAD proprietary tools heavily.
With my years of experience, I came up to know how to use Fedora, and I
like this distro because it is reliable, and fairly up to date with
When Fedora FEL spin was alive, I picked up some tools, and slowly learn
how to use them. gEDA, PCB, NGspice, GerbV, etc...
At some point, 2 years ago, I thought Open Source world gave me a lot, it
was time to give back... So I contacted the pcb-rnd project , and
started to contribute code around GTK, and GUI aspects of the application.
Naturally, as I am developing with a Fedora system, I thought it could be
nice to have pcb-rnd for Fedora... I had no clue on how to proceed, and
first, I tried to find someone who can do that for me...
Found no one. (I should have known :).
Time passes by, and one day a pcb-rnd Mageia contributor showed me the
.spec file he wrote for Mageia. I was curious about what was behind all
those commands and how this "recipe" (the .spec file) can lead to a package.
So I dug into the documentation (mainly Fedora wiki) learning how to first
build an RPM, then after a successful local "mock", my curiosity was
satisfied. I thought I understood the purpose of those tools (rpmbuild,
That is when I started to think about contributing this package to Fedora.
"It should be easy, I have the recipe, I just need to find where to
check-in the .spec file..." Easy thought, no ?
Unfortunately, no, this is not easy.
First, there are tons of pages describing the process, and what to do. In
theory the process is well described.
In practice, I got stuck in the "need a sponsor" phase where I think there
is kinda chicken-and-egg problem for a new contributor.
I might detail that, later, if someone is interested in this list.
My feeling today, 6 months after I jumped in the unknown is not very much
I had to register, open accounts, leave traces on many systems before being
able to .... get nothing at the moment
- mailing list
- Freenode registration
I feel like someone who has a complicated map under the eyes, walk, try and
error to make sense of the map, up to a point where the map says: next step
is "find a sponsor" and I have no idea how this is being done.
And time passes by... Slowly. I am silently ignored.
Somebody says today : "Do informal reviews [a suggestion on the wiki, but
what can I suggest ? I have no experience ->chicken and egg problem], make
some mails, fill some bugs and you will get noticed".
I think this is the problem: nobody noticed, it seems nobody cares having a
So, I am concluding: Fedora = too big ship, mainly automated, with a lot of
processes (procedures, way of working) and a community not open to new
contributors [I recall, my experience is only about contributing a new
package], because this is too complicated (which I agree and understand).
That said, I am a patient man, and I have done all this travel not to being
stop by a wall. I spent my life trying to get around, over, across... so
many walls, so, I won't surrender here !
Thanks for reading till that point, and let us open the debate.
PS: I am French, not EN native speaker, pardon my language if it does not
make sense to you.
In today's CommOps meeting, we revisited an old ticket about planning a
Fedora Docs hack-fest, focusing on getting active, knowledgeable users
across Fedora's user communities to contribute and update content in the
Quick Docs repo (also encouraging people from our user communities to
link and reference the official docs).
Please take a look and weigh in on this Fedora Discourse thread (please
don't reply on the mailing lists because it will inevitably exclude
someone from one sub-project or another):
We learned Fedora Join SIG was talking about similar ideas recently, so
we wanted to prevent duplication of work and see if we can all work
together to make this idea happen.
Justin W. Flory
On 9/28/18 5:19 AM, Harshit Modi wrote:
> Hi CommOps Team,
> I am Harshit Modi. I am interested in getting involved in the Fedora
> community by contributing to the Fedora CommOps. As Fedora CommOps deals
> with all other fedora projects, it will provide me good opportunity to
> work closely with all the community.
Hi Harshit, welcome to the CommOps list! I think CommOps is a good way
to get an early exposure to the wider Fedora community and how it comes
I've also added CC'd the Fedora Join SIG since they are a great resource
for getting started too.
> I am current graduate student at UT Arlington with computer science
> major. I have 2 years of experience in web development. I have proper
> knowledge in web stack and had used many open source technologies. As I
> move forward in my career, I want to dig into more in open source
> projects. And for that I want to join such project and learn from the
> highly motivated community. Fedora is well known in open source world
> and has diverse fields to work with. And CommOps has many active
> contributors and joining them will help me jump on board and become the
> part of fedora community. So I am confident that this opportunity will
> benefit us both.
> Please let me know if you need any additional information. Thanks!
Awesome! I definitely think there are ways for you to jump in and get
started. Are you looking for technical / development opportunities, like
some web development? Or are you looking for non-technical work, maybe
blog posts or helping with things like Fedora Appreciation Week?
If you're not sure, this is a good place to look, to get an idea of what
What can we do to help you get started? :) Hoping to see you around the
Justin W. Flory
I'm at AnsibleFest right now, and contributors to both Fedora and Ansible are discussing linux-system-roles:
It is upstream to to the rhel-system-roles package in RHEL/CentOS & it officially supports Fedora, although it does not seem to be provided as a package in Fedora. (I will be inquiring about this tomorrow.)
The few fellow Fedora contributors I've talked to (including mattdm) like the idea of listing linux-system-roles on fedora-join after a brief high-level discussion. It could be advertised towards anyone who knows how to write Ansible playbooks/roles (no module writing in Python); a very broad skill set nowadays.
What do people here think?
I've just cleared up the message moderation queue. Most of it was spam,
but a few genuine e-mails did get stuck in there too. I've let them
through now, although I think it's too late for us to follow up on them.
To ensure that we don't let this happen again, we need more people
looking at the moderation queue. It only takes 5 minutes a week. I've
filed a ticket here. If you're OK with being a mailing list moderator,
please comment on the ticket to let us know. I'd like to add 2--3 folks.
Ankur Sinha "FranciscoD"
Time zone: Europe/London
I started writing this a while ago and never got it fully formed. Rather than let it keep rotting in my drafts folder I wanted to share it and see if it made sense to anyone else.
Warning - rough edges ahead!
Conversations with several people have resulted in distilling the following idea:
== Changing metadata
Modify the table that drives fedoraproject.org/easyfix that is located at https://fedoraproject.org/wiki/Easyfix
The table would now include two additional columns (optional)
Col 1 = existing reference to the issue tracker. We should consider adding gitlab.com support
Col 2 = existing point of contact
Col 3 = category of task (documentation, infrastructure, programming-Haskell, programming-Ruby, etc.)
Col 4 = SIG/WG/etc. this project is related too (Design, Council, KDE, etc.)
== Changing fedoraproject.org/easyfix
Today we show only two categories: Issues from Pagure/Github and Bugzillas
I believe those categories are not the right categories for consumers of the page. Using the new category (col 3) above, we would break things out by the kind of contribution. This would serve to let people browse related tasks more easily and to reduce the overwhelming nature of the current lists.
For BZs we are either going to have to guess based on BZ metadata or leave them lumped together.
WCDIFF should be extended to show the categories and groups appropriate for the various endpoints. This way the person who navigates WCDIFF has the option of reading a specific task they could work on right now, if they so desire.
The categories give us the opportunity to promote our easyfixes as a great way to join or contribute in a targeted manner. This could come in the form of articles, tweets, or live conference appearances.
What do people think?
Hello Magazine team,
I wrote a draft about the next session on fedora classroom,
sorry for jumping the Pitch process, we need some time for promoting
the event and the magazine post is always our best reference.
Many thanks in advance.
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>