char-siuu-bao
commented
6 years ago Personas & Empathy Maps: Session 1 Outputs
Open npscience opened 6 years ago
char-siuu-bao
commented
6 years ago
char-siuu-bao
commented
6 years ago 
Confused? New to Github? Visit the GitHub help page on our site for more information!
[//]: # "======================= Even if you know Github well, we suggest you read this. Anything between these lines you can leave or delete, as they won't display anyway when you post (you can check this via Preview changes). They're here to help you complete issues quickly and in a way that will help other participants. If you're posting a new project, or challenge. We suggest you fill out the Google Forms first. ============================"
At a glance
[//]: # "======================= Please paste the metadata you received after submitting your project or challenge in your Google Form exactly as we sent it to you. You can delete what's there now, it's just there ============================"
Description
OpenCon this year will include workshops focused on advancing region-specific issues in Open Research and Open Education. In one of these workshops we’re proposing and going to be working through the question “How might we help academics/researchers in Europe make their next project more open?
We’re interested in this because researchers are often asked why certain aspects of their projects (data, code, access…) need to be open rather than being asked why something should not be open (e.g. for reasons of privacy). Rather than being asked “Why open?” we would like the default to be for researchers to critically address “Why not open?” We think we can move towards this if we can, as academics and researchers, consider how we can make our next project (more) open.
Participation
During the workshop (as well as before—and after!) we invite anyone to help tackle this challenge. You don’t need to be part of the workshop — or conference to share your thoughts and ideas!
If you will be with us in Berlin, here are the links to our sessions on Sched:
We’ll keep this issue up to date with anything we do or learn.
How can you contribute?
Anyone can contribute to these efforts. The place to start in helping us more deeply understand the challenge from more angles. We’ve started the effort in this Google Document, and we invite you to jump in and share any thoughts. Before the workshop, we’ll use that document to help make sure our theme has the right emphasis and help plan the workshop.
During the workshop, we’ll be following a plan that looks something like this. We’re still working on ironing out the final agenda details, but at the start of the session, we’ll confirm exactly what we’ll do and walk everyone through it.
For those not in the room, subscribe to this issue. We’ll post our outputs and notes here immediately after every session!
If you have an idea or comment to share that isn’t in the problem refinement exercise, and that you think won’t be covered in the workshop, we’d love to hear from you in the Github comments below.
[//]: # "======================= You're ready to post!!! After posting your issue, the real work begins. Next, you might want to: Tweet a link to this issue with #opencon so others can join in Make another issue to involve people in your work - remember to use your metadata Come back from time to time and update the community on your project. You'll get an email update whenever someone interacts with your issue. ============================"
This post is part of the OpenCon 2017 Do-A-Thon. Not sure what's going on? Head here.