The Community consists of all users of the EasySDI solution. Users are independant and their participation in the project is voluntary based. Each user is free to use EasySDI code in respect to its GPL V3.0 licence.
Within the EasySDI project the following kinds of roles are recognized:
-> Users download, install and use EasySDI components where Users typically contribute to documentation or configuration
-> Developers are people able to apply changes to the EasySDI source code
-> Committers are allowed to commit artefacts to the EasySDI code repository
The Project Steering Committee is a small group of individuals who are responsible for all organisational and strategic aspects of project management
The remainder of this document contains more detailed information about these groups or structural entities.
2. Community detailed description
Users are individuals or institutions who download, install and use EasySDI components. They can contribute to the Community with forums posts, tutorialsand documentation writing, funding work, etc.
Developpers are individuals or institutions who are able to apply changes to the EasySDI source code and submit patches .
Committers are individuals from the Developers groups who are allowed to commit artefacts to the EasySDI code repository.
Commit rights are granted upon request by the PSC. Individuals who already have contributed significant resources to the project may apply for commit rights. The prior commitment is usually shown by regularly submitting code that conforms to the current é EasySDI development best practices é and by involvement into the discussions at the developer and user list.
Project Steering Committee (PSC)
The Project Steering Committee is a small group of individuals who are responsible for all organisational and strategic aspects of project management.
PSC consists of individuals recognized for their competences or dynamism within the Community. The PSC decides about the major directions of the EasySDI project, the roadmap and the Committers. All decisions made by the PSC are either made in consensus or based on a single majority. The PSC usually meets online once a month and physically once a year in person.
Responsibilities of the PSC include:
-> setting the overall development road map
-> ensuring regular releases (major and maintenance) of EasySDI solution
-> overall technical aspects and strategic choices of EasySDI solution
-> project infrastructure (e.g. SVN, Mailing Lists, Wiki, Tracker, hosting options, etc...)
-> formalization of affiliation with external entities
-> setting project priorities, especially with respect to project sponsorship
-> creation and oversight of specialized sub-committees (e.g. project infrastructure, training)
-> vote on PSC membership