forked from SciTools/scitools.org.uk
-
Notifications
You must be signed in to change notification settings - Fork 0
/
collaboration.html
130 lines (93 loc) · 5.74 KB
/
collaboration.html
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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html dir="ltr" lang="en-gb">
<!-- Generated automatically by github.com/scitools/scitools.org.uk -->
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<meta content="AVD" name="author">
<meta content="SciTools - Python libraries for Weather and Climate Science." name="description">
<meta content="PP, GRIB1, GRIB2, netcdf, HDF, visualisation, weather, climate, map, cartography, projection, map, analysis,
Iris, Cartopy" name="keywords">
<link rel="stylesheet" type="text/css" href="styles/scitools.css">
<title>Collaboration</title>
</head>
<body>
<div class="wrapper">
<div id="hd">
<a href="iris/index.html" style="text-decoration:none;color:black;">
<img src="images/Iris7_1_trim_100.png" width="101" height="100" alt="Iris logo" />Iris
</a>
<a href="https://github.com/SciTools/iris">
<img style="position: absolute; top: 0; right: 65%; border: 0;"
src="https://s3.amazonaws.com/github/ribbons/forkme_right_orange_ff7600.png"
alt="Fork Iris on GitHub"></a>
<a href="cartopy/index.html">
<img src="images/cartopy_small.png" width="200" height="100" alt="small cartopy logo" style="position: absolute; top: 3%; right: 45%; border: 0;" />
</a>
<a href="https://github.com/SciTools/cartopy"><img
style="position: absolute; top: 0; right: 35%; border: 0;"
src="https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png"
alt="Fork Cartopy on GitHub"></a>
</div>
<div class="navigation">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="governance.html">Governance</a></li>
<li><a href="iris/index.html">Iris</a></li>
<li><a href="cartopy/index.html">Cartopy</a></li>
<li><a href="tools.html">Other tools</a></li>
<li><a href="about.html">About</a></li>
<li><a href="collaboration.html">Collaboration</a></li>
</ul>
</div>
<h1>Collaboration</h1>
<p>
Iris and Cartopy are free and open source projects, published under the <a href="http://www.gnu.org/licenses/lgpl.html">LGPLv3</a> licence. Both libraries work extensively with third party free and open source libraries.
</p>
<p>
One of the primary objectives of this approach is to aid collaboration and collaborative development.
</p>
<h2>Developing alongside SciTools</h2>
<p>
The SciTools projects provide capabilities for developers to make use of. Projects are encouraged to use the capabilities of SciTools and build libraries and functionality on top of these capabilities.
</p>
<p>
Projects depending on SciTools Libraries are encouraged to engage with the development process, through the <a href="iris/community.html">Community Forums</a> and the <a href="http://github.com/scitools">GitHub</a> code development sites. It is hoped that this will lead to developers contributing code to SciTools Libraries.
</p>
<h3>Publishing Code</h3>
<p>
For any potential collaborative development activity it is important that the code base is available to collaborators and licensed to enable collaboration. Publishing code as it is being developed is an excellent way to work with development communities working in similar spaces.
</p>
<p>
It will benefit SciTools development and the development of libraries dependent on SciTools if the code is published and available for developers to investigate and provide feedback on.
</p>
<p>
Publishing on a site such as <a href="https://github.com">GitHub</a>, the <a href="governance.html#contributors">SciTools Contributors </a> approach and <a href="http://www.gnu.org/licenses/lgpl.html"> LGPLv3</a> license present one way of managing this. It is the responsibility of a publisher to manage these matters as they see fit, considering license conditions, access rights and the implications for their project.
</p>
<p>Such public projects, dependent on SciTools modules, are likely to provide a rich seam of ideas and approaches, leading to developments in SciTools modules which can be adopted and shared across the SciTools community.</p>
<h2>Contributing to SciTools</h2>
<p>
Contributions to the SciTools open source libraries are encouraged: the pages on <a href="governance.html">governance</a> and the <a href="iris/docs/latest/developers_guide/index.html">developer's guide</a> provide information on what is involved in SciTools collaborative development.
</p>
<p>
Small scale contributions fit well with this model, such as bug fixes and new feature implementations to current modules. Larger scale development activities may require different approaches, as it may take significant design and implementation effort before it is clear how integration may occur.
</p>
<p>
It may prove useful to publish such code independently of SciTools and then investigate integration over time.
</p>
<h3>Adoption of Code</h3>
<p>
Adoption of code into SciTools libraries will follow the <a href="governance.html">governance</a> and then refer to our <a href="iris/docs/latest/developers_guide/index.html">developer's guide</a> procedures.
</p>
<p>
In most cases discussions via Github issues and the developer communities (<a href="iris/community.html"> iris </a> and <a href="cartopy/docs/latest/index.html#getting-involved"> cartopy </a>) will be required, to detail scope, interfaces and design considerations.
</p>
<p>
Providing publicly available code which can be developed collaboratively will enable more detailed and focussed discussions of the relevant issues facilitating code adoption.
</p>
<div id="ft">
© British Crown Copyright 2017, Met Office
<br>
</div>
</div>
</body>
</html>