Principles

The following describes the guiding principles used by the Archi® project:

Open – We believe in “open”, in open standards and in open source. We believe in sharing. Archi is open to all; everyone participates with the same rules; there are no rules to exclude any potential contributors

Transparent – project discussions, plans for new features and other artifacts are open, public, and accessible

Meritocracy – Archi development is a meritocracy. Roles are merit-based and earned by peer acclaim.

Liberal licensing – Archi’s code has a liberal open source licence, the MIT licence. It means that anyone can take the code and build a commercial product based on it.

Available – There will always be an open source version of Archi

Elegance – We believe in elegant and simple design. Archi is agile, intelligent and lightweight.

Who are the main committers?

How is Archi licensed?

Who decides what features are added to Archi?

Dependent on governing factors:

Users

Phil Beauvoir

Jean-Baptiste Sarrodie

Any valid feature proposal is considered. Phil Beauvoir is the technical design authority who, guided by users and Jean-Baptiste Sarrodie, makes the decision on whether a feature is valid and should be incorporated into the Archi product.

The development process is:

Open

User driven

Dependent on resources

What is the process for feature development?

All changes to Archi are reviewed and have to be approved. The process revolves around the project presence at GitHub. Approval is subject to developer resources, and whether the feature is implementable and maintainable.

If a feature is a user request, or it is a bug report, the code has to be implemented by Phil Beauvoir or Jean-Baptiste Sarrodie. This means the feature/bug may or may not be implemented depending on time, resources and developer inclination.

User Pull Requests (PR) can be made via the Git mechanism available on GitHub: