<!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> Dear freedesktop community, I’d like to open a discussion regarding the public-facing presence of freedesktop.org, as well as the internal structure of its standardization process. <h3 data-start="529" data-end="557" class="">Website and Landing Page</h3> Currently, the root domain (<code data-start="587" data-end="604">freedesktop.org</code>) redirects directly to <code data-start="628" data-end="635">/wiki</code>, which presents a raw wiki front page as the main landing page. While this page contains some general information and a brief mention of donations, it is essentially a wall of text without real visual hierarchy, navigation aids, or a clear structure for new visitors. The presentation is dated and not particularly welcoming—especially for those unfamiliar with the project. Some specific issues: <ul data-start="1033" data-end="1607"> <li data-start="1033" data-end="1125" class=""> The site is not really responsive, making it difficult to view or navigate on mobile devices. </li> <li data-start="1126" data-end="1238" class=""> There is no clear landing page that introduces freedesktop.org as an organization or collaboration effort. </li> <li data-start="1239" data-end="1316" class=""> Donation options are buried at the bottom. </li> <li data-start="1317" data-end="1485" class=""> The visual design and information architecture make it hard to understand what freedesktop.org actually is and what projects it encompasses. </li> <li data-start="1486" data-end="1607" class=""> The site (and some services) are not reachable via IPv6, which is increasingly expected from modern infrastructure. </li> </ul> I believe the site would greatly benefit from a proper homepage, separate from the wiki, that clearly and concisely explains: <ul data-start="1739" data-end="1906"> <li data-start="1739" data-end="1785" class=""> What freedesktop.org does and why it matters </li> <li data-start="1786" data-end="1836" class=""> How it relates to Linux/Unix desktop interoperability </li> <li data-start="1837" data-end="1876" class=""> Which projects are under its umbrella </li> <li data-start="1877" data-end="1906" class=""> How to contribute or donate </li> </ul> <h3 data-start="2060" data-end="2087" class="">Standardization Process</h3> Aside from the web presence, I also want to suggest formalizing the way freedesktop.org handles specifications and standards. At present, many specifications exist in various states across different wikis, Git repositories, or documents, without a consistent life cycle model. Taking inspiration from the IETF's RFC process, freedesktop.org could adopt a similar structure with: <ul data-start="2473" data-end="2744"> <li data-start="2473" data-end="2546" class=""> Clear document stages e.g.: draft → proposal → review → accepted → deprecated. </li> <li data-start="2547" data-end="2611" class=""> A central, versioned, and searchable archive of specifications </li> <li data-start="2612" data-end="2672" class=""> Transparent governance: who reviews or approves proposals? </li> <li data-start="2673" data-end="2744" class=""> A clear way for contributors to propose new standards or improvements </li> </ul> This would improve transparency, long-term maintainability, and community participation—especially from distributions and external developers who rely on these standards. I know freedesktop.org is not a real standardization organization, but maybe we could still benefit from this structure. <h3 data-start="2918" data-end="2929" class="">Summary</h3> In short, I propose: <ol data-start="2952" data-end="3273"> <li data-start="2952" data-end="3032" class=""> A redesigned, dedicated homepage for freedesktop.org (not based on the wiki). </li> <li data-start="3033" data-end="3112" class=""> Improved structure and visual clarity, including better donation visibility. </li> <li data-start="3164" data-end="3209" class=""> IPv6 availability for all public services. </li> <li data-start="3210" data-end="3273" class=""> A structured, RFC-style process for standardization efforts. </li> </ol> I’d love to hear your thoughts on this, and I’d be happy to contribute time or resources if there is interest in moving this forward. Best regards, Philippe </body> </html>