The IOTA Experience Team will operate transparently, openly, collaboratively, and ethically. Project proposals, timelines, and status must not merely be open, but also easily visible to the entire ecosystem.
Membership is for 6 months. The group will ask on a regular basis if the expiring members would like to stay on. A member just needs to reply to renew. There is no fixed size of the IOTA Experience Team. However, the expected target for Advisors, as defined in Section 6, is between 9 and 12, to ensure adequate coverage of important areas of community expertise, balanced with the ability to make decisions efficiently.
There is no specific set of requirements or qualifications for IOTA Experience Team membership beyond these rules. The IOTA Experience Team may add additional members to the IOTA Experience Team by a standard IOTA Experience Team motion and vote. A IOTA Experience Team member may be removed from the IOTA Experience Team by voluntary resignation, or by a standard IOTA Experience Team motion.
Changes to IOTA Experience Team membership should be posted in the agenda, and may be suggested as any other agenda item.
No more than one-fourth of the IOTA Experience Team members may be affiliated with the same employer or leadership of a community/ecosystem organization. If removal or resignation of a IOTA Experience Team member, or a change of employment by a IOTA Experience Team member, creates a situation where more than one-fourth of the IOTA Experience Team membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more IOTA Experience Team members affiliated with the over-represented employer(s). IOTA Foundation members excluded.
The IOTA Experience Team members shall consist of active members of Community Projects.
The IOTA Experience Team may, at its discretion, invite any number of non-voting Guests to participate in the public portion of IOTA Experience Team discussions and meetings.
The IOTA Experience Team shall meet regularly using tools that enable participation by the community (through any appropriate means selected by the IOTA Experience Team). Minutes or an appropriate recording shall be taken and made available to the community through accessible public postings.
IOTA Experience Team members are expected to regularly participate in IOTA Experience Team activities.
In the case where an individual IOTA Experience Team member -- within any three month period -- attends fewer than 25% of the regularly scheduled meetings, does not participate in IOTA Experience Team discussions, and does not participate in IOTA Experience Team votes, the member shall be automatically removed from the IOTA Experience Team. The member may be invited to continue attending IOTA Experience Team meetings as a Guest.
Subject to such policies as may be set by the IOTA Foundation, the IOTA Experience Team is responsible for cultural development and outreach within the IOTA Project, including:
- Outreach to community organizations
- Documentation of community organizations
- Recommendations for building and developing community projects that align with needs of IOTA
- Support the develompent team with code samples
- Enhance the official documentation
- Actively participate with feedback
- Discuss and engage with the community developers
- Actively develop of proof of concepts
- Being a developer advocate
- Create a list of RFP’s for the EDF to fund Open Source development
The IOTA Experience Team will establish and maintain a process of support for IOTA community projects. The process will establish guidelines for how culture and values of the community can be supported.
The IOTA Experience Team and entire technical community will follow any processes as may be specified by the Board relating to the intake and license compliance review of contributions, including the IOTA Foundation's IP Policy.
The git repositories for the IOTA Experience Team and its initiatives are maintained by the IOTA Experience Team and additional Collaborators who are added by the IOTA Experience Team on an ongoing basis.
Individuals making significant and valuable contributions, “Contributor(s)”, are made Collaborators and given commit-access to the project. These individuals are identified by the IOTA Experience Team and their addition as Collaborators is discussed during the weekly IOTA Experience Team meeting. Modifications of the contents of the git repository are made on a collaborative basis as defined in the development process.
Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the IOTA Experience Team for discussion by assigning the cc-agenda tag to a pull request or issue. The IOTA Experience Team should serve as the final arbiter where required. The IOTA Experience Team will maintain and publish a list of current Collaborators by Project, as well as a development process guide for Collaborators and Contributors looking to participate in the development effort.
- Contributors: contribute code or other artifacts, but do not have the right to commit to the code base. Contributors work with the Project’s Collaborators to have code committed to the code base. A Contributor may be promoted to a Collaborator by the projects’ Maintainer or the IOTA Experience Team. Contributors should rarely be encumbered by the IOTA Experience Team and never by the Board.
- Project: a collaboration effort, e.g. a subsystem, that is organized through the project creation process and approved by the IOTA Experience Team.
- Community Project: projects within the IOTA Foundation or in the IOTA Ecosystem that contribute to the health of the IOTA project.
- Advisor: a Collaborator within a Community Project elected to represent the Community Project on the IOTA Experience Team.
- Member: a Collaborator who has met the requirements of participation to be considered for acceptance, and subsequently voted in by the IOTA Experience Team voting process.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in all IOTA Experience Team documents are to be interpreted as described in RFC 2119.
For the current list of IOTA Experience Team members, see the project README.md.