Skip to content

Commit 93df563

Browse files
authored
Final few tweaks
1 parent e4042b7 commit 93df563

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

coc.html

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -13,31 +13,34 @@ <h2>Code of Conduct</h2>
1313

1414
<section class="wrapper style2">
1515
<div class="container">
16-
<p>We value the participation of every member of our community and want to ensure an that every contributer has an
17-
enjoyable and fulfilling experience. Accordingly, everyone who participates in any
18-
Hill Environmental Modelling Lab project is expected to show respect and courtesy to other community members at all time.
19-
We create our culture and our culture is inclusive.<p>
16+
<p>We value the participation of every member of our community and want to ensure an that every contributor has an
17+
enjoyable and fulfilling experience. Accordingly, everyone who participates in any Hill Environmental Modelling
18+
Lab project is expected to show respect and courtesy to other community members at all time. We create our
19+
culture and our culture is inclusive.<p>
2020

2121
<h3>Outputs and open science</h3>
2222

2323
<p>Where possible all outputs will be published as Open Access (preferably Gold or Diamond OA) and the submitted
2424
manuscript be posted on a pre-print server (e.g. <a href="https://eartharxiv.org/">EarthArXiv</a>) prior to
25-
publication</a>. Where Gold OA is not possible, the manuscript should be made available
25+
publication. Where Gold OA is not possible, the manuscript should be made available
2626
via Green OA and must be placed in the University of York's PURE system within three months of acceptance.</p>
2727

28-
<p> Authorship on any work will be openly discussed in lab meetings and should include everyone who contributed significantly to
29-
the work being presented. Where conflict arises, Jon Hill will facilitate discussion to resolve the conflict.</p>
28+
<p>Authorship on any work will be openly discussed in lab meetings and should include everyone who
29+
contributed significantly to the work being presented. Where conflict arises, Jon Hill will facilitate
30+
discussion to resolve the conflict.</p>
3031

31-
<p>All computers should be backed up. A USB hard drive should be used as a daily, automated back-up, with regular backups
32-
of important documents (e.g. model set-up files, manuscripts) to the lab group's google drive or the University servers.</p>
32+
<p>All computers should be backed up. A set of two USB hard drives should be used as a daily automated back-up,
33+
roated at regular intervals. Regular backup of important documents (e.g. model set-up files, manuscripts)
34+
to the lab group's google drive, the University's google drive or the University servers, preferably
35+
via a version control system, e.g. git.</p>
3336

3437
<p>All data should be placed on an appropriate repository with a DOI and published alongside the manuscript wherever possible.
3538
Data includes. Suitable examples of repositories include <a href-"https://figshare.com/">FigShare</a> and
3639
<a href="https://www.pangaea.de/about/">Pangaea</a>.</p>
3740

38-
<p>All software and scripts should be developed using Git or other suitable code versioning system, preferably in
41+
<p>All software and scripts should be developed using Git or other suitable code versioning system, ideally in
3942
an open online environment, such as GitHub. Group members are free to add repositories to this group's or
40-
start their own. Code should be released under a suitable, permissive licence, such as LGPL if possible.
43+
start their own. Code should be released under a suitable, permissive licence, such as LGPL whenever possible.
4144
Copyright of code developed lies with the University's of York for employees, but remains with the student on
4245
their work and notices should be placed in all source code stating copyright owner and licence.</p>
4346

@@ -55,8 +58,8 @@ <h3>Flexible working hours</h3>
5558
Automated emails, e.g. pull requests, github review request, etc are fine at any time, but no lab members are
5659
required nor should feel obliged to reply to them outside of their typical work hours.</p>
5760

58-
<p>If you experience any challenges related to flexible working within the lab please contact Jon Hill. All communication
59-
will be treated as confidential.</p>
61+
<p>If you experience any challenges related to flexible working within the lab please contact Jon Hill.
62+
All communication will be treated as confidential.</p>
6063

6164
<h3>Inclusivity and diversity</h3>
6265

0 commit comments

Comments
 (0)