BlankOn Linux

Getting Started

The quickest way to start contributing is by joining our Telegram group (https://t.me/BlankOnLinux/51909). Follow the ongoing discussions, understand the current priorities, and take action to help the team as a Freelance Contributor.

If you are not sure, feel free to lurking around our wiki to get better understanding of our project.

If you believe you can commit to the project as a serious long-term side endeavor, either as a Core Contributor or a Mentee. please send an email to blankon-dev@googlegroups.com.We will arrange a meeting to exchange expectations, discuss responsibilities, and ensure mutual understanding about the project's direction and your potential role within it.

For further explanation about contributor categories and their contribution areas, please see the sections below.

Contributor Categories

Regardless of their level of involvement, all contributors are valued and will be properly credited for their work.

Core Contributor

Core Contributors are individuals who are committed to the project for the long term. They carry greater responsibilities to ensure the project runs effectively and remains sustainable.

Core Contributors often serve as mentors to mentees, providing guidance, leadership, and direction. They typically demonstrate strong ownership, clarity of purpose, initiative, and a high level of accountability.

List of current core contributors: https://github.com/BlankOn/revival/blob/main/CoreContributors.md

Mentee

A Mentee is a contributor who joins the BlankOn project to learn, grow, and improve their skills. Mentees are guided and supported by selected mentors throughout their journey.

Over time, a mentee may graduate and potentially become a Core Contributor based on their development, commitment, and contributions.

Freelance Contributor

Freelance Contributors are individuals who contribute to the project on a flexible, non-committed basis. They may join and leave as needed, without long-term responsibilities. Getting involved is easy, contribution is just one pull request away.

Team / Contribution Areas

There is no dedicated Documentation Team. Every team is responsible for documenting their own activities, challenges, and achievements to this wiki, as part of their contribution to the project.

Package Maintainer

Responsible for maintaining, updating, and ensuring the quality of software packages within the distribution. This includes handling dependencies, security updates, bug fixes, and ensuring compatibility across releases.

Mentors:

Herpiko Dwi Aguno <herpiko@gmail.com>

Research and Development

Focuses on innovation, experimentation, and technical exploration. This team evaluates new technologies, improves existing systems, and proposes architectural or strategic enhancements for the project.

Infrastructure

Manages and maintains the technical backbone of the project, including servers, CI/CD pipelines, repositories, build systems, and deployment processes. This team ensures reliability, performance, and availability of project resources.

Artwork

Handles visual identity and user-facing design elements, including UI/UX assets, themes, branding materials, wallpapers, icons, and promotional visuals. The goal is to ensure a consistent and appealing visual experience.

Public Relations

Responsible for communication and community engagement. This includes managing announcements, social media, events, partnerships, and maintaining a positive public image for the project.