Our philosophy is to maintain a very open philosophy with flexibility to host contributions spanning across entire gambit of geosciences, ranging from a single script to delineate DEMs to complete toolboxes that can perform complex geospatial operations on remote sensing dataset. If you have other ideas, don't hesitate to surprise us 😉.

The few restrictions:
1. Licensing:We require contributions to be free and open access, which can be used by the wider community. The use of proprietary software such as MATLAB are allowed as long as the scripts are open access.
2. Project maintenance: In order to limit the number of zombie projects, we request that the project contributors keep their scripts up-to-date, with regular feature updates. The point is to enable open and replicable science which is not limited to an obscure publication.
3. Documentation: In order to enhance the usability of the projects, we request that authors maintain a minimum level of documentation which will allow easier adoption by other researchers. The goal here is not to force people to write a complete guide but to increase usability of the code.

Add a project to Open Geocomputing

Contributions are always welcome as long as they adhere to our goals and philosophy. Please contact us using the Google group (link) to start a new project. You should provide a short description of the project including goals, and use to the community.

We strongly encourage movement of personal projects to Open Geocomputing for a more sustained community evolution. You can contact us for the same using the Google group (link). A small review will be undertaken by community members. We also encourage older projects if developers can justify the reason for their resurrection. A typical reason for resurrection will be a prototype that is well used, and needs some support and maintenance.
After migration of a project, please fork the project to its original location and let users know of its recent migration.

We advise you to start a new project. Open Geocomputing will not only provide visibility to the project, but also imbibe community spirit, that will lead to further developments even after the original developer moves on to doing something new.

To improve code, datasets, etc., we request you to fork the repository and submit a pull request. If needed, reach out to the community for some inputs on how to add your modification. We already thank you for your contribution.

You struggled to use a feature, see a missing explanation in the documentation, or simply some typo. Help us to fix it !! The following users will be grateful. Don't forget that when we develop, things that look trivial to us may not be obvious to others. We thank contributors that provide features with documentation. We are also thankful to people who use their precious time to improve documentation, leading to an enhanced user experience.

When you see a missing feature, help yourself. You know how to add it ? Then add it yourself. In case you don't know, inform the community about it. (Don't forget that the community does not work for you, and that sometimes they don't know either how to add some awesome features)

You see a bug, first inform the community, to know if it's really one &x1F601;, and please provide examples. You know how to fix the problem? Then propose a fix through a pull request. You don't know, not a problem, the community probably has an idea. (Don't forget that the community does not work for you, and that sometimes they struggle on bugs as much as you do. So always be kind)