Our guiding principles
Everyone is welcome.
The following guidelines are some of the things we felt worth highlighting. When signing up to the community, you are also signing up to the principles below.
The code and authoring tool will be free
We will release the code and authoring tool under the GPL v3 license.
We produce stable, high-quality code
We recognise the importance of stable software, which has as few bugs as possible, and endeavour to produce very high quality code. This includes establishing and following quality coding standards, peer review processes, building in unit tests and thorough testing cycles using both the professional testing teams in the collaborating organisations and the Adapt community.
We are work towards the vision
Over time there will be opportunities (and maybe even pressures) to diverge away from the vision statement. We would like everyone to help this project stay focused on the vision and help to achieve it. This includes reminding and politely challenging people in the community, especially those who are looking after the core code.
Should you be invited into a decision-making role, we expect that by accepting you are signing up to the vision statement and will consider this in any decisions you have input to. To help with this, we have broken down the key strategic considerations and how they apply by defining a number of hats people could ‘wear’. More information about this can be found on our governance page.
We are open, honest and friendly
We would expect everyone does this naturally, and it's really a no-brainer, but it deserves a mention regardless as one of our core values. We would like everyone to remember that we are dealing with real people and that we want to welcome them. We would like everyone who signs up to feel like they can ask anything related to this project.
As part of this, we will be open and honest about where we are at, any shortcomings and things we are and are not planning or able to achieve given the circumstances. We always aim to explain the reasons as part of our responses.
We will also point out and tackle unacceptable behaviour.
All discussions are to take place in the open and on the forums of this site
We avoid having private discussions. The value of discussing things in the open is that we will be more likely to achieve consensus, make better decisions and that in doing so, we are also building up a knowledge base, which anyone (especially newcomers) can refer to.
The only exception to this is the quarterly steering group meeting. The agenda of this focuses on reviewing progress, strategic issues and opportunities, finances and funding, the running of our systems and the governance structure and appointments. This also includes considering nominations for promoting Community Members to Collaborator or Steering Group Member status as well as considering un-invitations in exceptional cases.
We are quick to respond
We sign up to responding to queries and posts promptly. This can make all the difference in us being able to build and retain thriving developer and user communities. It may also make all the difference in terms of attracting funding into the project.
We stay focused on learning
While our work may well apply to the wider web community, we are committed to the vision of building a leading responsive e-learning design framework and authoring tool in order to serve a learning-related purpose.
We drive for a low barrier to entry
In order to be able to achieve a market leading position, we need to be mindful of the barrier to entry at all times and for all types of users. This includes good documentation, a plug-in architecture for developers, an intuitive and easy to use interface for end users and a responsive and helpful community.
We consider documentation as being very important
In line with the point above, we consider documentation as very important part of the project, which helps keep a low barrier to entry. We therefore commit to create clear and sufficient documentation quickly.
We aim for ease of use for a non-technical audience
We consider ease of use and intuitive user interfaces of key importance. We commit to considering the end users, seeking their input and following best practice in user interface design.
We reward significant and continued contributions with influence over time
The project is set up as a meritocracy. As such, we are open to inviting contributors into the leadership structure if their commitment, contributions and behaviour warrant it.