-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathcontributing.html
56 lines (54 loc) · 2.39 KB
/
contributing.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
<!DOCTYPE html>
<html>
<head>
<title>Dataset Project</title>
<link href='https://fonts.googleapis.com/css?family=Open+Sans' rel='stylesheet' type='text/css'>
<link rel="stylesheet" href="https://caltechlibrary.github.io/css/site.css">
</head>
<body>
<header>
<a href="http://library.caltech.edu" title="link to Caltech Library Homepage"><img src="https://caltechlibrary.github.io/assets/liblogo.gif" alt="Caltech Library logo"></a>
</header>
<nav>
<ul>
<li><a href="/">Home</a></li>
<li><a href="index.html">README</a></li>
<li><a href="LICENSE">LICENSE</a></li>
<li><a href="install.html">INSTALL</a></li>
<li><a href="user_manual.html">User Manual</a></li>
<li><a href="about.html">About</a></li>
<li><a href="search.html">Search</a></li>
<li><a href="https://github.com/caltechlibrary/dataset">GitHub</a></li>
</ul>
</nav>
<section>
<h1 id="guidelines-for-contributing-to-this-project">Guidelines for
contributing to this project</h1>
<p>Any constructive contributions – bug reports, pull requests (code or
documentation), suggestions for improvements, and more – are
welcome.</p>
<h2 id="conduct">Conduct</h2>
<p>Everyone is asked to read and respect the <a
href="CODE_OF_CONDUCT.html">code of conduct</a> before participating in
this project.</p>
<h2 id="coordinating-work">Coordinating work</h2>
<p>A quick way to find out what is currently in the near-term plans for
this project is to look at the <a
href="https://github.com/caltechlibrary/dataset/issues">GitHub issue
tracker</a>, but the possibilities are not limited to what you see there
– if you have ideas for new features and enhancements, please feel free
to write them up as a new issue or contact the developers directly!</p>
<h2 id="submitting-contributions">Submitting contributions</h2>
<p>Please feel free to contact the author directly, or even better, jump
right in and use the standard GitHub approach of forking the repo and
creating a pull request. When committing code changes and submitting
pull requests, please write a clear log message for your commits.</p>
</section>
<footer>
<span>© 2022 <a href="https://www.library.caltech.edu/copyright">Caltech Library</a></span>
<address>1200 E California Blvd, Mail Code 1-32, Pasadena, CA 91125-3200</address>
<span><a href="mailto:[email protected]">Email Us</a></span>
<span>Phone: <a href="tel:+1-626-395-3405">(626)395-3405</a></span>
</footer>
</body>
</html>