The IOTA Experience Team is a high level team composed of community members and IOTA Foundation employees who focus on community-facing accessibility efforts surrounding IOTA technologies.
For more details read the [IOTA Experience Team Charter].
Sustainable open source software is always, first and foremost, a community effort. By its very nature, the health of every project in this domain has as much to do with those consuming the code as it has to do with those maintaining it.
At the IOTA Foundation, we want to open up a feedback loop between our internal development teams and, you, the amazing people doing wonderful things with the protocol. By bringing some of the “real world” back into the development processes, the vision is to offer the opportunity for you to become intimately involved in preparing software for its transition from Alpha to a Full Release.
As a member of the IOTA Experience Team, you won’t be met with demands or endless formalities. By participating in this IOTA Experience Team, you will be empowered to speak as a voice for the community and guide development processes. And at the end of the day, you will have helped yourself, the IOTA Foundation and the whole community to more solid, intuitive, and useful technologies.
code commits !== the only means to contributions.
The IOTA Experience Team is tasked with growing and sustaining the IOTA Community. If you're reading this, you're already a part of that community and we'd love to have your help!
Before you get started, here's a broad outline of the IOTA Experience Team's governance structure:
- IOTA Experience Team: meta-level admin concerns, cross-cutting with other groups and Working Groups
- Initiatives: focused on specific tasks, independent from the IOTA Experience Team but sharing what they're doing in IOTA Experience Team meetings.
As seen here, most of the community work that immediately affects the project is done within the numerous initiatives. We recommend checking the list of initiatives below and getting involved with one that you find interesting! If nothing suits your fancy and you have concrete ideas, open an issue here! We can help to point you in the right direction.
To get started with contributing, you should read the Contributing Guidelines document. This document details the roles you can take on. It also includes a guide to contributing and links to
good first issues where we're looking for help.
If you're interested in participating in the IOTA Experience Team directly, you're more than welcome to join via the Jitsi link posted in our meeting issues.
IOTA Experience Team meetings are broadcast via Jitsi. The join link is published in the meeting's respective issue. Meeting times are coordinated to optimize for contributor timezones.
(last survey April 2020)
Initiatives are projects that the IOTA Experience Team and the broader community members are collaborating on to enable IOTA across the ecosystem.
At any one time the IOTA Experience Team has a number of strategic initiatives underway. With the less-tangible approach to the work that the IOTA Experience Team does, having a way to track this work is important.
For each strategic initiative, the IOTA Experience Team's goal is to have a single point of reference - a champion - that understands what's happening with the initiative to the fullest extent possible, and can report on the initiative as needed.
A review of the initiatives will be a standing item on the IOTA Experience Team agenda (even if the update is 'nothing new') as a way to ensure they are active and have the support needed.
|IOTA Client Lib Experience||https://github.com/iota-community/X-Team_IOTA_Libraries|
|IOTA Access Experience||https://github.com/iota-community/X-Team_IOTA_Access|
|IOTA Smart Contracts||https://github.com/iota-community/X-Team_IOTA_SmartContracts|
|IOTA Streams Experience||https://github.com/iota-community/X-Team_IOTA_Streams|
|IOTA Client Lib Experience||?|
|IOTA Identity Experience||?|
|IOTA Smart Contracts Experience||?|
|IOTA Streams Experience||?|
In an effort to be more concise and distribute our knowledge, we do our best to use labels on issues to give context on their status. Here's a guide to how we use labels:
initiative-prefix: Belonging to or about an initiative that follows the prefix.
waiting-on-prefix: This indicates that we're waiting on a group for input/feedback.
type-prefix: Denotes what kind of discussion is happening – a request, an open discussion, a problem, etc.
-agendasuffix: Denotes that an issue will be included in the agenda of the initiative or WG pririor to the suffix.
good-first-issue: Issues that are a good place to start contributing to the IOTA Experience Team
mentor-available: Issues that have a mentor available to help out
The IOTA Experience Team is a team that collaborates alongside the IOTA Foundation. See the [IOTA Experience Team Charter] to learn more about the group's evolving structure and CONTRIBUTING.md for guidance about the expectations for all contributors to this project.
Based on all-time SourceCred scores.