Community policy

In our project, we as maintainers of Hyperledger Iroha want to create a friendly environment for the contributors, who are suggesting changes to code or documentation, process or tools — whatever needs an improvement to get better in your opinion. These suggestions are very valuable for us as they show the product from a different perspective, and in this case, we can have Iroha which suits everyone.

In order to create such environment, we are performing following actions as the part of our process:

Inform the community about recent changes in the project

This includes (but not limited to) the following:

• release notes
• tasks selected for next iteration
• new requirements to be implemented
• new challenging and good first-time issues
• new members of maintainers team

Collect suggestions for improvements and defects found in a formal way

Previously, having no or limited process on how to handle suggestions for improvement from contributors or defects found led to ambiguous status of such work. Also, having no structure for change request documents was not helpful for the team of maintainers — as they were spending their time to clear things up and sometimes the communication was not fruitful. To overcome this, we are starting with:

1. Collection of change requests via GitHub issues.
2. Development of lightweight process, which includes statuses and requirements for transitions between such statuses.
3. Set of document templates and examples for them.
4. A bot which will check conformance to the process and docs (optional).

Progress weekly sessions with the community (Iroha Dev meeting)

Such meetings include informing contributors and newcomers about current progress, help to answer questions related to development tools, process, and Hyperledger Iroha as a whole. The schedule and agenda are posted on each Monday, defacto including Q&A in each session.

Tools used

To stay in touch with a diverse community of developers we are using:

• Gitter.im
• Telegram chat
• Rocket chat of Linux Foundation
• Mailing list
• Zoom.us and hangouts for Iroha Dev meeting

Community manager

Among the maintainers' team a person, who is in charge of tracking the progress of all the activities listed and in charge of the strategy of working with the community, is selected by voting of maintainers team. The results of the voting are posted in channels updated here in the policy.

Title	Data
Name	Bulat Nasrulin
GitHub profile	@grimadas
e-mail	[email protected]
Chats	telegram - @grimadas