Hubbry Logo
search
logo
X.Org Foundation avatar
X.Org Foundation
X.Org Foundation
current hub
2196598

X.Org Foundation

logo
Community Hub0 Subscribers
Read side by side
X.Org Foundation
View on Wikipedia
from Wikipedia

The X.Org Foundation is a non-profit corporation chartered to research, develop, support, organize, administrate, standardize, promote, and defend a free and open accelerated graphics stack. This includes, but is not limited to, the following projects: DRM, Mesa 3D, Wayland, and the X Window System and its primary implementation, the X.Org Server.[2][3]

Key Information

Organization

[edit]

The X.Org Foundation was founded on 22 January 2004.[4]

The modern X.Org Foundation came into being when the body that oversaw X standards and published the official reference implementation joined forces with former XFree86 developers.[5] The creation of the Foundation marked a radical change in the governance of X (see the history of the X Window System). Whereas the stewards of X since 1988 (including the previous X.Org, part of The Open Group) had been vendor organizations, the Foundation is led by software developers and using community development on the bazaar model, which relies on outside involvement. Membership is also open to individuals, with corporate membership being in the form of sponsorship.

In 2005 the X.Org Foundation applied for 501(c)(3) non-profit status. In 2012, with the help of the Software Freedom Law Center (SFLC), the Foundation gained the status. In 2013, the Foundation lost the status because they did not fill a tax form (it had no income to declare and did not get any info from SFLC) and in the same year it regained the status, after clearing up the issue.[6] In 2016, the X.Org Foundation joined Software in the Public Interest (SPI)[7] who would manage the bureaucracy.[8]

In 2019, freedesktop.org formally joined the X.Org Foundation.[9][10]

In 2023, The X.Org Foundation decided to join Software Freedom Conservancy[7], which took over the bureaucratic roles SPI had had previously[11].

Fields of activity

[edit]

The X.Org Foundation does not provide technical guidance, roadmaps or deadlines, releases or supervision of any kind.

The X.Org Foundation does provide communication tools (in relation with freedesktop.org), an annual physical meeting and money to help developing the free graphics stack.

  • a physical annual meeting (X.Org Developer's Conference)
  • Travel sponsorship:
  • The X.Org Foundation participated as an organization of the Google Summer of Code (GSoC). This allows students to participate to X.Org-related projects over the summer .
  • Endless Vacation of Code (EVoC): EVoC is a GSoC-like project, funded by the X.Org Foundation. It allows students to participate to X.Org-related projects during their vacation, at any time of the year.
  • Communication: Google+[needs update] and Twitter Google+/YouTube: Store and/or link to talk videos, slides, blog articles or G+ posts related to projects under our umbrella (Martin Peres); Twitter: Mostly security issues, random updates (Alan Coopersmith).
  • There is an X.Org developer guide written by Alan Coopersmith, Matt Dew and the X.Org team; edited by Bart Massey at https://www.x.org/wiki/guide/

The X.Org Foundation organizes the annual X.Org Developer's Conference (XDC) and sponsors students to work on X.Org as part of their X.Org Endless Vacation of Code (EVoC) initiative.[12]

The X.Org Server and xlib are the reference implementation of the X protocol, and is commonly used on Linux and UNIX; it is the fundamental technology underlying both the modern GNOME and KDE desktops and older CDE desktop environment; applications written for any of these environments can be run simultaneously.

xclock

Along with reference implementation of X protocol, the X.org Foundation hosts development of several utilities and example applications, including xcalc on-screen calculator, xclock simple digital and analog clock, xedit text editor, xload periodically updated histogram of the average system load, xterm terminal emulator, and xeyes which shows, by default, a pair of eyes that follow the mouse cursor.

As of April 2013, the Board of Directors consisted of Alan Coopersmith, Alex Deucher, Martin Peres, Matt Dew, Matthias Hopf, Peter Hutterer (Secretary), Stuart Kreitman (Treasurer), and Keith Packard.[13]

X.Org Developer's Conference

[edit]

The physical meeting is the X.Org Developer's Conference (XDC/XDS),[14] which is organized once a year, around September/October and alternates between North America and Europe and lasts for 3 days. The board of directors can cover the travel and accommodation expenses to the developers who couldn't attend an X.Org-related conference (XDC or FOSDEM?) otherwise.

Conference history

[edit]
Event and year Date Host city Venue Resources Themes
XDC2004 28–30 April Cambridge, Massachusetts, USA Cambridge Research Laboratory [1]
XDC2005 12–14 February Cambridge, Massachusetts, USA Cambridge Research Laboratory [2] X.Org Server, Cairo, xephyr, ...
XDC2006 8–10 February Santa Clara, California, USA Sun Microsystems campus [3] Xgl,
XDC2007 7–9 February Menlo Park, California, USA TechShop Menlo Park facility [4]
XDS2007 10–12 September Cambridge, United Kingdom Clare College [5]
XDC2008 16–18 April Mountain View, California, USA Google campus [6]
XDS2008 3–5 September Edinburgh, United Kingdom Edinburgh Zoo [7] XKB, MPX, ...
XDC2009 28–30 September Portland, Oregon, USA University Place Hotel, Portland State University [8]
XDS2010 16–18 September Toulouse, France Toulouse 1 University Capitole [9]
XDC2011 12–14 September Chicago, Illinois, USA McCormick Tribune Campus Center [10]
XDC2012 19–21 September Nuremberg, Germany SUSE campus [11]
XDC2013 23–25 September Portland, Oregon, USA University Place Hotel, Portland State University [12] DRM, DRI3, XCB, nouveau, etc.
XDC2014 8–10 October Bordeaux, France Laboratoire Bordelais de Recherche en Informatique (LaBRI) [13] Wayland, Tizen, FreeBSD, DragonflyBSD, Mesa 3D, etc.
XDC2015 16–18 September Toronto, Canada Seneca@York campus, Seneca College [14] GLSL compiler, Nouveau, libinput, Freedreno, Etnaviv, amdgpu, drm, etc.
XDC2016 20–22 September Helsinki, Finland Haaga-Helia University of Applied Sciences [15]
XDC2017 20–22 September Mountain View, California, USA Google Bldg 1055 [16]
XDC2018 26–28 September A Coruña, Galicia (Spain) Computer Science Faculty of University of A Coruña [17]
XDC2019 2–4 October Montreal, Canada Concordia University Conference Centre [18]
XDC2020 16–18 September Virtual Virtual [19] Archived 7 July 2020 at the Wayback Machine
XDC2021 15–17 September Virtual Virtual [20]
XDC2022 4–6 October Minneapolis, Minnesota University of St. Thomas [21]
XDC2023 17–19 October Coruña, Spain PALEXCO [22]
XDC2024 9–11 October Montréal, Canada Concordia University Conference Center [23]
XDC2025 29 September – 1 October Vienna, Austria TU Wien [24]

X.Org Endless Vacation of Code (EVoC)

[edit]

X.Org Endless Vacation of Code (EVoC) is a Google Summer of Code (GSoC)-like project initiated in 2008 funded by the X.Org Foundation. It allows students to participate to X.Org-related projects during their vacation, at any time of the year.

An example of an accepted EVoC project from 2014 is to work on nouveau, the free and open-source graphics device driver for GeForce-branded GPUs.[15] NVA3/5/8 are the engineering names of the Tesla-based GT215, GT216 and GT218.[16]

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

X.Org Foundation

View on Grokipedia
from Grokipedia
The X.Org Foundation is an educational non-profit corporation chartered to research, develop, support, organize, administrate, standardize, promote, and defend a free and open accelerated graphics stack, including the X Window System, Direct Rendering Manager (DRM), Mesa, and Wayland.[1] Founded in late 2003 to early 2004 amid a licensing dispute within the XFree86 project, it succeeded the X Consortium by assuming control of the x.org domain and merging the XFree86 codebase with prior X.Org developments, ensuring continued open-source stewardship of these technologies.[1] As a low-overhead, all-volunteer organization, the Foundation operates with open membership and an elected Board of Directors, who oversee its activities and fiscal responsibilities, often in partnership with entities like the Software Freedom Conservancy for donations.[2][1] Its key efforts include funding student-led development programs such as the X.Org Endless Vacation of Code (EVoC), organizing workshops and conferences like XDC (X.Org Developer's Conference), and facilitating independent module releases for the X Window System, with the last full release being X11R7.7 in 2012.[1][3] The Foundation supports the broader free desktop community through hosting mailing lists, providing source code mirrors, and encouraging sponsorships to advance open graphics initiatives.[2]

History

Origins and Pre-Foundation Era

The X Window System originated at the Massachusetts Institute of Technology (MIT) in 1984, developed as a network-transparent windowing system to address the graphical interface needs of distributed computing environments.[4] It emerged from simultaneous requirements within MIT's Project Athena and the Laboratory for Computer Science, where researchers sought a flexible, redistributable solution for bitmap displays that could operate over networks without vendor lock-in.[5] Robert W. Scheifler and Jim Gettys led the initial implementation, starting with a prototype based on the earlier W window system and emphasizing simplicity, extensibility, and free redistribution to encourage widespread adoption.[6] By 1988, as commercial interest in X grew, MIT established the MIT X Consortium, a member-funded non-profit organization to oversee the system's technical development, administrative coordination, and standardization efforts.[7] This consortium facilitated collaboration among academic institutions, vendors, and developers, releasing key versions like X11 in 1987 while managing licensing and commercialization to balance openness with industry support.[8] Its formation marked a shift from purely academic development to a structured framework that promoted the X protocol's evolution as an open standard. In 1993, the X Consortium, Inc. was created as an independent non-profit successor to the MIT X Consortium, incorporating in Delaware to focus on the ongoing maintenance and enhancement of the X11 protocol.[7] Headquartered near MIT in Cambridge, Massachusetts, it operated through membership dues and active participation from organizations worldwide, ensuring the protocol's stability and interoperability across diverse hardware and operating systems.[8] This entity sustained X's role as a foundational technology for Unix-like systems until the late 1990s. During the 1990s, the XFree86 project arose as a pivotal open-source implementation of the X Window System, targeting Intel x86-based personal computers and Unix-like operating systems.[9] Initiated in 1992 by David Dawes, Glenn Lai, Jim Tsillas, and David Wexelblat to address limitations in earlier X386 ports, building on contributions like Thomas Roell's X386 server, XFree86 emphasized hardware acceleration, driver support, and performance optimizations for non-proprietary environments.[10] It became the dominant free X server for Linux and other open-source platforms, driving innovation in graphics rendering and configuration tools while remaining compatible with the X Consortium's protocol specifications.[9] Tensions culminated in early 2004 with the release of XFree86 4.4.0, which incorporated licensing changes—adding clauses that rendered it incompatible with the GNU General Public License (GPL)—sparking disputes over open-source principles and leading to a community fork that transitioned into the X.Org Foundation later that year.[9]

Formation and Early Developments

The X.Org Foundation was incorporated as a non-profit corporation in Delaware, United States, in early 2004, established specifically to resolve escalating licensing disputes with the XFree86 Project over changes introduced in its 4.4.0 release. These disputes, which involved the adoption of a license deemed incompatible with the GNU General Public License by the Free Software Foundation, prompted a group of developers, vendors, and distributors to form the foundation as a successor to the informal X.Org group. Operating as a 501(c)(3) scientific charity, the organization aimed to steward the open development of the X Window System while ensuring compatibility with free software ecosystems.[11][1][12] To build its initial codebase, the foundation merged the legacy X11R6.6 sources from prior X.Org efforts with selected, compatible contributions from XFree86 4.4 release candidate 2, carefully excluding any components licensed under the contentious XFree86 1.1 terms. This hybrid approach preserved key advancements like enhanced driver support and the XAA acceleration architecture from XFree86 while reverting to permissive licensing for broader adoption. The resulting codebase emphasized modularity and maintainability, laying the groundwork for future enhancements such as IPv6 support and updated Render extension versions.[13] The foundation's first major output was the release of X Window System X11R6.7 (X.Org Server 6.7) on April 6, 2004, marking the debut of the forked project and demonstrating rapid progress despite the split. This was followed by X11R7.0 in December 2005, which introduced a fully modularized structure using Autotools for easier compilation and distribution across platforms. Early development faced significant challenges, including stabilizing the integrated codebase—such as fixing bugs in Intel graphics drivers—and coordinating the migration of the developer community, with tools like Bugzilla on freedesktop.org facilitating contributions and transitions from XFree86. Projects like Cygwin/X explicitly shifted to the X.Org codebase during this period due to waning XFree86 support.[13][11][14][15] In response to these formative hurdles, the foundation adopted a structured release strategy starting in 2005, committing to annual major versions to balance innovation with reliability and encourage sustained community involvement. This cycle enabled consistent updates, such as the interim X11R6.8 and 6.9 releases in 2004 and 2005, while prioritizing long-term stability over frequent disruptions.[16][17]

Key Milestones and Releases

The X.Org Foundation marked a significant shift in the development of the X Window System with the release of X11R7.0 on December 21, 2005, introducing a fully modular architecture that replaced the previous monolithic build system.[18] This change enabled independent development and maintenance of individual components, such as drivers and libraries, allowing for more focused updates and improved support for diverse hardware configurations without requiring a complete rebuild of the entire system.[18] Building on this modular foundation, the X.Org Foundation integrated key open-source graphics projects, including the Mesa 3D graphics library and the Direct Rendering Infrastructure (DRI), into its ecosystem during the mid-2000s.[1] Mesa provides an open implementation of OpenGL and other graphics APIs, while DRI facilitates direct access to graphics hardware for accelerated rendering, enhancing 3D performance in X11 applications.[19] These integrations, formalized under the Foundation's oversight, streamlined collaboration between X server developers and graphics driver teams, fostering advancements in open-source graphics stacks.[1] In response to evolving display protocols, the Foundation began supporting the transition to Wayland—a modern successor to X11 initiated in 2008—with the introduction of XWayland in 2014 to enable compatibility for legacy X11 applications on Wayland compositors.[20] This effort addressed limitations in X11's network transparency and security model while preserving backward compatibility, allowing gradual adoption without disrupting existing software ecosystems.[21] Major release cycles continued to drive improvements, culminating in X11R7.7 on June 6, 2012, which incorporated enhancements like multi-touch support via the XInput extension and fence objects for better synchronization in rendering pipelines.[22] Following this, the Foundation shifted to independent module releases rather than monolithic versions, sustaining updates to the X.Org Server through 2025 to address security vulnerabilities, input handling, and driver compatibility.[23] Development activity remained robust into 2025, with contributors adding 11,998 lines of code to the X.Org Server while removing 14,680 lines in 2024 alone, reflecting active maintenance and refactoring efforts amid the broader graphics ecosystem's evolution.[24][25]

Organization and Governance

Structure and Membership

The X.Org Foundation operates as an all-volunteer, low-overhead non-profit corporation with an open membership model available to actively involved individuals, such as developers, testers, and documentation contributors supporting the X Window System technologies.[1][26] This structure emphasizes community-driven operations without paid staff, relying instead on volunteer contributions for development, maintenance, and administrative tasks, overseen by an elected Board of Directors.[1][2] Membership is granted to those demonstrating ongoing involvement in X.Org activities, requiring board approval and adherence to the organization's bylaws, but it is not necessary for general participation in projects or access to resources like source code.[26] Benefits include voting rights in board elections and decisions on bylaws or membership agreements, the ability to chair foundation committees, host related events, and access to select non-public materials, along with opportunities to participate in or mentor funded programs such as student development initiatives.[26][3] Funding for the foundation derives primarily from individual and corporate donations, cash and in-kind sponsorships, and travel grants, facilitated through its fiscal sponsorship by the Software Freedom Conservancy since 2023 to ensure tax-deductible contributions.[27][2] The organization also maintains reserves accumulated from prior activities, with historical goals focused on deploying these funds toward productive efforts like student stipends and community workshops rather than traditional contracting.[28] Operations remain lean, with no salaried employees, enabling efficient allocation of resources through volunteer efforts and board guidance.[1] The foundation provides annual financial reports publicly through its website, covering fiscal years up to 2017 and including treasurer summaries approved by the board within 60 days of year-end, promoting transparency in how donations support ongoing X.Org advancements.[29][30]

Board of Directors and Leadership

The X.Org Foundation is governed by an eight-member Board of Directors, with four seats elected annually by foundation members for two-year terms beginning in the first quarter of the election year.[31] This staggered structure ensures continuity in leadership while allowing regular refreshment of the board. The election process involves nominations submitted by eligible members via email to [email protected], including the nominee's name, affiliation, contribution statement, and personal statement; a two-week nomination period is followed by candidate Q&A, membership renewal deadlines, and a two-week voting phase using ranked preferences via the online portal at members.x.org, employing the Borda Count method.[31] The board can be contacted collectively at [email protected] for inquiries related to governance or nominations.[32] As of November 2025, the board consists of the following members, with terms ending in the specified quarter:
NameAffiliationTerm EndsKey Roles
Mark FilionCollaboraQ1 2026XDC Organizer and Sponsor Coordinator, Housekeeper
Arkadiusz HilerCodeWeaversQ1 2027Treasurer, Social Media Manager
Lyude PaulRed HatQ1 2027Secretary
Erik Faye-LundCollaboraQ1 2026XDC Paper Committee Chair
Simon SerUnaffiliatedQ1 2026Housekeeper, XDC Sponsor Coordinator
Neal GompaVelocity LimitlessQ1 2026
Andres GomezIgaliaQ1 2027
Harry WentlandAMDQ1 2027
[32] The board oversees the foundation's strategic direction, approves funding allocations, and organizes key events such as the X.Org Developer's Conference (XDC); it maintains no formal executive officers but assigns administrative roles including secretary, who handles meeting agendas, minutes, and annual reports, and treasurer, who manages financial reporting and reimbursements.[33] Additional duties encompass liaison work with organizations like Khronos and VESA, as well as housekeeping tasks such as maintaining documentation and social media presence.[33] Historical transitions reflect the board's evolving composition to align with community needs; for instance, the 2023 election added Arkadiusz Hiler, Lyude Paul, Christopher Michael, and Daniel Vetter for terms ending Q1 2025, following a 73.3% voter turnout among members.[34] The 2024 election, prompted by the end of terms for Emma Anholt, Ricardo Garcia, and Alyssa Rosenzweig, along with other adjustments, elected Mark Filion, Erik Faye-Lund, Simon Ser, and Neal Gompa for terms ending Q1 2026, with 75.3% turnout.[35] In 2025, the election for the remaining seats re-elected Lyude Paul and Arkadiusz Hiler while adding Andres Gomez and Harry Wentland for terms ending Q1 2027, achieving a 92.5% turnout amid a resignation by Simona Vetter in Q3 2024 and the end of Christopher Michael's term in Q1 2025.[36]

Mission and Focus Areas

Objectives and Goals

The X.Org Foundation is chartered to research, develop, support, organize, administrate, standardize, promote, and defend a free and open accelerated graphics stack, encompassing technologies such as the X Window System, DRM, Mesa, and Wayland.[37] This mandate emphasizes worldwide stewardship of open-source graphics technologies, ensuring their evolution through community collaboration rather than proprietary control.[38] The Foundation's principles prioritize vendor-neutral and architecture-independent standards, fostering innovation in display servers and related systems while avoiding dependencies on closed-source software.[39] Central to its goals is the promotion of community-driven development, including education, organization, and participation among developers and users of these graphics stacks.[37] The Foundation explicitly avoids funding traditional contracting for X Window System maintenance, instead directing resources toward emerging areas to encourage novel advancements.[1] This approach supports accessibility in graphics systems by upholding network transparency, allowing seamless operation across diverse computing environments and hardware.[39]

Supported Technologies and Projects

The X.Org Foundation stewards a suite of open-source projects that form the backbone of graphical computing on Unix-like systems, emphasizing interoperability, hardware acceleration, and evolution toward modern display protocols. These initiatives support the development and maintenance of essential graphics infrastructure, enabling developers and users to build robust visual environments. Central to this ecosystem is the X.Org Server, alongside complementary libraries and kernel components that handle rendering, display management, and protocol transitions.[1] The X.Org Server serves as the primary implementation of the X Window System, providing a network-transparent windowing system that manages client-server interactions for graphical user interfaces on bitmap displays. It handles input distribution from devices like keyboards and mice to applications, while accepting output requests to render windows, icons, and other visual elements across local or remote connections. Developed in collaboration with the freedesktop.org community, the server supports extensions for advanced features such as compositing and damage tracking, ensuring compatibility with a wide range of hardware and software. Annual major releases since 2004 have incorporated improvements in performance and security, making it a foundational tool for desktop environments like GNOME and KDE.[2][1][40] Mesa 3D is the flagship open-source graphics library under the Foundation's purview, delivering implementations of the OpenGL, OpenGL ES, Vulkan, and EGL APIs to enable accelerated 3D rendering on diverse hardware platforms. It acts as a software rasterizer and driver interface, supporting GPUs from vendors including Intel, AMD, and NVIDIA through gallium3d and classic drivers, while also providing virtual GPU support for environments like VMware. Mesa's architecture allows for direct rendering bypasses traditional CPU involvement, optimizing for real-time applications in gaming, scientific visualization, and multimedia. Its integration with the X.Org stack has been pivotal, with ongoing development ensuring conformance to Khronos Group specifications and broad Linux distribution adoption.[41][42][41] The Direct Rendering Manager (DRM) comprises kernel modules that facilitate low-level graphics hardware acceleration within the Linux kernel, serving as a bridge between user-space applications and GPU resources. DRM provides mechanisms for memory management, including the Translation Table Manager (TTM) for dedicated video RAM and the Graphics Execution Manager (GEM) for unified memory architectures, allowing efficient allocation of buffers for textures, framebuffers, and command submissions. It enables kernel mode setting (KMS) for dynamic display configuration without user-space intervention, reducing boot times and improving stability. As a core component of the open graphics stack, DRM's drivers are actively maintained to support modern GPUs, with interfaces exposed via libdrm for higher-level libraries like Mesa.[43][44] In parallel, the Foundation supports the Wayland protocol and associated compositors as a contemporary successor to X11, designed for simpler, more secure communication between display servers and clients. Wayland defines an asynchronous, object-oriented protocol where clients directly manage their surface rendering, while the compositor handles input events and composition, eliminating much of X11's intermediary overhead for reduced latency and enhanced privacy. The reference implementation, Weston, demonstrates these principles as a minimal, feature-rich compositor that supports multiple backends for DRM, headless operation, and nested compositing, aiding developers in testing and extending the ecosystem. Weston includes built-in shells for desktop and kiosk modes, showcasing Wayland's flexibility for embedded and general-purpose use.[45][46][47] To bridge the transition, XWayland operates as an integrated X server running as a Wayland client, allowing legacy X11 applications to display and interact seamlessly within Wayland-based sessions. It translates X11 protocol requests into Wayland surfaces, preserving compatibility for tools reliant on X extensions like GLX for OpenGL rendering, without requiring full X11 server deployment. This compatibility layer is bundled with the X.Org Server distribution and is essential for hybrid environments, ensuring gradual adoption of Wayland while maintaining support for the vast X11 software corpus. Ongoing enhancements focus on performance optimizations and security alignments with Wayland's model.[2]

Programs and Events

X.Org Developer's Conference

The X.Org Developer's Conference (XDC) is the annual flagship event organized by the X.Org Foundation for developers working on the open-source graphics stack, including topics such as Linux kernel drivers, the Mesa graphics library, and the Wayland display server protocol.[48][49] Established in 2005, it serves as a primary forum for technical discussions, collaboration, and advancement of free and open-source software in graphics and display technologies.[50] The conference typically spans three days and features an in-person format with presentations, workshops, and unstructured hack sessions to facilitate hands-on problem-solving and project coordination among attendees. Events are live-streamed on YouTube to enable broader participation from the global community.[51][52] Funding for the conference, including travel grants, is provided through the X.Org Foundation's sponsoring fund.[53] XDC originated from earlier X.Org Foundation meetings and the Desktop Developers' Conference held in Ottawa, Canada, in July 2004, evolving into a dedicated annual gathering starting with XDC2005 in Cambridge, Massachusetts.[54][50] Over time, the event has grown in scope and international reach, with locations alternating between North America and Europe or Asia to accommodate diverse contributors.[55] Notable past events include XDC2007, held February 7–9 in the San Francisco Bay Area, which focused on early advancements in X Window System development.[54] XDC2017 took place September 20–22 at the Googleplex in Mountain View, California, featuring talks on Wayland integration and graphics optimizations.[56] In XDC2023, hosted October 17–19 in A Coruña, Spain, sessions highlighted progress in the open-source NVIDIA Vulkan driver (NVK) and Kernel Mode Setting (KMS) enhancements.[57][58] XDC2024 was held October 9–11 in Montréal, Canada.[55] XDC2025 took place September 29–October 1, 2025, in Vienna, Austria, hosted by TU Wien and co-organized by Snap, continuing the tradition of fostering innovation in open graphics technologies.[48][59]

Endless Vacation of Code

The Endless Vacation of Code (EVoC) is a mentorship program initiated by the X.Org Foundation in 2008 as a GSoC-like initiative to support student contributions to open-source graphics projects, with expansions in 2011 to enhance year-round participation and funding mechanisms.[3][60] Funded directly by the Foundation, it offers stipends of up to $5,000 USD per student, disbursed in an initial payment of $500 followed by two $2,250 installments upon achieving project milestones.[3][61] Unlike seasonal programs such as GSoC, EVoC provides flexible timing, enabling projects to run for 3-4 months at any point during the year to accommodate students whose academic schedules prevent summer-only involvement.[3][62] Participants must be enrolled university students, and the program emphasizes nearly full-time commitment, including upstreaming code patches and producing technical documentation.[3] The application process requires students to submit detailed proposals for X.Org-related projects, which are evaluated by the Foundation board after securing a lead mentor from the community; accepted projects focus on improvements to the graphics stack, such as driver enhancements or protocol integrations.[3][60] Mentors propose ideas aligned with ongoing needs, and the board votes on funding based on feasibility and impact.[60] Following the discontinuation of X.Org's participation in GSoC after 2023, EVoC emerged as the Foundation's primary outreach mechanism for engaging student developers in flexible, self-paced contributions.[3] Notable examples include a 2014 project enhancing the nouveau open-source graphics device driver for NVIDIA hardware, as well as efforts on X.Org Server optimizations and Wayland protocol integrations to improve compositing and display handling.[3][63] Participant reports underscore the program's value in fostering practical open-source experience through personalized mentorship, though early iterations highlighted challenges like insufficient preparation time leading to adjusted expectations for project scope and timelines.[60][61] Overall, contributors have noted the flexibility as a key enabler for balancing academics with meaningful code contributions, resulting in sustained community involvement post-project.[60]

Recent Developments

Security Updates and Vulnerabilities

In early 2025, the X.Org Foundation disclosed eight critical vulnerabilities affecting the X.Org Server prior to version 21.1.16 and XWayland prior to version 24.1.6, including issues such as use-after-free errors and buffer overflows that could enable local privilege escalation.[64][65] Some of these flaws, like CVE-2025-26597 involving a buffer overflow in XkbChangeTypesOfKey, traced their origins to the initial implementation of xkb.c in X11R6 released in 1994, highlighting long-standing risks in the codebase.[64][66] The vulnerabilities were promptly addressed through patches released in X.Org Server 21.1.16 and XWayland 24.1.6, with full disclosure and advisory details published via the xorg-announce mailing list on February 25, 2025, and subsequent distribution updates in March 2025 by major Linux vendors.[64][67] These fixes mitigated potential exploits, including denial-of-service and code execution scenarios, underscoring the foundation's commitment to rapid remediation.[66] The X.Org security team maintains ongoing responsibilities for coordinating vulnerability reporting, triage, and remediation across X.Org projects, with reports directed to [email protected] following a structured checklist that ensures coordinated disclosure and patch development.[66][68] In 2024, the X.Org Server codebase experienced a decade-high level of development activity, with nearly 12,000 lines of code added and over 14,000 removed, which facilitated enhanced security reviews and proactive auditing to identify and address latent issues.[24] The foundation emphasizes community-driven reporting for security issues, enabling rapid responses through collaborative patches without reliance on formal bug bounty programs, as evidenced by the swift handling of the 2025 disclosures via public mailing lists and open-source contributions.[66][64]

Community Initiatives and Forks

In June 2025, the X.Org Foundation's X server project saw the launch of Xlibre, a community-driven fork initiated by leading developer Enrico Weigelt to revitalize and modernize the codebase. This fork, branched on June 5, 2025, focuses on extensive code cleanups, enhanced security features, and performance optimizations, addressing long-standing maintenance challenges in the original X.Org Server while preserving its core functionality for X11 compatibility. By late June, the project released its inaugural version, Xlibre 25.0, attracting over 30 contributors and integrating new features not yet in the upstream repository.[69][70][71] Community engagement remained robust through the X.Org Developer's Conference (XDC) in 2024, held in Montréal, Canada, from October 9 to 11, where developers discussed advancements in Linux kernel graphics drivers, Mesa 3D graphics library improvements, and related open-source tools. The event featured high participation, with sessions on topics like video offloading in Wayland and Rust-based porting efforts for graphics components, underscoring the ongoing vitality of volunteer contributions. XDC 2025 was held from September 29 to October 1 in Vienna, Austria, hosted by TU Wien, featuring sessions on similar themes including GPU Linux kernel drivers, Mesa improvements, Wayland protocol governance, and Rust-based graphics efforts.[51][48][72] The 2024 board elections bolstered the Foundation's volunteer leadership, adding members such as Arkadiusz Hiler from CodeWeavers and Christopher Michael from Igalia, whose two-year terms extend through early 2026 and support sustained governance focused on open-source graphics stewardship. Broader community initiatives include targeted workshops, such as the Wayland development session at XDC 2024, which explored protocol governance and integration strategies, alongside annual reporting that highlights strategic allocation of reserves toward core development activities like student programs and hackfests.[35][73] Amid these efforts, the community continues a measured shift toward Wayland adoption as the preferred display protocol for modern Linux desktops, while committing to X11 backward compatibility through projects like Xlibre to ensure seamless transitions for legacy applications and users. Recent security patches in 2025 have further supported this balanced approach by fortifying both X11 and Wayland ecosystems.[1][74]

References

  1. X.Org Foundation
  2. X.Org
  3. The X.Org Endless Vacation of Code (EVoC)
  4. [PDF] The X Window System
  5. 40 years later, X Window System is far more relevant than anyone ...
  6. X Window System At 40 - DSHR's Blog
  7. XConsortium - X.Org
  8. X Consortium Definition - The Linux Information Project
  9. XFree86 definition by The Linux Information Project (LINFO)
  10. XFree86 Announces Formation of the XFree86 Project, Inc.
  11. X.Org Foundation releases X Window System X11R6.7 - LWN.net
  12. X11R6.8.2 Officially Released - X.Org
  13. [PDF] Release Notes for X11R6.7.0 - X.Org
  14. X11R6.9 and X11R7.0 Officially Released - X.Org
  15. The Complete Guide to XFree86 - R. Couri Hay
  16. History - X.Org
  17. [PDF] X.Org and XFree86 Version Numbering Schemes
  18. X11R7.0 Release - X.Org
  19. [PDF] Release Notes for X11R7.6 - X.Org
  20. LFCS 2012: X and Wayland - LWN.net
  21. Release Notes for X11R7.7 - X.Org
  22. https://www.x.org/releases/individual/
  23. X.Org Server Development Hit A Decade High For The ... - Phoronix
  24. Membership - X.Org
  25. SponsorshipPage - X.Org
  26. xorg-report-2009
  27. Reports - X.Org
  28. treasurer-2017 - X.Org
  29. Elections - X.Org
  30. X.Org Foundation Board of Directors
  31. X.org Foundation Duties
  32. 2023 - Elections - X.Org
  33. None
  34. 2025
  35. [PDF] BYLAWS of the X.Org Foundation
  36. 2022 Program X.Org Foundation - Google Summer of Code
  37. XORGFOUNDATION
  38. X Window System Protocol - X.Org
  39. Home — The Mesa 3D Graphics Library
  40. Introduction — The Mesa 3D Graphics Library latest documentation
  41. Introduction - The Linux Kernel documentation
  42. DRM Memory Management - The Linux Kernel documentation
  43. Wayland
  44. https://wayland.freedesktop.org/docs/html/
  45. Welcome to Weston documentation! - Freedesktop.org
  46. XDC 2025 - X.Org Developer's Conference - Indico
  47. X.Org Developer's Conference 2024 - Collabora
  48. XDC2005 - X.Org
  49. XDC 2024 - X.Org Developer's Conference 2024 - Indico
  50. X.Org Developer's Conference (XDC) 2023 - YouTube
  51. Travel grants - XDC 2025 - Indico
  52. History - X.Org
  53. Events - X.Org
  54. Events/XDC2017 - xorg
  55. XDC 2023 - X.Org Developer's Conference 2023 (17-19 October ...
  56. October 17 | Nouveau/NVK update | Faith Ekstrand and Karol Herbst
  57. XDC 2025 - The Khronos Group
  58. [PDF] Return of experience on the EVoC - Selecting and preparing students
  59. Igalia Coding Experience, GSoC, Outreachy, EVoC
  60. xorg-report-2010
  61. [Nouveau] Project ideas for GSoC/EVoC - Mailing Lists
  62. https://lists.x.org/archives/xorg-announce/2025-February/003584.html
  63. Eight New Security Vulnerabilities Reported Against The X.Org ...
  64. Security Advisories - X.Org
  65. X.Org Server & XWayland: 8 Critical Security Bugs Patched
  66. https://www.x.org/wiki/Development/Security/Checklist/
  67. XLibre 25.0 Released As Inaugural Version Of X.Org Server Fork
  68. Xlibre, a new fork of the X.org X11 server, announced - The Register
  69. Xlibre 25.0 summer solstice release - Mailing Lists - X.Org
  70. From Vienna, with Open Source: XDC 2025 - Collabora
  71. XDC 2024 - X.Org Developer's Conference 2024 (9-11 October ...
  72. X11 Session Removal FAQ – Rust in Peace - GNOME Blogs
User Avatar
No comments yet.