Processes

General Structure

AYA is a software foundation. It hosts independently progressing projects.

Projects

Projects at AYA are led by appointed project leaders. Each project leader forms a project team at their discretion.

However, the model encouraged by AYA is for previously established communities such as kamp-us, patika.dev, eser.live, etc., to lead these projects.

Project leaders may request specialist resources or technical requirements from AYA based on the project's needs. These requests are fulfilled from AYA’s resource pools.

New project proposals should be submitted via the Project Idea Form.

Project Team

Each project team has a project leader. Permanent team members who contribute to the project are called maintainers.

However, similar to open-source projects, contributors do not need to be part of the project team at AYA. External contributions are reviewed and decided upon by the fixed members of the project team.

To join project teams, ensure your information is listed in our expert pool via the Volunteer Form.

Project Development Process

The project development process follows procedures set by the project leader. Each team may have its own autonomous standards. AYA’s only expectation here is adherence to the fundamental criteria we have defined for our projects.

Our Fundamental Criteria

• Must be published as open-source with a Permissive or CopyLeft license.
• If the project is tied to any domain, ownership of this domain must be transferable.
• An action plan must be prepared to swiftly deploy the project when needed.
• Not storing data, nor violating any legal obligations.
• Adherence to our Code of Conduct.

Project Evaluations

Projects are evaluated according to AYA’s schedule availability. Decisions like incubation, providing support, and graduation of projects are made following these evaluations.