Achieving Fedora Verified: A Community-Informed Guide to Contribution Recognition

Overview

Fedora Verified is a conceptual initiative under discussion by the Fedora Council, designed to formally recognize contributors who have demonstrated sustained, meaningful engagement with the project. The idea emerged from a desire to highlight the diverse ways people support Fedora—not just through code, but through documentation, design, event organization, and community support. A community survey earlier this year gathered 90 responses, revealing strong preferences and tensions that shape how such a program might work. This guide walks you through the proposed process, based on the survey findings, so you can understand what steps you might take to become Fedora Verified and how the community envisions this recognition.

Prerequisites

Before you can pursue Fedora Verified status, you’ll need:

• A Fedora Account System (FAS) account – This is your identity across Fedora infrastructure. Create one at accounts.fedoraproject.org.
• Active contributions – The survey emphasized that all contribution types carry equal weight: code commits, documentation edits, design assets, event planning, and community support. You should have at least a few contributions in any of these areas.
• Understanding of the community’s values – Fedora prides itself on being welcoming to newcomers. The program must keep doors open; 40% of respondents worried that a “Verified” label might intimidate new contributors. Be prepared to help others as you progress.
• A willingness to track your progress – 53% of respondents requested a visual dashboard to show contribution history. While such a tool isn’t yet built, you can maintain a personal log or use Fedora Badges as a proxy.

Step-by-Step Instructions

1. Set Up Your Fedora Account and Profile

Log into accounts.fedoraproject.org and complete your profile. Ensure your name, email, and timezone are accurate. Add a brief bio describing your interests (e.g., “I contribute to documentation and translation”). This profile will be used by the Verified review committee to verify your identity and contributions.

2. Start Contributing in Any Area

The loudest feedback from the survey (66%) was clear: code isn’t everything. Contribute wherever you excel. Below are examples with hypothetical code snippets to illustrate how your contributions might be tracked.

• Code: Submit a patch to a Fedora package via Pagure or GitLab. For instance, you might fix a bug in python-fedora. Your commit message should reference the relevant bug tracker.
• Documentation: Improve Fedora Docs. Create a new page about installing on a Raspberry Pi. Use AsciiDoc syntax:

  === Raspberry Pi Installation Guide
  
  Follow these steps to install Fedora on your Raspberry Pi.
  ...
  

• Design: Submit a wallpaper for the next Fedora release or design a new badge concept. Share your work on the Design Team mailing list.
• Events: Organize a Fedora release party or a local meetup. Announce it on the Community Blog and record attendance.
• Support: Answer questions on Fedora Forum or the mailing list. Log your responses and peer reviews.

Each contribution gets a badge (like the existing Fedora Badges). The survey found 53% want a dashboard to see progress; until then, manually list your badges.

3. Track Your Contributions with a Dashboard

While no official Verified dashboard exists, you can simulate one using the Fedora Badges API. The following Python script fetches your badges and counts them by category:

import requests
import json

username = "your_fas_username"
url = f"https://badges.fedoraproject.org/api/v1/badges?user={username}"
response = requests.get(url)
badges = response.json()

categories = {}
for badge in badges:
    cat = badge.get('category', 'other')
    categories[cat] = categories.get(cat, 0) + 1

print("Your contribution breakdown:")
for cat, count in categories.items():
    print(f"{cat}: {count}")

Run this script regularly to see where you stand. The survey showed 62% of respondents prefer a lightly structured path—this script gives you autonomy.

4. Apply for Verified Status

When you believe you’ve made substantial contributions (the survey didn’t specify a threshold, but think in terms of months of activity), submit an application to the Fedora Council or a designated SIG. Based on the survey tensions:

• 43% want clearly defined milestones – Prepare a list of contributions mapped to proposed milestones (e.g., “10 contributions in documentation”, “organized 2 events”).
• 62% prefer light structure – If you’re part of this group, a simpler narrative of your journey may suffice. Include testimonies from other contributors.

Your application should include:

• A cover letter explaining your commitment to Fedora
• Links to your top 5 contributions
• Your badge dashboard output
• A statement about how you’ve helped newcomers (to address the 40% concern)

5. Maintain Your Status

The survey rejected a strict 12-month expiry (52% said it was too short). The Council may adopt a more flexible renewal period—perhaps 24 months or based on continued activity. To maintain Verified status:

• Stay active in at least one contribution area every 18 months (a compromise suggestion from the data).
• Update your profile and badge dashboard periodically.
• Notify the Council if you take a long break (life gets in the way, as respondents noted).

Common Mistakes

• Focusing only on code: The survey’s top finding—66% demand equal weight for non-code contributions. Don’t neglect documentation, design, or community work.
• Ignoring the newcomer welcome: 40% worried Verified could scare new contributors. If you become Verified, actively mentor newcomers to avoid creating an elite class.
• Assuming 12 months is sufficient: Remember that 52% of respondents thought the original 12-month expiry was too harsh. Build your contribution schedule realistically—quality over volume.
• Neglecting the visual dashboard: 53% want one, so even if unofficial, maintain your own tracker. Don’t rely on memory.
• Choosing extreme structure or no structure: The tension between rigidity and flexibility means the ideal path is balanced. Engage with the community to find a middle ground.

Summary

The Fedora Verified initiative is still in discussion, but the community has spoken clearly: equal recognition for all contribution types, a welcoming environment for newcomers, longer renewal timelines, visible progress tracking, and a careful balance between structure and flexibility. By following this guide—setting up your account, contributing widely, tracking progress, applying with a thoughtful portfolio, and maintaining status thoughtfully—you can position yourself for Verified recognition when the program launches. The Council will continue these conversations at upcoming events like Flock, and your feedback remains vital. Dive in, contribute, and help shape Fedora’s future.