-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathabout.html
More file actions
159 lines (148 loc) · 9.74 KB
/
about.html
File metadata and controls
159 lines (148 loc) · 9.74 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<!DOCTYPE HTML>
<!--
Massively by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<head>
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-KYWT8J8BHL"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-KYWT8J8BHL');
</script>
<title>Open Geocomputing</title>
<meta charset="utf-8" />
<link rel="apple-touch-icon" sizes="57x57" href="favicon/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="favicon/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="favicon/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="favicon/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="favicon/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="favicon/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="favicon/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="favicon/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="favicon/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="favicon/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="favicon/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="favicon/favicon-16x16.png">
<link rel="manifest" href="favicon/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="stylesheet" href="assets/css/main.css" />
<noscript><link rel="stylesheet" href="assets/css/noscript.css" /></noscript>
</head>
<body class="is-loading">
<canvas style='position: fixed;' id="earth-gl"></canvas>
<!-- Wrapper -->
<div id="wrapper" class="fade-in">
<!-- Header -->
<header id="header">
<img src="images/digitalWorld.gif">
<a href="index.html" class="logo">Open Geocomputing</a>
<img src="">
</header>
<!-- Nav -->
<nav id="nav">
<ul class="links">
<li><a href="index.html">Home</a></li>
<li class="active"><a href="about.html">About</a></li>
<li style="background-color:#ff000075"><a href="projects.html">Projects</a></li>
<li><a href="contact.html">Contact</a></li>
</ul>
<ul class="icons">
<li><a target="_blank" href="https://twitter.com/OGeocomputing" class="icon fa-twitter"><span class="label">Twitter</span></a></li>
<!--<li><a href="#" class="icon fa-facebook"><span class="label">Facebook</span></a></li>
<li><a href="#" class="icon fa-instagram"><span class="label">Instagram</span></a></li>-->
<li><a target="_blank" href="https://github.com/open-geocomputing" class="icon fa-github"><span class="label">GitHub</span></a></li>
</ul>
</nav>
<!-- Main -->
<div id="main" style="background-color: #ffffffd6;">
<!-- Featured Post -->
<article class="post featured">
<header id="GoalsAndPhilosophy" class="major">
<h2><a>Our Goals and Philosophy</a></h2>
<p>The goal of the Open Geocomputing project is to enable sharing of free and open access tools and software that are frequently used in geosciences.</p>
</header>
<p>
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 😉.
</p>
<ol style='text-align: justify;'>
<u>The few restrictions:</u>
<li >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.</li>
<li>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.</li>
<li>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.</li>
</ol>
</article>
</div>
<div style='height:500px'></div>
<div id="main">
<article class="post featured">
<h2><a>Add a project to Open Geocomputing</a></h2>
<header class="major">
<h3><a>New project</a></h3>
</header>
<p>Contributions are always welcome as long as they adhere to our <a href="#GoalsAndPhilosophy">goals and philosophy</a>. Please contact us using the Google group (<a href="https://groups.google.com/g/open-geocomputing" target="_blank">link</a>) to start a new project. You should provide a <b>short</b> description of the project including goals, and use to the community.
</p>
<header class="major">
<h3><a>Project migration</a></h3>
</header>
<p>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 (<a href="https://groups.google.com/g/open-geocomputing" target="_blank">link</a>). 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.<br>After migration of a project, please fork the project to its original location and let users know of its recent migration.</p>
<header class="major">
<h3><a>You are hesitating between a project on Open Geocomputing or on a local academic repository (personal, research group or institutional repository)</a></h3>
</header>
<p>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.</p>
</article>
</div>
<div style='height:500px'></div>
<div id="main">
<article class="post featured">
<header class="major">
<h2><a>Contributions</a></h2>
<p>If you want to contribute, please feel free to reach out to us. If you already have something ready, please share it with us. If you are feeling hesitant, drop us a message! </p>
</header>
<header class="major">
<h3 id="ImprouveCode"><a>Improve code</a></h3>
<p>Repositories are waiting for you</p>
</header>
<p>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.</p>
<header class="major">
<h3><a>Documentation and example</a></h3>
<p>Contributions can be very simple too!</p>
</header>
<p>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.
</p>
<header class="major">
<h3><a>Missing feature</a></h3>
<p>Spotting a missing feature is a contribution too !!</p>
</header>
<p>When you see a missing feature, help yourself. You know how to add it ? <a href="#ImprouveCode">Then add it yourself</a>. 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)
</p>
<header class="major">
<h3><a>Bug</a></h3>
<p>You see a bug ? Save your time along with others!</p>
</header>
<p>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? <a href="#ImprouveCode">Then propose a fix through a pull request</a>. 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)</p>
</article>
</div>
<!-- Copyright -->
<div id="copyright">
<ul><li>Design inspired by: <a href="https://html5up.net">Massively</a></li></ul>
</div>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/jquery.scrollex.min.js"></script>
<script src="assets/js/jquery.scrolly.min.js"></script>
<script src="assets/js/skel.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
</body>
<script type="module" src="assets/js/earth.js"></script>
</html>