thanks for feeding back - it's very much appreciated. And thanks also to Nicola and Paul for responding.
It's good to reflect upon you saying you're not quite sure how to get involved. I imagine this is probably true for many people in the community, especially for those new to open source. I wanted to offer my thoughts below:
Using Adapt / following what's going on
This is the foundation stone to us thinking of the project as successful. The more people use Adapt, the happier we are. Our aim is to make the Adapt Framework a global, industry standard for producing responsive e-learning.
As Paul said, we're aiming at non-technical end users who have an interest in Learning & Development and this audience will be engaged more and more, especially when we're making our first authoring tool release this year. The current tools are relatively easy to use but we're being careful about managing expectations and until the authoring tool is out. The framework is mainly aimed at developers / semi-technical people.
Telling others about us
If you feel in any way supportive of our efforts, please tell others and share the link to this community site. It's really helpful to us and we're committed to supporting anyone who arrives here and wants to use Adapt.
We know that supporting the end users in the community is hugely important and the entire core team as well as experienced community members are on the case to help quickly and in a friendly way.
We consider anyone who tells the world about Adapt an 'ambassador' for the project and we really love those of you who spread the word.
Telling us about what you're doing / what you like and what could be better
As you are working with Adapt, you might have questions, ideas, improvement suggestions, find bugs/issues etc. Please tell us either via this community forum or - if you already know it's a software bug - via our bug tracker in Github.
We also love hearing about the projects people are doing with Adapt. I think it's fair to say that for the entire community. The more examples we see, the better our own work gets and the more we can feed ideas and enhancements into the core product. We also really appreciate small notes of encouragement - thank you for yours!!
Help answer other community members' questions
You might know an answer or have some thoughts to add to the posts here. We really appreciate when community members help other members and do so in a friendly way.
Help us test
Every now and then, we ask the community for pre-release testing. While we have thorough development processes (peer review and professional testing e.g. by the collaborators test departments) in place, community testing really helps according the the open source mantra which goes something like 'the more eyes, the shallower the bugs'.
Feed back on the user interface design work
Granted we're a little overdue in sharing our interface latest design work but we're due to publish it before the end of this month and we're keen to get feedback for you. We want to produce an easy to use tool with great functionality. The functional requirements are written down in this document and will be delivered as time goes on. The UI design work is trying to translate this into a great and intuitive interface.
Help with the documentation effort
This starts with pointing out what's missing or unclear and goes all the way to writing documentation yourself. If you feel this is something you can do please just get in touch and the core team will support you in getting it right etc.
This is really only for developers - the Adapt Framework has a plug-in architecture and it should be very easy to add functionality. Any plug-ins can be registered with the Adapt registry, which makes it really easy for anyone to install and use these plug-ins. Most of this is currently done via the command line and we're working on a web UI for this, too, to make it easier to browse.
Help us shape the roadmap
As Paul says, this will become much more active in terms of discussion and visibility. We've only just put up the roadmap page and it's in flux as you might expect. We're really keen to hear what features and functions the community would like to see and would love a discussion about priorities.
Join the team and become a collaborator
As and when you feel you really believe in the project vision and would like to join the team and become and official part of the project, please let us know. There are some definitions on our governance page.
The big difference between contributors and collaborators is that collaborators make time available and work under the guidance / direction of the project leadership, as opposed to 'doing their own thing and sharing it'.
Unlike many other 'young' open source projects, the core team work in a very structured way and we prioritise and assign tasks to team members in order to progress towards the vision.
Anyone can become an official collaborator, whether they are organisations or individuals. Please just get in touch if this is of interest. We have an onboarding process to help new members to get up to speed.
Help us shape the project
There are a number of factors, which shape the project. These are (in no particular order):
- The vision
- The community (we really do listen)
- The people on the steering group (see governance structure page)
This project is set up as a meritocracy and that means that anyone who commits a significant level of time and energy on an ongoing basis, achieves good results on behalf of the project and helps the project progress can be invited into the steering group and help shape the project, the strategy etc.
There is probably lots more to say about how you can get involved. I hope this gives everyone a general idea and encouragement.