You can find out who's contributed recently just by looking at GitHub's contributors list. But there are a few more things you ought to know about who maintains this code, and how they do it:
- Make sure you read our contributor guidelines so you understand how we work and how to collaborate effectively. This includes instructions about pull request and code review protocols, and it explains what we mean by calling someone a "maintainer" in this file.
- Be aware that individual folders in the project may have more
specific maintainers; if you see another
MAINTAINERS.mdin a subfolder, that governs the tree below it. - A lot of interactions with maintainers take place on Jira. You'll need Linux Foundation credentials to comment there; creating them is self-service. The project name you want, once in jira, is "IS".
- The other important communication mechanism to know about is Rocket.Chat.
Again, you use your Linux Foundation credentials. Most of the team hangs out
there during their work day; look for
#indy-hipe,#indy,#indy-pr-review, and so forth. - We use developer certificate of origin (DCO) in all hyperledger repositories, so to get your pull requests accepted, you must certify your commits by signing off on each commit. More information can be found in Signing Commits article.
For ordinary questions, we suggest you contact active contributors
generically, on rocket.chat #indy-hipe. If that doesn't get someone's attention,
feel free to contact the contributors individually.
Maintainers are busy and delegate many decisions to other trusted contributors. However, it is appropriate to contact them if you have a complex design decision or a controversial PR.
- Daniel - maintainer . geo=Utah, USA; github=dhh1128, rocket.chat=danielhardman, jira=dhh1128
- Nathan - maintainer . geo=Utah, USA; github=nage, rocket.chat=nage, jira=nage
- Sam - maintainer . geo=Idaho, USA; github=telegramsam, rocket.chat=telegramsam, jira=TelegramSam