Join Fedora Badges community
Become a member of Fedora Badges community by following these steps.
Log into the Fedora mailing lists site at
using your FAS account credentials. Then, find the
Badges mailing list and subscribe using your personal email address. Do
not use the
@fedoraproject.org alias, as you are unable to send email from
News, updates, and discussion are shared through on the mailing list. It is a key part to how we communicate. It receives low to medium traffic.
Say hello and introduce yourself to the team! Post a self-introduction to the mailing list and tell us a little about yourself.
Not sure what to say? Answer these questions to start:
Why are you interested in contributing to Fedora?
Why are you interested in contributing to Badges?
If you’re involved with other things in Fedora, what are/were you working on?
Do you have any experience in open source or online communities? If so, what?
What parts of the Badges project are interesting to you?
Do you have any questions for us? How can we help you get started?
The Fedora Community Blog is an important place for sharing news in the Fedora community. An account gives permissions to view article drafts and previews before they are published. If you ever write an article, you need an account. To register, log in at the login page with your Fedora Account System (FAS) credentials.
Need more help logging in? Read the help page for more detailed instructions.
Fedora uses the Freenode IRC network and Telegram for instant messaging and communication. You can use the messaging client of your choice, as the IRC channel and Telegram group are bridged together. Short discussions and planning happen in our group chat.
Never used IRC before? See the Beginner’s Guide to IRC on the Fedora Magazine. Additionally, you can connect temporarily in a chat session in your browser via Freenode web chat. However, if you want to stay connected even when you are not online, consider using Riot as your IRC client.
See Make your first steps in Fedora for more info.
There are three ways to contribute to Fedora Badges:
As a designer
As a developer
As a system administrator
Before you begin any of the following tasks, introduce yourself on the mailing list!
The Fedora Badges community accepts requests for new badges in a public issue tracker on pagure.io/fedora-badges. The community opens an issue there when they have a new idea for a badge. To get started with badge design, follow these steps:
Review How to design a Fedora Badge documentation
Set up Inkscape with Badges color palettes, fonts, and templates (provided in documentation)
Review Badge tickets tagged as https://pagure.io/fedora-badges/issues?status=Open&tags=artwork+-+needed[artwork
If nobody is assigned to the issue, leave a comment that you want to work on the Badge artwork
A Badges contributor will reply to confirm the Badge is possible and ready to be worked on (we don’t want you to make a design for a Badge that isn’t technically possible!)
Begin designing the badge, post SVGs/PNGs of your artwork to the issue for review
NOTE: This section is specific to Outreachy Summer 2020 applicants.
You can also contribute code to the Fedora Badges project. There are two git repositories to contribute code:
Tasks, problems, and goals are filed as tickets in the issue trackers. The upstream repository is where we submit patches and improvements to the badgr-server project that Fedora Badges uses. Our forked repository is where we keep track of development tasks and goals specific to the Fedora Badges implementation.
This Outreachy project is different from many other Outreachy projects. The Fedora Badges project involves moving from a legacy framework to a new platform for the Fedora Badges web app. It might sound scary, but there is a team of people ready to help! So, part of the work for development includes research tasks before we begin writing a lot of new code.
Before you write code, you need to set up a development environment and learn about Fedora infrastructure tooling. The Fedora Badges team identified a few "mini projects" for applicants to work on. These help you learn about the tools we will work with and get more experience with other parts of Fedora’s infrastructure. Check out these issues to get started:
NOTE: We advise waiting until Monday, 16 March 2020 to start on code patches! The recommended development environment will have major changes starting that day.
Fedora Badges is partnering with the upstream concentricsky/badgr-server project to submit code and documentation improvements. The Concentric Sky team tagged issues as "help wanted" for where to start with contributing. The Fedora Badges mentor team is also participating there. If you are interested in working on a code patch for concentricsky/badgr-server, comment on the GitHub issue that you would like to work on the task. If someone else has not already started, you can begin working on your pull request.