forked from char-siuu-bao/do-a-thon-preview
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathchallenge.html
260 lines (234 loc) · 15.1 KB
/
challenge.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
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
<!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>Present a challenge - 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]-->
<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>
<!-- Essential META Tags -->
<meta property="og:title" content="OpenCon Do-A-Thon">
<meta property="og:description" content="Is there a specific problem you want to tackle in Open Research and Education? Work together on designing a solution with the OpenCon community!">
<meta property="og:image" content="/doathon-dev/images/social.png">
<meta property="og:url" content="https://doathon.opencon2018.org/challenge">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@open_con" />
</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>
Present a challenge.
</h2>
<p>
Is there a specific issue or problem you want to tackle in Open Research and Education? Here's a chance to share it with the OpenCon Community and work together on designing a solution.
<ul class="actions">
<li>
<a href="https://docs.google.com/forms/d/e/1FAIpQLScliEFPRWlvtn0LoK6-1OejaYLz6OwKMd00jFdsMjQRQTlM1A/viewform" class="button big">Submit a Challenge</a>
</li>
</ul>
<a name="participate"></a></header>
<h3>
What do we mean by "challenge"?
</h3>
<p>For the do-a-thon, we're encouraging participants to think about problems in terms of <u><a href="https://public-media.interaction-design.org/pdf/How-Might-We.pdf"><i>"How might we?"</i> statements.</a></u> This type of framing can encourage us to think big, consider multiple perspectives, and focus on a variety of possibilities rather than fixating on a pre-determined solution.
</p>
<p>
We're asking you to define the challenge you're working on—really understanding what the hurdles are—before jumping straight to a solution. This helps avoid the situation of designing a product that doesn't actually address the heart of a problem! </p>
<p><strong>
Some examples of challenge statements could look like:
</strong></p>
<table>
<tr><td>
How might we create offline Open Educational Resources that can be used and adopted in regions without steady internet connection?
</td></tr>
<tr><td>
How might we increase the rewards associated with preprint publishing? </td></tr>
<tr><td>
How might we make Open Educational Resources more easily editable to better serve local contexts?
</td></tr>
</table>
<p>
See the full list of challenges your fellow community members have put forward <a href="participate#challenges"><u>here</u></a>.
</p>
<h3>
Steps for Submitting a Challenge
</h3>
<p><strong>
1. Make sure your proposed challenge is related 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. Come up with a "How might we___?" statement for your problem.</strong><br> Make sure to <u><a href="participate#challenges">explore the challenges others have already submitted</a></u> to ensure we're not proposing the same problems twice. (If you do see a similar challenge - consider joining forces with them!)
</p>
<p><strong>
3. Submit your problem statement for review through our <u><a href="https://docs.google.com/forms/d/e/1FAIpQLScliEFPRWlvtn0LoK6-1OejaYLz6OwKMd00jFdsMjQRQTlM1A/viewform" target="_blank">Google form</a>.</u></strong><br>This allows us to go through a super quick review process, and provides us with some metadata about the challenge you've proposed.
</p>
<p><strong>
4. Wait for instructions via e-mail on how to share more about your challenge on Github.</strong><br>Github is a platform for open source, collaborative working. We'll be using it as a space to manage do-a-thon challenges and projects. This is so others can discover it and contribute! We do this through Github "issues", where each issue will act as a mini discussion thread for each challenge you want to collaborate on. Please follow the email instructions carefully so your challenge is listed properly on our page.
</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>
5. Your challenge will now be discoverable on our <u><a href="participate.html">Do-a-thon Challenge page</a></u>.</strong><br>Now, others will be able to easily find your challenge and contribute! Please check out our tips for leading challenges, as well as our <u><a href="#resources">design thinking resources</a></u> that will guide you through designing a solution to your problem statement.
</p>
<h3>Tips for Challenge Leads</h3><a name="resources"></a>
<p><strong>Be a respectful facilitator and challenge lead</strong>. As a challenge 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>
Document your process and update your Github issue frequently</strong>.
This allows for remote participants or newcomers to stay updated on your challenge progress. Doing a design thinking activity on paper? Make sure you take a photo of your sketch and upload it to the issue. 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><strong>
Familiarize yourself with some <u><a href="#resources">design thinking resources</a></u></strong>.
These tools are meant to help you better understand your challenge statement. Who are the people involved? What forces are influencing the problem? Having this understanding can bring us closer to a solution.
</p>
<p><strong>Write clear guidelines on how people can participate. </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 challenge 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><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>
</section>
<section id="one" class="wrapper style7 special">
<header class="major"><a name="designthinking"></a>
<h2>
Design Thinking Tools
</h2>
<p>
Design thinking can help you build a solution through first understanding your problem from various perspectives. Learn how to design a simple prototype of your solution that you can test and continue building off of after the do-a-thon. The complete OpenCon design thinking introductory slidedeck can be <strong><u><a href="https://docs.google.com/presentation/d/1qMNS2-AtnvZPldGoBRitRq-IVrHUNUp1aedys7kOz3M/edit#slide=id.p">downloaded here.</a></u></strong>
</p>
<p> A printable toolkit with exercise templates for the day-of can be accessed <u><a href="https://docs.google.com/document/d/1WA4RXHmolgidiVpOizz0rsaE8PE_4fRwg1B3XK8jkZU/edit?usp=sharing"><strong>here.</strong></a></u>
</header>
<h3> The design thinking tools will walk you through three key steps: </h3>
<div class="row 150%">
<div class="4u 12u$(medium)">
<section class="box">
<i class="icon big rounded fa-sitemap"></i>
<p></p>
<h3 style="text-align:center;">
1) Map the System
</h3>
<p style="text-align:center;">
Understand the system your problem is situated in—sketch out the users and institutions involved, the flow of resources.
</p>
</section>
</div>
<div class="4u 12u$(medium)">
<section class="box">
<i class="icon big rounded fa-user"></i>
<p></p>
<h3 style="text-align:center;">
2) Know Your Users
</h3>
<p style="text-align:center;">
Better understand the various people involved in the system, who they are, what their needs are, and what barriers they face.
</p>
</section>
</div>
<div class="4u$ 12u$(medium)">
<section class="box">
<i class="icon big rounded fa-send-o"></i>
<p></p>
<h3 style="text-align:center;">
3) Design a Solution
</h3>
<p style="text-align:center;">
Based off your user and systems research, design a solution. Learn how to create & test a simple prototype.
</p>
</section>
</div>
</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>