forked from char-siuu-bao/do-a-thon-preview
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathproject.html
213 lines (182 loc) · 11 KB
/
project.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
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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
<!DOCTYPE html>
<!--
Transit by TEMPLATED
templated.co @templatedco
Released for free under the Creative Commons Attribution 3.0 license (templated.co/license)
-->
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Submit a project - OpenCon Do-A-Thon</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="description" content="" />
<meta name="keywords" content="" />
<link rel="icon" type="image/x-icon" href="/doathon-dev/images/favicon.ico" />
<!--[if lte IE 8]><script src="js/html5shiv.js"></script><![endif]-->
<!-- Essential META Tags -->
<meta property="og:title" content="OpenCon Do-A-Thon">
<meta property="og:description" content="Submit a project to the do-a-thon. It's a great opportunity to receive support and contributions from collaborators around the world">
<meta property="og:image" content="/doathon-dev/images/social.png">
<meta property="og:url" content="https://doathon.opencon2018.org/project">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@open_con" />
<style type="text/css">
.hidden {display:none;}
</style>
<script type="text/javascript" src="/scripts/jquery.js"></script>
<script type="text/javascript">
$('html').addClass('hidden');
$(document).ready(function() { // EDIT: From Adam Zerner's comment below: Rather use load: $(window).on('load', function () {...});
$('html').show(); // EDIT: Can also use $('html').removeClass('hidden');
});
</script>
<link rel="stylesheet" href="css/skel.css" />
<link rel="stylesheet" href="css/style.css" />
<link rel="stylesheet" href="css/style-xlarge.css" />
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-61115389-4"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-61115389-4');
</script>
</head>
<body>
<body class="landing">
<!-- Header -->
<header id="header">
<h1><a href="index.html">OPENCON DO-A-THON</a></h1>
<nav id="nav">
<ul>
<!-- <li><a href="challenge.html">SUBMIT CHALLENGE</a></li> -->
<!-- <li><a href="project.html">SUBMIT PROJECT</a></li> -->
<li><a href="participate.html">PARTICIPATE</a></li>
</ul>
</nav>
</header>
<!-- Main -->
<section id="one" class="wrapper style5 special">
<p></p>
<header class="major">
<h2>
Submit a project to the do-a-thon
</h2>
<p>
Have a project idea you want to put into action? Or an existing project that needs development or support? The do-a-thon is a great opportunity to receive support and contributions from collaborators around the world.
</p>
<ul class="actions">
<li>
<a href="https://docs.google.com/forms/d/e/1FAIpQLSd_ptZY4xgc4vZAiMmsrjspPF3gUxOfOj_iBQ5ign3f5n5bqw/viewform" class="button big">Submit a Project</a>
</li>
</ul>
</header>
<h3>
What are some examples of projects people might work on?
</h3>
<table width=100%>
<thead>
<th>Project Name</th>
<th>What's this project all about?</th>
<th>Help Needed </th>
</thead>
<tbody sheetsu="https://sheetsu.com/apis/v1.0/fa8925c0663c" sheetsu-limit="3">
<tr>
<td><strong>{{Project Name}}</strong></td>
<td>{{Project Summary}}</td>
<td>{{What aspects of the project need support during the do-a-thon? }}</td>
</tr>
</tbody>
</table>
<script src="//load.sheetsu.com"></script>
<h3>
Steps for Submitting
</h3>
<p><strong>
1. Make sure your project is related in some way to Open Research or Open Education.
</strong>
<br>
We go through a simple review process to make sure all the challenges for the do-a-thon are related to Open Research and Education. If you'd like to learn more about these issues, perhaps <u><a href="https://www.youtube.com/watch?v=V9nrLVRNCuQ&list=PLKzRudZaXUD2835Qswd8SB3JKhlLJgG7j" target="_blank">watch some of our videos introducing the issues</a></u>.<p>
<p><strong>
2. Fill out our project submission form.
</strong>
<br>Access the form <strong><u><a href="https://docs.google.com/forms/d/e/1FAIpQLSd_ptZY4xgc4vZAiMmsrjspPF3gUxOfOj_iBQ5ign3f5n5bqw/viewform" target="_blank">here</a></u></strong>. This tells us a bit more about your project and what kind of support you're looking for. It only takes 5-10 minutes!</p>
<p><strong>
3. Wait for e-mail instructions on how to share your project on Github.
</strong><br>
After you've filled out the form, you'll be emailed instructions on how to share information about your project so others can discover it and contribute! Github is a platform for open source, collaborative working. We'll be using it as a space to manage do-a-thon projects and challenges. Specifically, we are doing this through Github "issues". Each issue will act as a mini discussion thread for each task you want to collaborate on. Please follow the email instrutions carefully so your project includes the correct meta-data, which will allow others to find it easily!
</p>
<p>
If you don't already have one, you'll need to <a href="https://github.com/"><u>create a Github account</u></a> (top tips: try and use your name as your username, you only need the free plan, and you can skip step 3).
</p>
<p><strong>
4. Your project will now be discoverable on our <u><a href="participate.html">Do-a-thon Projects page.</a></u></strong>
<br>
Now, others will be able to easily find your project and contribute!
</p>
</li>
<h3>
Tips for Leading Projects
</h3>
<p><strong>Be a respectful facilitator and project lead</strong>. As a project lead, we ask you pay special attention to our <u><a href="http://www.opencon2018.org/code_of_conduct" target="_blank">Code of Conduct</a></u> and be welcoming, enthusiastic, and patient with contributors. And of course - remember to thank them for their contributions!
</p>
<p><strong>Write clear contributing guidelines. </strong> Be specific about how people can help and get in touch. Is there particular skills or expertise you're looking for? <strong>If your project is regionally based in a non-English-speaking region</strong>, let people know in your contributing guidelines what language you and contributors will primarily be communicating in.
</p>
<p><strong>Keep in mind that there are people participating both in-person and remotely!</strong>. If you're at the in-person meeting in Toronto: Be as inclusive as possible to those outside the room. In your guidelines, give clear instructions to those participating in the do-a-thon remotely on how they can keep up to date and contribute. <strong>If you're leading your project remotely:</strong> use your contributing guidelines to let people know that this is a remote project, and that you'll be communicating with contributors online! Let other participants know what the best way to get in touch with you, where the work will happen, and where any updates or outputs will go.
</p>
<p><strong>Update — and check — the Github issue frequently to keep people up to speed.</strong> Make sure to document whatever conversations or progress is happening somewhere online. If the conversation is moving off the original Github thread (e.g. onto a Google Doc or Slack), be sure to include a link to wherever that's happening in the original issue, in case new folks want to join your project!
</p>
<p><i>
Still have question about this before the do-a-thon starts? Send an email or feedback to Joe[at]sparcopen[dot]org. </i>
</p>
</div>
</section>
<!-- Footer -->
<footer id="footer">
<div class="container">
<section class="links">
<div class="row">
<section class="3u 6u(medium) 12u$(small)">
<h3>About</h3>
<ul class="unstyled">
<li><a href="https://www.opencon2018.org/" target="_blank">OpenCon Main Site</a></li>
<li><a href="https://www.opencon2018.org/code_of_conduct" target="_blank">Our Code of Conduct</a></li>
<li><a href="mailto:[email protected]" target="_blank">Feedback</a></li>
<li><a href="github-help.html" target="_blank">Github Help</a></li>
<li><a href="host-your-own.html" target="_blank">Host your own Do-a-thon</a></li>
</ul>
</section>
</div>
</section>
<div class="row">
<div class="8u 12u$(medium)">
<ul class="copyright">
<li>Except where otherwise noted, content on this site is licensed under a <u><a href="https://creativecommons.org/licenses/by/4.0/" target="_blank">
CC-BY 4.0 International License</a></u>. Web Design template from <u><a href="http://templated.co" target="_blank">TEMPLATED</a></u>. Thanks to <u><a href="https://mozilla.github.io/global-sprint/" target="_blank">Mozilla Science & the Global Sprint</a></u> for inspiration in designing to Do-a-thon. Contributions and edits to this page are welcomed on <u><a href="https://github.com/sparcopen/doathon-dev/#doathon-development-site" target="_blank">Github</a></u>.</li>
</ul>
</div>
<div class="4u$ 12u$(medium)">
<ul class="icons">
<li>
<a class="icon rounded fa-facebook" href="https://www.facebook.com/openconglobal" target="_blank"><span class="label">Facebook</span></a>
</li>
<li>
<a class="icon rounded fa-twitter" href="https://twitter.com/open_con" target="_blank"><span class="label">Twitter</span></a>
</li>
</ul>
</div>
</div>
</div>
</footer>
</body>
<script src="js/jquery.min.js"></script>
<script src="js/skel.min.js"></script>
<script src="js/skel-layers.min.js"></script>
<script src="js/init.js"></script>
<!-- Start of opencon Zendesk Widget script -->
<!-- Zendesk Widget, now retired for OpenCon sites. Leaving here as a reminder of mechanisms we used.
<script>/*<![CDATA[*/window.zEmbed||function(e,t){var n,o,d,i,s,a=[],r=document.createElement("iframe");window.zEmbed=function(){a.push(arguments)},window.zE=window.zE||window.zEmbed,r.src="javascript:false",r.title="",r.role="presentation",(r.frameElement||r).style.cssText="display: none",d=document.getElementsByTagName("script"),d=d[d.length-1],d.parentNode.insertBefore(r,d),i=r.contentWindow,s=i.document;try{o=s}catch(e){n=document.domain,r.src='javascript:var d=document.open();d.domain="'+n+'";void(0);',o=s}o.open()._l=function(){var e=this.createElement("script");n&&(this.domain=n),e.id="js-iframe-async",e.src="https://assets.zendesk.com/embeddable_framework/main.js",this.t=+new Date,this.zendeskHost="opencon.zendesk.com",this.zEQueue=a,this.body.appendChild(e)},o.write('<body onload="document._l();">'),o.close()}();
/*]]>*/</script>
-->
<!-- End of opencon Zendesk Widget script -->
</html>