Procyberian Systems Distribution (PSD)

Join the Next Evolution of Systems Programming!

Are you tired of open-source projects being consolidated by corporate giants? Do you believe that low-level systems programming deserves strict technical meritocracy, democratic governance, and uncompromising philosophical leadership?

Procyberian Systems Distribution (PSD) is building a decentralized yet highly disciplined ecosystem of Free Software. Our flagship project is a rock-solid, Debian Stable-based GNU/Linux distribution engineered specifically for the next generation of cloud-native infrastructure, kernel-level optimizations, and advanced system bugfixes.

We are looking for visionary Systems Programmers, kernel hackers, cloud architects, and open-source advocates who code in C, C++, Rust, and Golang, as well as automation experts fluent in Python and Java.

🚀 How You Can Participate:

• Contribute Code: Help us patch the LTS kernel, optimize virtualization layers, and build lightweight cloud tooling.
• Shape the Governance: Join as a Contributor, earn your status as a Committer, and run for the Core Team or Project Lead positions in our democratic 2-year election cycles.
• Spread the Philosophy: Help us build a resilient community that stands for “Free Software for everyone.”

Ready to build the future of system infrastructure? 👉 Explore Our Repositories | 👉 Join Our Discussion Forum | 👉 Read Our Chat Channels

Happy Hacking!

Constitution of the Procyberian Systems Distribution (PSD)

Section 1: Core Principles and Definitions

Article 1: Mission and Philosophy

The Procyberian Systems Distribution (PSD) is an independent, transparent, and auditable network of Free and Open Source Software communities. It bridges technical meritocracy with democratic accountability. PSD operates under the fundamental guiding philosophy: “A community for communities, a company for companies, an institution for institutions, and Free Software for everyone.”

Article 2: Trademarks, Infrastructure, and Ownership

1. Ownership and Intellectual Property: The trademark “Procyberian Systems Distribution,” the acronym “PSD,” all official logos, branding assets, the primary domain procyberian.xyz, all related subdomains, and the core server infrastructure are the exclusive property and under the ultimate control of the founder, Mert Gör.
2. Granted Usage: The community and its elected bodies are granted the right to use these assets and trademarks solely as long as they operate in absolute compliance with this Constitution and the overarching philosophy of Free Software.
3. Restrictions on Forking: While copying and modifying the source code under open-source licenses is fully permitted, no independent entity or spin-off project may use the names “Procyberian,” “PSD,” or any official infrastructure without the express, prior written consent of Mert Gör.

Section 2: Governance Model and Roles

Article 3: Benevolent Dictator for Life (BDFL)

1. Leadership: Mert Gör serves as the Benevolent Dictator for Life (BDFL), acting as the philosophical, visionary, and strategic leader of the project. The BDFL guides both the internal community network and the broader computing world toward future aspirations.
2. Veto Power: To protect the future and philosophical integrity of the project, the BDFL holds absolute veto power over all technical architectural decisions and software licensing modifications.
3. Accountability and Recall: The BDFL’s powers are subject to constitutional oversight. In extraordinary circumstances, the BDFL’s veto power can be suspended, or a vote of no confidence can be triggered, by a supermajority vote of 80% from all active Core Team members across the entire ecosystem.

Article 4: Project Roles and Contribution Tiers

1. Contributors: Anyone who contributes to the project via code, documentation, infrastructure support, or community management. This tier is open to all global participants.
2. Committers: Expert developers who have proven their technical merit and hold direct write/commit access to the official code repositories.
3. Core Team: The governing body elected from among the active Committers, responsible for defining the project’s architectural direction and handling administrative decisions.
4. Project Lead Developer: Elected leaders responsible for managing technical operations. They must possess specialized expertise as a Systems Programmer.

Section 3: Elections, Terms of Office, and Voting

Article 5: Election Cycle and Term Limits

1. Term of Office: The mandate for all elected Project Lead Developers and Core Team members is strictly limited to a term of 2 (two) years. Outgoing members are eligible to run for reelection.
2. Electorate: To maintain the rigorous technical discipline required for systems programming, the right to vote in leadership elections is restricted exclusively to active Committers and Core Team members of the respective project.

Article 6: Voting Methodology

All institutional decisions and elections shall be conducted via transparent, verifiable digital voting platforms. Leadership elections shall follow the Condorcet Voting Method (preferential ranked-choice voting), matching the established standards of democratic open-source governance.

Section 4: Technical Standards and Licensing

Article 7: Programming Languages and Technological Focus

1. Core System Layer: Operating system kernels, cloud infrastructure software, virtualization layers, and performance-critical systems shall be developed primarily using C, C++, Rust, and Golang.
2. Tooling and Upper Layers: System utilities, automation scripts, testing frameworks, and user-facing applications may leverage Python and Java.

Article 8: Licensing Policy

All software developed under the PSD umbrella must be released under approved Free and Open Source Software licenses (e.g., GPLv3, AGPLv3, Apache 2.0, or BSD-3-Clause). License selection and any subsequent modifications are subject to the BDFL’s review and veto power. Transitioning any project into an “Open Core” or proprietary business model is strictly prohibited and cannot be proposed.