-
Notifications
You must be signed in to change notification settings - Fork 7
Governance
Role: Project Lead - Veiko Aunapuu Responsibilities:
- Setting project goals and milestones.
- Coordinating communication between team members.
- Making final decisions in case of deadlocks.
Role: Technical Lead- Martynas Karobcikas Responsibilities:
- Guiding technical decisions and ensuring alignment with project goals.
- Reviewing and approving code contributions.
- Coordinating with contributors on technical matters.
Role: Community Manager - Veiko Aunapuu Responsibilities:
- Encouraging community participation and contributions.
- Managing communication channels (forums, mailing lists, etc.).
- Resolving community-related issues.
- Liaising with the sponsoring organization to secure resources.
- Allocating resources for project needs.
- Ensuring efficient resource utilization.
Active project members:
- Veiko Aunapuu, Baltic RCC (with voting right)
- Gintautas Poderys, Baltic RCC
- Matīss Kļaviņš, Baltic RCC
- Martynas Karobcikas, Baltic RCC
- Margus Rätsep, Baltic RCC
Decision-Making Process: Collaborative Decision-Making: For most decisions, a collaborative approach should be encouraged, involving input from all team members with voting rights. Major Decisions: In cases where a major decision needs to be made, a simple voting system can be implemented, with each member having an equal vote. The Project Lead serves as a tiebreaker if needed. Transparency: All decisions and discussions should be transparent and documented for the benefit of the community.
Resource Allocation: Resources provided by the sponsoring organization should be allocated based on project needs and priorities. Regular communication with the sponsoring organization to provide updates on resource utilization and project progress.
Communication: Regular team meetings to discuss progress, challenges, and upcoming tasks. Open and transparent communication with the community through public forums and mailing lists. Main communication channels are:
- For development daily standups is being organised by technical lead
- Goal review and sprint priority review bi-weekly calls
- Open milestone review (quaterly) for non-project members is notified via emailing list.
To be added to any communication please contact us via: veiko.aunapuu@baltic-rcc.eu or kristjan.vilgo@baltic-rcc.eu
Review and Adaptation: Regularly review the governance structure and make adjustments based on the evolving needs of the project and community. This structure provides a balance between centralized decision-making, community engagement, and resource management. Adjustments can be made based on the specific needs and dynamics of the project. Review and update of governance shall be discussed at every Open Milestone review meeting (quaterly)
Non-members can contribute by using the project's code and reporting issues. Code Usage:
- Clone the repository to your local machine: git clone https://github.com/Baltic-RCC/EMF.git
- Integrate the code into your project as needed (note the README for stack requirements https://github.com/Baltic-RCC/EMF/blob/main/README.md)
- Respect the project's license and include proper attribution.
Issue Reporting:
- Check existing issues to avoid duplicates.
- Open a new issue with a clear title and description.
- Include relevant details, such as operating system, version numbers, and steps to reproduce the issue.