raynamharris
commented
6 years ago This is a critical and timely topic. It is challenging when progress is limited because the structures of academia haven't changed to meet the current needs or demands of today's researchers and educators.
char-siuu-bao
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 “How might we navigate and change power structures within academia to support greater openness”.
We’re interested in this because power structures within the research and education ecosystems shape the incentives that drive early career practitioners toward, and away from, openness and other practices. By mapping these power relationships, we’ll be able to identify potential areas that could be most productively addressed to create change.
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! We’ll keep this issue up to date with anything we do or learn.
How can others 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.
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.