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

Compare with Current View Page History

« Previous Version 4 Next »

The Hyperledger India Chapter is responsible for growing the Hyperledger developer community in India by responding to new user questions, helping with first-level triage of community-reported bugs or other issues, helping demonstrate to new developers how to report bugs or file pull requests, and pointing motivated developers towards the project roadmaps and development initiatives at the global Hyperledger web sites.

It should also make sure to expose new users to the broad range of projects at Hyperledger and drive participation in these projects. Given the time zone differences, it should act as a bridge between the Hyperledger projects and the local community.

Get Involved

Participation in this group is open to anyone who is interested in this topic.  To get involved with the Hyperledger India Chapter, please feel free to join the discussion on these channels and meetings:

Work Products

The anticipated initial work products will include (but is not limited to):

  • Help promote the adoption of Hyperledger projects and technical exchange & collaboration among them.

  • Guide and drive technical involvement including code contributions, tutorials and project proposals.

  • Help organize technical events including hackathons/hackfests, meetups, education and training.

  • Proxy meetings of Hyperledger Technical WGs in a Geo Friendly time.

  • Promote and drive technical communications through email-list, Slack/chat, forums, etc.

Regional Leads

The leaders of this Chapter are:

  • Amol Kulkarni, Sr. Security Architect & Head of Engineering, Blockchain Program Office at Intel India
  • TBD

Collaborating with other groups

This Working Group will collaborate with other Hyperledger working groups, the TSC, Linux Foundation staff, and the project maintainers.  Julian Gordon and David Boswell will be the main staff points of contact for the group and will be available to make sure this group is plugged in where needed and is not duplicating efforts.



  • No labels