Ontology Provides Clear Guidelines For Community Technical Contribution

Ontology has provided guidelines for contributions by community members. The guidelines are basically the standard that every member wishing to make a “technical contribution” will need to abide by. According to Ontology “technical contribution” refers to…

  • the Ontology Enhancement Protocol or OEP,
  • the development as well as submission of dApps and the
  • creation of codes.

Ontology makes it clear that “technical contribution” does not refer to document translation, the organisation of community events or efforts made by members towards the management of the Ontology community.

In order to ensure that members engage in collaborative efforts, Ontology encourages the formation of community groups. Members can work together on the creation of a dApp and submit it as a group or they can work on their own if they choose.

However, Ontology would only be open to discussion with one elected member of a group. It is this member that will be responsible for any correspondence from the group to the Ontology Council or technical committee.

All technical contributions made either by individual members or by groups within the community will be indexed by Ontology. The purpose of indexing is to make sure that anybody in the community including investors can fully appreciate the contribution made.

If you want to peruse the full Ontology technical contribution guidelines, you can click here. For instructions on how to upload your technical contribution to the Ontology community, you can click on this link.

Ontology Will Compensate Contributors

If you thought that your technical contribution would go unrewarded, you thought wrong! It is the intention of Ontology to incentivise all technical contributions in order to encourage continual contributions from its community members towards the enhancement of the Ontology ecosystem in the provision of value driven business based dApps. What you should know is that the level of compensation each contributor receives is determined by the value such a technical contribution adds to the Ontology ecosystem.

Every contribution is assessed and evaluated by the Ontology Technical Committee with the Ontology Council giving their seal of approval on the compensation to be made to contributors for their submitted dApp or code. However, in order to ensure that the compensation given for a technical contribution is fair, Ontology will consider the following;

  • The time spent in developing the technical contribution.
  • The complexity of the technical contribution.
  • The level of expertise of the contributors.
  • The number of team members involved in the contribution especially if it’s by a group.
  • The level of technological requirement for the completion of a technical contribution.
  • The technical contribution architecture and design.
  • The risks involved in the development of the dApp or code.

You can expect that part of the compensation offered by Ontology for technical contributions will be the award of ONT, it’s utility tokens used for both backend transactions and smart contracts under the network.

The Ontology ecosystem has provided a platform where business oriented dApps can be developed utilising the public chain infrastructure that Ontology provides in order to build the code or dApp. Ontology offers a distributed, public multi-chain, open source, transparent and collaborative trust platform for developers of codes and dApps.