**All submissions are now managed through the HCDP Github page**
When we launched the Hydro Community Development Program (HCDP), we aimed to have a different and inclusive approach to community engagement. The program has been a success and — thanks to ongoing feedback from our community — we are making it even better. We are re-positioning HCDP to be more open and decentralized.Any member of the Hydro community can create HCDP tasks to be completed by others. It is the responsibility of the task creator to define the task clearly, enumerate deliverables, manage submissions, and send out HYDRO allocations upon successful completion. Members of the community will also be able to become admins to contribute more to the program over time.
The tasks eligible for HCDP fall under 2 general categories: Development and Document Translations. Let’s take a look at what each entails.
This section is dedicated to tasks regarding the expansion of the Hydro technology ecosystem internally (dealing with core Hydro code) or externally (extending or implementing Hydro code). Below are some examples of Development tasks.SDKs & Code LibrariesCode interfaces are important, as they ease the integration of Hydro into existing systems and applications. Tools like these, which enhance the usability of the Hydro ecosystem, are great outcomes for HCDP. For reference, we have released JavaScript and Python SDKs for our Raindrop products:
Bugs & Code Improvements
Finding and diagnosing bugs is a critical part of code development. While core developers strive to ship code that is bug-free, the reality is that some edge cases may not be accounted. As more and more people implement Hydro technology, bug discovery under HCDP will play a key role in fostering a healthy ecosystem and maximizing user experience.Integrations & ExpansionsWhile SDKs and Code Libraries facilitate processes within the Hydro ecosystem, integrations and expansions broaden the ecosystem as a whole. An example of this might be a wrapper that connects Hydro smart contracts to systems. For example, this C# wrapper was created by a community member.
Security Reports
HCDP can also include security reports and audits. Since Hydro is integrated into systems that may hold or transmit sensitive data, vulnerabilities can be catastrophic. Whenever new Hydro code is released, security analyses are instrumental in shoring up any potential holes — the more eyes on the code, the better it will be for the entire community. A good example of a security report would be a smart contract audit.
Document Translation
This section will be dedicated to community members who prefer to read our materials in their native language. Hydro strives to make it seamless for developers to incorporate blockchain into their apps, and in order to achieve that goal we need to eliminate as many barriers as possible. Language is a key barrier to be addressed, especially for our community since it spans dozens of countries around the world. HCDP task creator can call on the community to help make documents easier to read, which in turn helps more and more people leverage the Hydro ecosystem. Some examples of documents are:
We hope that community members will also form sub-communities that can more easily communicate in various native languages! All submissions must be made on the HCDP Github page. We’re excited for this evolution of the Hydro community, and we can’t wait to work with developers, product managers, and others in the coming months!
For those interested, the original HCDP post is available here.
