FOCUS Governing articles
FOCUS Community
[foh-kuh s] ~ “a central point, as of attraction, attention, or activity”
Fisheries Open sourCe commUnity Solutions
Executive summary
FOCUS is a community dedicated to raise the technological awareness amongst fisheries organisations and as a consequence contribute to the sustainability of the fisheries resource. We believe that sharing information is a pillar of the platform needed to perform efficient fisheries management.
This paper outlines the governing articles for FOCUS community.
Scope
The scope of FOCUS encapsulates the main functions to manage, maintain open source artefacts and standards, to propose new shared projects, to support its sponsors and to promote and engage the community.
Vison
The FOCUS aspire to the following vision statement.
“To be the global reference for standards and innovative open source solutions for sustainable fisheries management “
Mission
The FOCUS Mission statement sets the boundaries and scope of the context in which we work, in order to get us where we want to go (vision).
“We facilitate, coordinate and promote the sharing of standards and open source fisheries management solutions as a collaborative community”
Principles
The FOCUS principles is meant to act as guidelines when opposite interests or opinions occurs within the community.
Name | Description |
---|---|
Open | We choose open source software first |
Free Open community | Anyone can be part of our community |
Legal | We are guided by and respect legal framework related to our context |
Standard first | Our preferred option is to adhere to existing standards first |
Transparency | Our decision making process is transparent, honest and open. |
Efficiency | We reuse what exist and design for reuse. |
All efforts are good | Not everyone is a developer but contributions are always appreciated, no matter form. |
Trustworthy | Say what you do, do what you say |
Generic solutions first | A generic solution is more reusable then a specific one. |
Business drives | Development is performed after a business need has been identified. |
Collaboration | We believe collaborate efforts are worth more than results from a solitary process. |
Organisation
FOCUS is organized and managed by a board [The Community Board]. The Community Board are custodians of the Community. The Community Manager is responsible for the day to day management of the FOCUS Community. FOCUS divides its work in different projects/interest groups. Each project/interest group has a different contextual focus and should have a natural separation from other projects/interest groups e.g. standardisation, open source software etc. A project/interest group is managed by a Project/Group Lead.
Election
The general principal for being elected to a specific role within the Community is by merit. In this sense FOCUS promotes a meritocratic philosophy.
Community Board
The Community Board draw nominations from interest countries and organisations to join the Board. Beside showing dedication and commitment to the Community a board member must have extensive experience related to fisheries management. A Community Board member needs to contribute and play an active role.
Community Manager
The Community Manager is elected from and by the Community Board.
Project/Group lead
Project/Group leads are agreed by the Community Board and the Community Manager.
Committer
Committer are appointed by the Project/Group leads and are authorized to commit updates to shared artefacts.
Contributor
Contributors are users of the Community that are recognized for their contributing work.
User/member
Anyone can become a user/member of the Community.
Voting
The community governance is centred on a Community Board elected by the FOCUS Community that is designed to represent the views and decisions of the Community whilst also providing leadership to support the needs and promotion of the Community. The Community Board is comprised as follows:
- The Community Board is elected by the Community and consists of 10-12 members to serve a three year term.
- The Community Board manager is selected by the board to serve a 1-year term based on his/her ability to address the current needs of the Community.
- Community Board members elected by the community are voted upon by organisations contributing to the community or adopters of products developed by the community.
- Community Board members must provide sufficient notice to the Board when they wish to stand down from their role.
Actions and activities
This section contains a proposal on activities related the identified actions.
Planning
Activity | Action | Owner |
Planning | Establish and define annual and 3 year plan/roadmap. | Board |
Planning | Structure, roles and responsibilities | Board |
Planning | Review plans | Board + externals(Audit) |
Govern
Activity | Action | Owner |
Govern | Aligning deliverables with roadmap/vision | Board |
Govern | Document and implement a version control strategy for managed artefacts. | Board |
Govern | Agree/document a Taxonomy (Terminology) | Board |
Govern | Maintain member list with contact details | Manager |
Manage
Activity | Action | Owner |
Manage | Coordination between projects | Manager |
Manage | The releases needs to be managed | Manager + Project lead |
Propose
Activity | Action | Owner |
Propose | During meetings, new business needs need to be identified | Board |
Propose | Proposals are documented on a “Wiki” like page by category | User |
Propose | Presented by Manager to board. Decision by board | Manager + Board |
Propose | Other projects can be included in FOCUS by this process |
|
Propose | Before proposing a new project this process needs to make sure the proposal is viable and achievable | Manager + Board |
Evaluate/Govern
Activity | Action | Owner |
Evaluate | Other projects can be included in FOCUS by this process | Anyone can offer artefacts to FOCUS |
Evaluate/ Govern | Agree on a UAT and peer review process. | Manager/Project lead |
Evaluate | Presented by originator evaluated by Board/Manager | Manager/Board |
Evaluate/ Govern | Test procedure needs to be documented. Automated test, test environment | Manager/Board |
Support
Activity | Action | Owner |
Support(User) | A forum needs to be established | Manager/Project lead |
Support(User) | Private support should be possible |
|
Support(User) | Participants collaborate to provide support | FOCUS User |
Support(Sponsor) | Communication, coordination with sponsors (meeting, email-updates) | Manager |
Support(Sponsor) | Give presentations in conferences | Manager |
Promote/engage
Activity | Action | Owner |
Engage | Monthly board meetings during initiation phase. Thereafter quarterly. | Board and Manager |
Promote | Info/updates on social media (tweet), meet-ups, mail list | Manager + Project Lead |
Promote | To promote the existence of FOCUS | Board and Manager |
Promote | Develop standard presentation/document material | Manager |
Promote | Identify forums, events etc. to participate in | Manager |
Engage | Organise yearly meeting(s) to: * review the existing governance processes and ensuring the defined processes are serving the community well or enhancing processes to improve results * updates on projects, their status and progress * review product roadmap and discuss project vision * align community and priorities * discuss future development and collaboration opportunities | Board |