You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Many of our community members wish to show their support for Hyperledger by identifying themselves as members of the community in their profiles on social media and their email signatures and even business cards. This page identifies the different roles in our community and provides guidelines on how to accurately represent yourself in your communications. In general, the rule is to be as specific as possible so that you don't confuse people about your role.

Community Roles

Everybody!!

First of all, everybody involved in the Hyperledger community, no matter how small of a contribution or the form of the contribution, can and should proudly identify themselves as a Hyperledger Contributor. Showing up to, and participating in, community meetings is a contribution. Editing the wiki is a contribution. Replying to an email in one of our mailing lists is a contribution. Reporting a bug or asking a clarifying question about our documentation is a contribution. Submitting a patch is a contribution. Attending one of our community events or meetups is a contribution. If you are reading this, it is likely you have made a contribution to the Hyperledger community. Thank you.

Hyperledger TSC Chair, Vice Chair, and Members

This group consists of the elected members of the Hyperledger Technical Steering Committee. There is one Chair and Vice Chair elected from the committee membership. When identifying yourself, please use "Technical Steering Committee" and your role. Abbreviating "Technical Steering Committee" as "TSC" is acceptable. All of the following are acceptable:

  • Hyperledger Technical Steering Committee Chair
  • Hyperledger Technical Steering Committee Vice Chair
  • Hyperledger Technical Steering Committee Member
  • Hyperledger TSC Member

Hyperledger Special Interest Group/Working Group Chair, Vice Chair, and Members

Members of Hyperledger special interest groups (SIGs) and working groups (WGs) may identify themselves using the name of the SIG/WG along with their role. As with the technical steering committee titles above, it is OK to abbreviate special interest groups and working groups as SIG and WG respectively. All of the following are acceptable:

  • Hyperledger Capital Markets Special Interest Group Member
  • Hyperledger Smart Contracts WG Chair

Hyperledger Project/Labs Maintainers and Contributors

The people involved in our various open source software projects should identify themselves using the name of the project and their role in the project. All of the following are acceptable:

  • Hyperledger Fabric Maintainer
  • Hyperledger Ursa Developer
  • Hyperledger Umbra Contributor

Hyperledger Mentees

Each year we have a group of students that contribute as mentees and community members that contribute as mentors on our various mentorship programs. They should identify themselves using the year and role. Optionally, the name of the project may be included. All of the following are acceptable:

  • Hyperledger 2020 Mentee
  • Hyperledger 2019 Mentor, Git Commit Signing with DIDs

Conclusion

As stated in the introduction, the goal is for all of us to clearly communicate our roles in the community so that everybody can gain from their affiliation with Hyperledger in an honest and open way.

  • No labels