Fact-checked by Grok 2 weeks ago

Fedora Project

The Fedora Project is a global, community-driven initiative sponsored by that develops and maintains , a and open-source operating system distribution focused on advancing innovative software technologies for desktops, servers, clouds, and containers. Originating in 2003 as a successor to , the project was established to foster rapid open-source development through collaboration between and volunteers worldwide, emphasizing principles and serving as a testing ground for technologies later integrated into . Fedora Linux releases occur approximately every six months, with each version receiving about 13 months of support, and as of November 2025, the latest stable release is 43, which includes editions such as for general desktop use, Server for enterprise workloads, and specialized featuring alternative desktop environments like KDE Plasma, , , and others. The project operates under the governance of the Fedora Council and involves thousands of contributors who adhere to a , with a majority of the codebase maintained by community volunteers rather than corporate employees. Key goals include promoting upstream innovation, ensuring 100% , and providing platforms like Desktops for enhanced , Fedora Labs for curated application bundles, and tools for and cloud deployment.

Overview

Mission and Principles

The Fedora Project's mission is to create an innovative platform for , clouds, and containers that enables software developers and members to build tailored solutions for their users, serving as a testing ground for upstream innovations that benefit the broader ecosystem. This focus positions Fedora as a -driven initiative dedicated to advancing (FOSS) through rapid experimentation and integration of cutting-edge technologies, ensuring that developments flow upstream to influence distributions like and beyond. Guiding this mission are the project's four foundational principles—Freedom, Friends, Features, and First—which shape its ethos and operations. emphasizes dedication to and content, respecting the four essential freedoms: to run, study, redistribute, and modify programs, while avoiding or patent-encumbered components to promote and universal access. Friends fosters a diverse, inclusive where contributors of all skill levels collaborate through consensus, valuing participation from volunteers and emphasizing caring relationships to advance collectively. Features commits to integrating innovative, useful that enhances the platform's capabilities for developers and users alike. First prioritizes leading-edge adoption via a rapid release cycle, delivering the latest stable technologies to demonstrate the future of operating systems and drive forward momentum. These principles profoundly influence project decisions, such as mandating open-source licensing for all included software to uphold , and relying on community-driven processes for and development to embody and Features. For instance, Fedora's policy against non-free components ensures ideological purity, while its semi-annual releases exemplify First by testing innovations like SELinux early on. Red Hat's sponsorship supports these without compromising openness, providing resources while adhering to the principles. From its inception in , the Fedora Project has embodied these principles, evolving from a community effort to package additional software for into a structured initiative that prioritizes and innovation as core tenets. This foundational adoption has sustained Fedora's role as an upstream innovator, with Freedom and Friends enabling broad participation, and Features and First ensuring it remains a vanguard for advancements.

Sponsorship and Relationship with Red Hat

The Fedora Project has been primarily sponsored by , Inc. since its inception in 2003, when Red Hat announced the first release of Fedora Core 1 as a community-driven successor to . As the main sponsor, supplies essential resources including full-time employee developers, infrastructure such as servers and bandwidth, hardware, event funding, and legal counsel, enabling the project's operations without exerting direct control over its direction or decisions. This sponsorship model supports Fedora's open-source ethos while allowing to contribute significantly through its engineering teams. Fedora functions as an upstream development platform for Red Hat Enterprise Linux (RHEL), where new technologies and features are prototyped, tested, and refined in Fedora's biannual releases before being stabilized and incorporated into RHEL's longer support cycles. Red Hat engineers participate in Fedora as individual community members, often leading key areas such as the GNOME desktop environment, Linux kernel development, and Xorg graphics server, with several hundred active contributors from the company blending seamlessly with volunteers. Governance mechanisms further integrate this collaboration; the Fedora Council, the project's top-level body, includes Red Hat-appointed roles like the Fedora Project Leader, Community Architect, and Operations Architect, alongside community-elected representatives, ensuring decisions are made via consensus to maintain balanced input. This partnership yields mutual benefits for , serving as an innovation pipeline where community-tested advancements—such as of emerging software—feed into , while also facilitating talent recruitment by showcasing contributor skills through the project's open contributions, with over 24,000 individuals having signed the . Fedora's independence is preserved through its open governance structure, where approximately 65% of the codebase is maintained by non-Red Hat volunteers, and no single entity holds veto power, aligning the sponsorship with the project's commitment to community-led .

History

Origins from Red Hat Linux

Red Hat Linux, launched in 1994, served as a pioneering commercial Linux distribution developed and distributed by Red Hat, Inc., which was formally established in 1995. Initially sold as boxed software products through retail channels, it evolved into a semi-annual release cycle by the early 2000s, incorporating open-source components while relying on sales and limited support subscriptions for revenue. However, this model faced sustainability challenges, as the growing popularity of free Linux alternatives eroded retail sales, and the inclusion of some proprietary elements, such as bundled commercial software like StarOffice in early versions, clashed with increasing community demands for fully open-source distributions without commercial encumbrances. By 2003, Red Hat recognized that maintaining a community edition under a commercial umbrella was no longer viable, prompting a strategic pivot to focus on enterprise sustainability while fostering a separate, purely community-driven effort. In a pivotal decision announced on September 22, 2003, separated its community development from enterprise products, merging the project with the pre-existing project—a community initiative started by Warren Togami to provide third-party packages for . This merger birthed the Fedora Project, positioned as a free, open-source alternative to the newly formed (RHEL), which targeted corporate customers with long-term support subscriptions. The split addressed community calls for greater independence, ensuring Fedora operated as a volunteer-led effort sponsored by but not controlled by it, thereby promoting rapid innovation without commercial constraints. Sponsored by to enable this division, the project emphasized transparency and openness from inception. Initially named Fedora Core to denote its foundational distribution role, the project was led by early figures such as Michael K. Johnson as the first project leader, with contributors like Bill Nottingham playing key roles in packaging and release management. Complementing this, the project formed in 2003 as a community effort to provide ongoing security updates and bug fixes for older versions (such as 7.3, 8.0, and 9) and early Fedora releases, extending their usability beyond official end-of-life. This initiative, supported by volunteer developers and some resources, ensured continuity for users reliant on systems during the transition. Key events underscored the project's launch, including the September 2003 merger announcement, the release of Fedora Core Test 1 on July 21, 2003, Test 2 on September 25, 2003, Test 3 on October 13, 2003, with the stable Fedora Core 1 arriving on November 6, 2003. These early alphas and the final release emphasized as the default , adopting a familiar panel layout from to ease adoption for existing users.

Formation and Early Releases

The Fedora Project was officially launched by Red Hat on November 6, 2003, as a community-led initiative to develop a free and open-source Linux distribution, building directly on the foundations of Red Hat Linux by separating community development from commercial products. Fedora Core 1, codenamed Yarrow, marked the project's first major release, featuring the Linux kernel version 2.4.22 with Native POSIX Thread Library (NPTL) support for improved threading performance and XFree86 4.3 as the graphics subsystem. This version utilized the Anaconda installer for system setup, supporting graphical installations over FTP, HTTP, or VNC, while transitioning from proprietary Red Hat tools to community-maintained components like the yum package manager, which provided automatic dependency resolution for RPM packages and began replacing the older up2date system. Subsequent releases established a roughly six-month development cadence to deliver timely updates. Fedora Core 2, codenamed , arrived on May 18, 2004, introducing the 2.6 for better support and initial SELinux integration in targeted mode to enhance mandatory access controls without disrupting standard workflows. Fedora Core 3, codenamed , followed on November 8, 2004, with deeper SELinux refinements, including a targeted policy covering about 10 key domains and an unconfined_t domain for less restrictive processes, alongside 2.8 for improved desktop usability. In its formative years, the project faced challenges such as standardizing artwork to foster a unique visual identity distinct from Red Hat's branding, leading to iterative redesigns of themes like Bluecurve. By Fedora 7, codenamed and released on May 31, 2007, the branding evolved further by dropping the "Core" suffix and merging the Core and Extras repositories into a unified Fedora package set to streamline contributions.

Major Milestones and Transitions

Fedora 11, released in June 2009 and codenamed Leonidas, introduced performance enhancements such as the default adoption of the filesystem, which provided improved speed and reliability compared to , contributing to overall system efficiency including reduced boot times in many configurations. The release also featured the Fedora Unified Installer, enabling faster installations from live media. Fedora 13, codenamed Goddard and released in May 2010, advanced user accessibility with the introduction of automatic language pack installation via the yum-langpacks plugin, allowing the system to detect and install localization resources based on user settings during setup or updates. This feature streamlined multilingual support, making Fedora more approachable for global users without manual intervention. In late 2010, Fedora 14 (Laughlin) emphasized customization through an expanded focus on —pre-configured variants tailored to specific desktop environments like and —building on earlier introductions to offer diverse user experiences while maintaining a semi-annual release cadence established since 2007. These , such as the and editions, provided optimized environments for different workflows, enhancing the project's appeal to varied communities. A pivotal strategic shift occurred in with the Fedora.next initiative, which restructured the project around modular products including , , and editions, enabling more flexible and targeted releases starting with Fedora 21 in December . This model promoted modularity by separating base systems from application stacks, fostering innovation in areas like and cloud deployment while aligning with Fedora's open-source principles. In 2023, with the release of Fedora 39, the project rebranded the distribution to "" to emphasize its identity as a operating system. The project evolved with the introduction of immutable operating system designs, such as in 2018 with Fedora 28, an atomic variant that treats the base OS as read-only and uses rpm-ostree for layered updates, improving reliability and rollback capabilities for desktop users. By 2023, these immutable variants saw increased adoption as part of broader trends toward image-based distributions, positioning Silverblue as a stable alternative to traditional mutable setups. As of 2024, Fedora 41 highlighted advancements in artificial intelligence tooling by integrating updated libraries like PyTorch 2.4 and ROCm 6.2, facilitating easier development and execution of AI workloads with GPU acceleration support. These enhancements built on prior math library updates, enabling seamless integration for machine learning applications within the Fedora ecosystem. In 2025, Fedora 42 enhanced Wayland protocol support, including improvements to accessibility features like Orca screen reader compatibility and input-method protocol version 2 for better text handling in compositors such as Sway and Hyprland, alongside a native Wayland-based Anaconda installer. These updates solidified Wayland as the default display server, reducing reliance on X11 and improving security and performance for modern desktops.

Security Incidents and Responses

In August 2008, the Fedora Project experienced a significant security breach when its Koji build system was compromised, allowing an attacker to insert a backdoor into the packages distributed for Fedora 8 and 9. The intrusion was discovered through a code audit that revealed remote vulnerabilities enabling over the host system without modifying the dom0 . This affected users who installed the tainted Xen RPMs, prompting the project to revoke the compromised builds and advise users to rebuild or reinstall the from trusted sources. A subsequent supply chain compromise occurred in 2011, involving the unauthorized access to a Fedora packager's account, which led to the signing of malicious packages using a compromised GPG key. This incident raised concerns about the integrity of package signatures and mirrors, resulting in the temporary revocation of the affected key and a review of authentication processes to restore trust in the distribution chain. Although no widespread exploitation was reported, it highlighted vulnerabilities in contributor access controls. In response to these events, the Fedora Project formalized the Fedora Security Team in 2009 to coordinate vulnerability responses and infrastructure security. Key enhancements included making SELinux enforcement mandatory by default across installations, providing mandatory access control to limit potential damage from exploits. Additionally, Fedora 18 in 2013 adopted support, integrating UEFI verification to prevent unauthorized bootloaders and kernels from loading. Ongoing security practices emphasize rapid errata releases for vulnerabilities, often within hours or days of disclosure, and encourage community-driven audits through special interest groups. These measures, integrated with broader for incident handling, have contributed to no major compromises reported in the project since 2015 as of 2025.

Governance and Community

Organizational Structure

The Fedora Council serves as the top-level governance and leadership body for the Fedora Project, responsible for stewarding the overall direction, setting strategic goals, managing trademarks, arbitrating disputes, and overseeing community health and finances. Composed of appointed and elected members—including two annually elected community representatives, Red Hat-appointed roles such as the Fedora Project Leader, Community Architect, and Operations Architect, as well as representatives from engineering, mindshare, , and community initiatives—the Council operates on a process, utilizing "lazy approval" for routine matters and full (requiring +3 votes with no vetoes) for major decisions, with the Fedora Project Leader resolving deadlocks. This structure evolved from earlier models to emphasize community involvement while maintaining accountability to both the community and sponsors. The Engineering Steering (FESCo) provides technical oversight, managing engineering initiatives, approving features and change proposals, coordinating resources, and establishing development schedules for software offerings and . Fully elected by the community, FESCo consists of nine members, including designates from working groups like , , and , with elections held twice yearly and decisions made via ticket-based voting requiring three +1 approvals without vetoes. It empowers subcommittees, such as the , to maintain policies like the Guidelines, which ensure consistent, high-quality software across the project by covering aspects like naming, versioning, licensing, and spec file standards. FESCo also handles trademark-related technical policies in coordination with the . Voting membership in the Fedora Project is granted through the (FAS), requiring contributors to sign the Fedora Project Contributor Agreement (FPCA) for CLA_done status and demonstrate proven contributions via membership in at least one additional FAS group (achieving CLA+1 status), which enables participation in elections for bodies like the and FESCo. This system ensures that only active contributors with verified involvement—such as , , or work—hold voting rights, populating structures through community elections using range voting methods. Key policies underpin these bodies, including the Fedora Code of Conduct, which promotes an inclusive environment by outlining expected behaviors and prohibiting harassment based on diverse characteristics like background, identity, or experience, with enforcement delegated to a dedicated comprising the Fedora Project Leader, Community Architect, and community members. The Council oversees its implementation to foster community health.

Community Participation and Roles

The Fedora Project fosters a vibrant, global community where individuals contribute through diverse roles tailored to various skills and interests. Packagers play a central role by creating and maintaining RPM packages, adhering to strict guidelines set by the Fedora Engineering Steering Committee to ensure software quality and compliance across the distribution. Ambassadors focus on local , organizing events, demonstrating Fedora at public gatherings, and promoting the project's principles to grow the contributor base and enhance public understanding. Testers contribute by participating in dedicated Test Days, where they evaluate upcoming features, report bugs, and collaborate with developers in real-time to verify release quality. To support newcomers, the project offers structured programs for onboarding and skill development. The Fedora Classroom provides interactive sessions on topics like packaging, localization, and documentation, helping participants learn and engage with the community effectively. Mentorship programs, including participation in Outreachy since around 2014, pair mentees from underrepresented groups with experienced contributors to promote diversity and guide initial contributions in areas such as coding and community building. The Fedora community spans the globe and relies on collaborative tools for coordination, with a strategic goal to double its contributor base by 2028. Communication occurs via mailing lists for asynchronous discussions, IRC channels like #fedora-ambassadors for real-time support, and Pagure as the primary platform for issue tracking, git repositories, and project collaboration. Contributions are recognized through the Fedora Account System (FAS), which awards badges for achievements like adding SSH keys or joining groups, gamifying participation and highlighting progress. Dedicated contributors may also advance to leadership positions via community elections, overseen by bodies like the Project Board.

Fedora Linux Distribution

Core Features and Architecture

Fedora Linux utilizes the as its foundational system for software distribution and management, which ensures package integrity verification, dependency resolution, and support for upgrades or downgrades. Built atop RPM, DNF serves as the default frontend, enabling users to query package information, install or remove software groups, and handle modular repositories that allow for multiple versions of applications and runtimes to coexist without conflicts. This modular approach, integrated into DNF, facilitates flexible software streams, such as different or versions, enhancing compatibility for developers and users. The distribution employs the latest stable upstream releases, typically updating to new major versions shortly after their upstream availability and incorporating weekly stable patches to maintain and . While Fedora minimizes custom modifications to align closely with upstream , it applies targeted patches through its git-based , particularly for enablement where out-of-tree drivers are included only if upstream integration is not feasible, such as for specific networking or storage support. This strategy ensures broad compatibility while prioritizing upstream contributions for long-term sustainability. Fedora Workstation defaults to the desktop environment, providing a modern, intuitive interface optimized for productivity with features like support and integrated system settings. It emphasizes for deploying sandboxed applications, which GNOME Software uses to install secure, distribution-agnostic apps from sources like Flathub, isolating them from the host system to mitigate security risks. For multimedia, has been the default framework since Fedora 34, offering low-latency audio and video processing that unifies professional and consumer use cases while supporting sandboxed environments like . Guiding these components is Fedora's upstream-first architectural principle, which mandates that improvements and fixes be contributed back to original projects before integration, reducing downstream maintenance and benefiting the wider open-source community. Additionally, Fedora supports natively through Podman, a daemonless, rootless tool compatible with images that enables secure pod-based deployments for applications and services without requiring elevated privileges.

Release Process and Versions

The Fedora Project maintains a predictable six-month release cycle for , with new versions targeted for the fourth Tuesday in April and October to ensure regular updates and community alignment. This cycle begins with ongoing development in the Rawhide branch, a rolling that serves as the primary testing ground for upcoming features and packages without direct user-facing releases. Approximately ten weeks before the final release, the codebase branches from Rawhide for stabilization, followed by phases that allow extensive community testing to identify and resolve issues. These releases occur around 14:00 UTC, providing a public milestone before the general availability (GA) final release, with freezes imposed prior to both and final stages to lock in changes and conduct final validations. Central to the process are quality gates enforced through tools like Greenwave, which verify that packages meet criteria such as successful builds and tests before promotion. Koji, Fedora's distributed RPM build system, handles package compilation in isolated chroot environments across multiple architectures, enabling mass rebuilds of RPMs and modules post-branching to ensure compatibility. Bodhi, a web-based update management system, facilitates the submission, testing, and promotion of package updates during the beta and post-release phases, using a karma-based feedback mechanism where community testing (e.g., +3 for stable, -3 for issues) determines advancement from testing to stable repositories. Updates are pushed to testing repositories on Tuesdays at 03:00 UTC in batches, with daily stable pushes, ensuring rigorous validation before integration into the core architecture that underpins each version. Each Fedora Linux version receives approximately 13 months of support, during which security fixes, bug resolutions, and critical updates are provided via Bodhi-managed repositories. The N-2 release reaches end-of-life (EOL) four weeks after the release of version N, after which it is archived and no longer receives updates, prompting users to upgrade. For instance, Fedora Linux 41 is scheduled to reach EOL on November 25, 2025, four weeks after the release of Fedora Linux 43. Versions are numbered sequentially, starting from Fedora Linux 1, with Fedora Linux 43 released on October 28, 2025, as the latest major version as of November 2025. Historically, prior to Fedora Linux 21, releases featured thematic code names drawn from cities, landmarks, or cultural references, selected through votes to foster engagement, such as Fedora 20 ("") or Fedora 19 (""). Since Fedora Linux 21, the convention has shifted to primary numerical designation for simplicity, though occasional special names are used, like Fedora Linux 42 ("") honoring Douglas Adams.

Special Interest Groups and Sub-Projects

Software and Design SIGs

The Special Interest Group (SIG) within the Fedora Project is responsible for overseeing the creation and maintenance of official community , which are customized variants of designed to cater to diverse user preferences through alternative desktop environments and tailored software selections. These build upon the core distribution by incorporating specific desktop environments such as , , and , along with bespoke artwork, configurations, and pre-installed applications that enhance usability for targeted audiences. The SIG ensures that all adhere to Fedora's technical standards, including compatibility with the base system's package management and security features, while allowing flexibility in and workflow customizations to promote broader adoption. The Fedora Design Team SIG serves as the project's dedicated design unit, focusing on the creation and refinement of visual and experiential elements that define 's identity across releases. Established to provide comprehensive services, the develops themes, icons, and usability guidelines that influence the overall aesthetic and interaction patterns in Fedora spins and editions. For instance, they contribute to icon sets and themes like variants of , the default toolkit theme adapted for Fedora's branding, ensuring consistency in visual while supporting free and open-source creative tools. Their work extends to producing release-specific wallpapers through tools like Nuancier and designing contributor badges, all aimed at enhancing and project cohesion. Complementing these efforts, the Atomic Desktops SIG manages experimental and innovative editions of , emphasizing immutable system designs for greater reliability and container-based workflows. This group maintains variants such as , an immutable based on environment that uses rpm-ostree for updates to minimize system breakage, and , its Plasma counterpart offering similar immutability with a focus on traditional . These editions represent forward-looking explorations in architecture, allowing users to layer applications via tools like and while keeping the base system read-only. To establish and sustain these SIGs, Fedora employs a streamlined proposal process that encourages involvement while maintaining alignment with principles. Interested contributors gauge interest via mailing lists, create a dedicated wiki page outlining the SIG's mission, and request resources if needed, with minimal formal . For specifically, proposals undergo technical review by the Spins SIG to verify adherence to best practices, followed by Fedora Board approval for usage, ensuring all variants remain compatible with core Fedora repositories and philosophies without diverging into unsupported territories. This process fosters ongoing maintenance through regular meetings and infrastructure support, enabling SIGs to evolve and designs in tandem with Fedora's biannual release cycle.

Infrastructure and Documentation Efforts

The Fedora Infrastructure team, composed of volunteers and professionals, is responsible for maintaining the servers, services, and tools essential to the project's operations, including the management of key websites such as getfedora.org, global mirror networks for distribution downloads, and / (CI/CD) pipelines that automate building and testing of software packages. This team ensures and across globally distributed systems, supporting the development and distribution of by handling daily operations like content hosting and system issue resolution. Their efforts are coordinated through weekly meetings and communication channels like rooms and mailing lists, with oversight from the Fedora Project Council for policy decisions. Historically, the infrastructure has utilized CentOS images for virtual machine hosting within its private cloud environment, which supports various community projects including build systems and testing frameworks, although current operations increasingly rely on cloud providers like Amazon for scalability. The team also manages critical services mapped in official documentation, ensuring seamless collaboration for developers and users worldwide. The Documentation (Docs Project) focuses on creating and maintaining comprehensive, open-source guides to enhance user and contributor experiences, producing official resources such as installation manuals, user handbooks, and release notes that detail changes, upgrades, and best practices for each Fedora version. These documents are developed using , a for structured documentation, enabling reusable and modifiable outputs under the Attribution-Share Alike license. The project operates through collaborative workflows, including weekly meetings and issue tracking on Pagure, with content hosted on the dedicated Fedora Docs site at docs.fedoraproject.org. As of 2025, the project is migrating from Pagure to for enhanced collaboration and . Complementing these efforts, the Fedora Localization Team (L10N), often functioning as a , coordinates the of software interfaces, , websites, and content to make Fedora accessible globally, supporting localization in over 100 languages through community-driven contributions. Translators use Weblate, a web-based platform integrated with , to propagate changes and maintain consistency across projects, fostering cultural adaptation and inclusivity. This work extends to the Fedora Project at wiki.fedoraproject.org, a MediaWiki-powered site that enables collaborative editing of policies, guides, and community resources by verified contributors.

Enterprise and Security Sub-Projects

The Extra Packages for Enterprise Linux (EPEL) is a (SIG) that delivers high-quality, additional packages in RPM format for (RHEL) and compatible distributions like , focusing on packages not included in the official RHEL repositories. Established in the mid-2000s to leverage 's build infrastructure for enterprise needs, EPEL maintains separate stable branches for production use—limited to bug fixes and security updates—and testing branches for evaluating new packages before promotion, ensuring no interference with base system stability. EPEL's policies emphasize compatibility with RHEL's lifecycle, prohibiting rebuilds that alter ABI or functionality, which supports 's position as the upstream development platform for RHEL. The Security Lab is a dedicated of Fedora that creates a controlled live for professionals, educators, and researchers to perform auditing, forensics, testing, and tasks without risking host systems. It features a lightweight desktop with pre-installed tools tailored for workflows, including for developing and executing exploits, for packet capture and network analysis, and other utilities like for scanning, all configured for read-write persistence during live sessions. This highlights Fedora's commitment to robust tooling, drawing from upstream Fedora packages to provide an accessible platform for ethical and training. Additional enterprise-oriented efforts include FreeIPA integration, which embeds the FreeIPA identity management system into for centralized user authentication, authorization, policy enforcement, and certificate management across Linux environments using components like , MIT , and SSSD. The Container Tools SIG advances containerization by guiding the creation, maintenance, and distribution of OCI-compliant images, promoting tools such as Podman for rootless container building and orchestration without a daemon, facilitating secure and deployment. These initiatives, including EPEL's compatibility safeguards, enable sub-projects to serve as upstream sources for RHEL, with utilizing them to extend enterprise capabilities while preserving stability.

References

  1. [1]
    The Fedora Project: Open source evolved - Red Hat
    Red Hat is the primary corporate sponsor for the Fedora Project and a major contributor. There are more than 24,000 Fedora Account System members who have ...
  2. [2]
    Fedora Linux | The Fedora Project
    An innovative platform for hardware, clouds, and containers, built with love by you. 100% Free & Open SourceDownload Fedora Workstation · KDE Plasma · Download Fedora Server 43 · Kinoite
  3. [3]
    History of Red Hat Linux - Fedora Project Wiki
    This document describes that history, particularly focusing on the development themes for each release of Linux provided by Red Hat.
  4. [4]
    Fedora Linux Releases
    Fedora releases two major OS releases yearly, around April and October, with 13 months of support. Development includes Rawhide and Branched.Fedora Linux 42 · Fedora Linux 40 · Fedora Linux 38 · Fedora Linux 41
  5. [5]
    Download Fedora Workstation 43
    Oct 28, 2025 · Getting started with Fedora Linux is easier than ever. All you need is a 4GB USB flash drive and the Fedora Media Writer utility. After Fedora ...
  6. [6]
    Fedora's Mission and Foundations
    The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities. As a ...Fedora Leadership · Fedora Brand Guidelines · Get Involved · Getting Help
  7. [7]
    Fedora Origins - Part 01
    Apr 15, 2020 · The Four Foundations of Fedora, Freedom, Features, First & Friends were lived and breathed and not just a catchy line on a website or a leaflet.
  8. [8]
    Celebrate Fifteen Years of Fedora
    Nov 6, 2018 · On November 6, 2003, Red Hat announced Fedora Core 1, the first software release of the Fedora Project. This announcement marked the ...
  9. [9]
    Fedora Sponsors
    Red Hat, Inc. is the primary sponsor for the Fedora Project. Red Hat provides the Fedora Project with a wide variety of resources, including full-time ...
  10. [10]
    Fedora and Red Hat Enterprise Linux
    Fedora is developed by the Fedora Project and sponsored by Red Hat. It follows its own release schedule, with a new version approximately every six months.
  11. [11]
    Red Hat contributions - Fedora Project Wiki
    Red Hat is the primary sponsor of Fedora Project and provides hosting, engineering and other resources. It has several hundred active developers participating.
  12. [12]
    Fedora Council Charter
    The Fedora Council is composed of a mix of representatives from different areas of the project, named roles appointed by Red Hat, and a variable number of ...
  13. [13]
    Our history - Red Hat brand standards
    Red Hat Enterprise Linux became the company's flagship product, an offering to the world's most demanding datacenters. A freely available, community version of ...Missing: commercial sustainability 2003 elements
  14. [14]
    LWN.net Weekly Edition for September 25, 2003
    But the idea the company is trying to get across is clear: Fedora, as a project, is separate from Red Hat and its products. The degree to which that is true, ...
  15. [15]
    10 Years Ago: The Fedora Project was Announced
    Sep 22, 2013 · The Fedora Linux Project was a project started by Warren Togami to create 3rd party packages for Red Hat Linux until it merged with the Red Hat ...
  16. [16]
    10 Years of Round Cows and Meat-Based Miracles: The Fedora ...
    Nov 6, 2013 · On November 6, 2003, however, the Fedora Project became much more with the launch of Fedora Core 1, a full-fledged Linux distribution and the ...<|control11|><|separator|>
  17. [17]
    Archive:Legacy - Fedora Project Wiki
    The Fedora Legacy Project is a community-supported open source project to extend the lifecycle of select 'maintenance mode' Fedora Core distributions.Missing: 2003 Bill Nottingham
  18. [18]
    Releases/HistoricalSchedules - Fedora Project Wiki
    Fedora Core 1 (Codename: Yarrow). November 5th 2003 - Fedora Core 1 General Availability (Yarrow); October 13th 2003 - Fedora Core 1 Test 3 (0.95) ...
  19. [19]
    Fedora Core 1 Release Notes
    ### Extracted Information
  20. [20]
    SELinux/Policies - Fedora Project Wiki
    In Fedora Core 3 we targeted about 10 domains for lock down and came up with a new domain called unconfined_t . Processes within the domain of unconfined_t ...
  21. [21]
    Design/Release Artwork Process - Fedora Project Wiki
    Release artwork is that part of Fedora artwork that changes with each new release. The most notable part is the wallpaper, but it also contains various banners.Missing: years | Show results with:years
  22. [22]
    F13 Alpha release announcement - Fedora Project Wiki
    The Fedora 13 "Goddard" Alpha release is available! What's next for the free operating system that shows off the best new technology of tomorrow?
  23. [23]
    Releases/14/Spins - Fedora Project Wiki
    QA Test Day Spin, The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days ...Missing: Laughlin yearly cycle
  24. [24]
    Fedora.next - Fedora Project Wiki
    Fedora.next is an umbrella phrase for the planning for the second decade of the Fedora Project. Contents
  25. [25]
    Immutable variants are the majority of Fedora Linux in use
    Mar 20, 2023 · Distributions like Fedora's Silverblue have been exploring the immutable space as well. ... 2023: Fedora Discussion Year in Review · Software ...<|separator|>
  26. [26]
    Releases/41/ChangeSet - Fedora Project Wiki
    Builds on the math libraries released in F40 to also include packages to run AI workloads. Has been integrated with Fedora's PyTorch. Owner: Jeremy Newton; Last ...Fedora Linux 41 Accepted... · acpica-tools: Remove Big... · Upgrade systems to...
  27. [27]
    What's New in Fedora Workstation 42
    Apr 15, 2025 · Wayland Accessibility Improvements ... Orca screen reader capabilities are now available on Wayland. The Orca shortcuts now function correctly.
  28. [28]
    Fedora, Red Hat, and distributor security - LWN.net
    Aug 25, 2008 · On August 22, the Fedora Project released an "infrastructure report" confirming what most observers had, by then, suspected: the project had ...
  29. [29]
    [PDF] Subverting the Xen hypervisor - Black Hat
    Aug 7, 2008 · An attacker can gain backdoor control over the host by overwriting Xen code and data structures; as not a single byte in dom0 domain is modified ...Missing: incident | Show results with:incident
  30. [30]
    Fedora Project Investigates Possible Infrastructure Compromise
    Jan 25, 2011 · “A security incident on Fedora infrastructure has been reported by Jared Smith, Fedora Project's leader, who confirmed that the account of ...
  31. [31]
    SIGs/Security - Fedora Project Wiki
    With the Security SIG as core element, it replaces the former Security Team along with other SIGs and Teams. The Security SIG complements but does not yet ...
  32. [32]
    Getting started with SELinux - Fedora Docs
    In permissive mode, the system acts as if SELinux is enforcing the loaded security policy, including labeling objects and emitting access denial entries in the ...Introduction to SELinux · Benefits of running SELinux · SELinux examples
  33. [33]
    Features/SecureBoot - Fedora Project Wiki
    Jan 10, 2013 · "Secure Boot" describes a UEFI feature by which malware is prevented from inserting itself into the boot process before the operating system loads.
  34. [34]
    Security Features Matrix - Fedora Project Wiki
    It has been there since Kernel 2.6.19. It works at filesystem-level, so this type of encryption can be applied to specific folders/directories as needed after ...
  35. [35]
    Security Bugs - Fedora Project Wiki
    Security bugs, in Fedora, generally come from one of two places: people finding them and opening a ticket in Red Hat's Bugzilla instance or Red Hat's Product ...
  36. [36]
    Fedora Council and Board Historical Membership
    The Fedora Board was the Project's top-level governance body from July 2007 to November 2014. Before that, the "Fedora Advisory Board" was merely (as the name ...
  37. [37]
    Fedora Engineering Steering Committee
    ### Summary of FESCo
  38. [38]
    Fedora Packaging Guidelines
    Fedora packaging guidelines cover naming, versioning, licensing, spec files, and more. They are a collection of common issues, not to be blindly followed.What can be packaged · R Packaging Guidelines · Ruby Packaging Guidelines
  39. [39]
    Groups in Fedora
    Contents. What are the different types of groups? How to request a group to be created? COPR groups; "pkgdb" groups name ...
  40. [40]
    Elections Guide - Fedora Docs
    Voting Eligibility. Eligible voters are determined by their Fedora Account System (FAS) membership. To vote for the Fedora Council you ...
  41. [41]
    Code of Conduct - Fedora Docs
    The Fedora Code of Conduct is a set of guidelines that explains how our community behaves and what we value to members and outsiders.Missing: adoption | Show results with:adoption
  42. [42]
    Fedora Code of Conduct Committee
    The Code of Conduct Committee consists of the Fedora Project Leader, the Fedora Community Architect, and Fedora community members.Missing: 2018 | Show results with:2018
  43. [43]
    Fedora Package Maintainers
    The Packaging Committee handles the rules and Packaging Guidelines for writing SPEC files for software in Fedora.
  44. [44]
    Ambassadors - Fedora Project Wiki
    Fedora Ambassadors are representatives who ensure public understanding of Fedora, grow the contributor base, organize events, and promote Fedora.Contributing roles in the... · Joining the Fedora...
  45. [45]
    QA/Test Days - Fedora Project Wiki
    Test Days are often focused on testing Changes planned for an upcoming Fedora release, but they also regularly test important areas of the Fedora distribution.
  46. [46]
    Fedora Classroom
    The Fedora Classroom is a project to help people spread knowledge to others. We host a plethora of sessions on different subjects.Missing: onboarding | Show results with:onboarding
  47. [47]
    Mentored Project - Fedora Docs
    Fedora's mentored projects include roles like Intern and Mentor, and programs like Google Summer of Code and Outreachy. Projects must be related to Fedora.
  48. [48]
    Communication in Fedora
    The most significant mailing lists are: announce · devel · devel-announce · test. For a catalog of all the mailing lists look at lists.fedoraproject.org.
  49. [49]
    Fedora Badges
    Fedora Badges is a fun website built to recognize contributors to the Fedora Project, help new and existing Fedora contributors find different ways to get ...
  50. [50]
    Fedora Join Special Interest Group
    ### Summary of Fedora Join Special Interest Group Content
  51. [51]
    Package management system - Fedora Docs
    This system is based on rpm , the RPM Package Manager, with several higher level tools built on top of it, most notably PackageKit (default gui) and DNF.
  52. [52]
    Using modules in Fedora
    This is a quick overview how to use modules and module streams with the package manager DNF. ... Installing a RPM package from a wrong module stream.
  53. [53]
    Fedora Linux Kernel Overview
    The Fedora Linux kernel closely follows the upstream kernel releases. To see the current versions in Fedora, check out the packages application.
  54. [54]
    Kernel - Fedora Project Wiki
    The Fedora kernel uses the latest released kernel, rebaser, and is maintained via a git tree. It's maintained on the 'os-build' branch, synced with Linus ...Missing: choices | Show results with:choices
  55. [55]
    Fedora Workstation Documentation
    These pages are a general guide to Fedora Workstation. They provide an overview of Workstation, and are intended for Workstation users and Fedora contributors.Software Repositories & Tools · Downloading · Disk ConfigurationMissing: features | Show results with:features
  56. [56]
    Software Repositories & Tools - Fedora Docs
    Fedora Workstation uses default repositories (RPM, Flatpaks) and third-party repositories. Tools include the GNOME Software app, dnf, flatpak, and fwupdmgr.Disk Configuration · Using the DNF software... · Third-Party Repositories
  57. [57]
    Changes/DefaultPipeWire - Fedora Project Wiki
    Feb 17, 2021 · PipeWire is designed to be multiprocess. It separates the processing of the multimedia graph and the management into separate processes. This ...
  58. [58]
    Upstream First: A Core Fedora Principle
    Apr 2, 2025 · "Upstream first" means sharing software improvements with the original source project, the "upstream" project, to benefit all users, not just  ...
  59. [59]
    Containerization - Fedora Docs
    Nov 5, 2022 · Podman is natively supported by Fedora Server and the recommended solution for application containers. Docker. Its characteristics are.
  60. [60]
    Fedora Linux Release Life Cycle
    Historically, the Fedora Project has found that supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load. End of Life ...
  61. [61]
    Release process - Fedora Docs
    Release process · Rawhide starts Fedora Linux 43 development · Mass Rebuild: RPMs first, then modules · Branch Fedora Linux 43 from Rawhide · Rawhide starts Fedora ...
  62. [62]
    Using the Koji build system - Fedora Docs
    The Koji Build System is Fedora's RPM buildsystem. Packagers use the koji client to request package builds and get information about the buildsystem.Using Koji in Fedora · Building with fedpkg targets · Scratch Builds · Build Failures
  63. [63]
    Bodhi - Fedora Project Wiki
    Bodhi is a modular web-based system that facilitates the process of publishing package updates for Fedora.What is Bodhi · Workflow · Karma · How to help test important...
  64. [64]
    Fedora Linux | endoflife.date
    Oct 28, 2025 · Fedora has a relatively short life cycle: Release X is supported until 4 weeks after the release of Release X+2 and with approximately 6 ...Missing: spins | Show results with:spins<|separator|>
  65. [65]
    Fedora Linux 43 is here!
    Oct 28, 2025 · I'm excited to announce my very first Fedora Linux release as the new Fedora Project Leader. Fedora Linux 43 is here! 43 releases!
  66. [66]
    Release Name History - Fedora Docs
    Fedora Linux 7 (Moonshine). Moonshine is an independent record label, and also the name of a movie. http://en.wikipedia.org ...
  67. [67]
    SpinSIG - Fedora Project Wiki
    The purpose of the Spin SIG is oversee the development of an evolving set of technical best practises to be applied to all community spin concepts. The Spin SIG ...
  68. [68]
    Spins - Fedora Docs
    Spins are alternate versions of Fedora Linux, tailored for various types of users via hand-picked application sets and other customizations.
  69. [69]
    Fedora Spins | The Fedora Project
    Alternative desktops for Fedora. Find a Fedora Spin to enhance your experience! You can find the latest versions of our spins here. Latest release.Fedora Xfce · Fedora COSMIC Spin · Fedora Sway Spin · Fedora i3 Spin
  70. [70]
    Design - Fedora Project Wiki
    The Fedora Design Team is Fedora's in-house design agency. We provide artwork, user experience, usability, and general design services to the Fedora project.
  71. [71]
    https://fedoraproject.org/wiki/Design
  72. [72]
    Fedora Silverblue | The Fedora Project
    Fedora Kinoite is an atomic KDE Plasma-based desktop. Sway Atomic. Fedora ... The Labs are Fedora Linux set up with software bundles based on particular topics.
  73. [73]
    Creating a Fedora SIG - Fedora Project Wiki
    SIGs (Special Interest Groups) are basic building blocks of the social structure of Fedora. They're very informal with an incredibly low bar to creation.
  74. [74]
    Fedora Infrastructure and Release Engineering
    All Fedora Documentation content available under CC BY-SA 4.0 or, when specifically noted, under another accepted free and open content license. Fedora Logo.
  75. [75]
    Infrastructure private cloud - Fedora Project Wiki
    Fedora Infrastructure is running a private cloud infrastructure for various infrastructure and community projects. ... We will provide fedora, centos and ...
  76. [76]
    https://fedoraproject.org/wiki/Infrastructure_private_cloud
  77. [77]
    Docs Project - Fedora Project Wiki
    The mission of Fedora's Documentation Project is to improve the overall experience of Fedora users and contributors by providing documentation.
  78. [78]
    Fedora Docs: Fedora Documentation
    How tos and tutorials for using and configuring Fedora Linux. Fedora Tools. Documentation of generic Fedora installation and administration tools. EPEL.Fedora Workstation · Fedora Quick Docs · Fedora Project Learn how the... · EPEL
  79. [79]
    Fedora Localization Team
    Aug 27, 2023 · The goal of the Fedora Localization Team (L10N) is to bring everything around Fedora (software, documentation, websites, and the culture) closer to local ...<|control11|><|separator|>
  80. [80]
    How To Use Weblate - Fedora Docs
    Aug 27, 2023 · Weblate is a web based translation tool with tight version control integration. It features a simple and clean user interface, propagation of translations ...
  81. [81]
    Extra Packages for Enterprise Linux (EPEL) - Fedora Docs
    EPEL is an initiative within the Fedora Project to provide high quality additional packages for CentOS Stream and Red Hat Enterprise Linux (RHEL).Getting started · Available packages · Requesting a new package · EPEL Next
  82. [82]
    History and philosophy of EPEL (Extra Packages for Enterprise Linux)
    The EPEL project was born out of Fedora. There was a need for quality 3rd party packages for Enterprise Linux using the already existing Fedora infrastructure.
  83. [83]
    What's EPEL, and how do I use it? - Red Hat
    Nov 21, 2019 · EPEL (Extra Packages for Enterprise Linux) is a Fedora SIG providing additional packages for RHEL, not in RHEL, and not part of the official ...
  84. [84]
    Security Lab - Fedora Project Wiki
    The Fedora Security Spin is a live media based on Fedora to provide a safe test environment for working on security auditing, forensics and penetration testing.
  85. [85]
    FreeIPA - Identity, Policy, Audit — FreeIPA documentation
    Integrated security information management solution combining Linux (Fedora), 389 Directory Server, MIT Kerberos, NTP, DNS, Dogtag certificate system, SSSD and ...About · Documentation · Downloads · FreeIPA Identity Management...
  86. [86]
    Fedora Container & Tools Documentation
    Fedora Container SIG. The Fedora Container SIG mission is to maintain, grow, guide and promote best practice of the development and release of container images.
  87. [87]
    Frequently Asked Questions (FAQ) - Fedora Docs
    EPEL (Extra Packages for Enterprise Linux) is a Fedora initiative providing high-quality, additional, free/libre open source packages for RHEL and CentOS ...Why is the Fedora Project... · What is EPEL-Next? · Does EPEL replace packages...