npscience
commented
6 years ago Some notes:
- This doesn't appear to only be a LMIC problem: a researcher in US found students there only use the tools provided by the institution too, and aren't aware of others. More info on this and an idea.
- David Perez is trying to gather a list of good tools for collaborative research online and with an annual conference (maybe not an option for all). You can use and contribute to his resources on GitHub - [more info](info at https://github.com/npscience/eLife-at-MozFest2017/issues/17).
- The FOSS community seemingly needs support everywhere, I'd love to hear about it from your context too.
- NumFocus could be a good resource?
KoenVermeir
asbtariq
leenyahodza
livmar2000
israb12
solomon3m
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
[//]: # "======================= Insert a paragraph providing more context for your project or challenge focuses on. For project leads, this is a good place to give some broader context about your project—beyond the scope of the do-a-thon. If you're posting a challenge, this is a good chance to say how the problem arise or why it feels relevant to you. ============================" Recent research has shown that researchers in low- and middle income countries overwhelmingly rely on proprietary software, but they often do not have the means to acquire this software. Furthermore, the desired Research Software is highly field-specific and diverse.
On the other hand, they are hardly aware of the existence and possibilities of Free and Open Source Software (FOSS) alternatives to proprietary Research Software.
As a result, a survey has shown that the lack of access to software significantly affects research content and networks. The lack of access to Research Software thus obstructs equal research opportunities and the reproducibility of research results.
How do we raise awareness of field-specific Free and Open Source Software (FOSS) in low- and middle income countries? What are the right networks and strategies for communication and dissemination?
What are we working on during the do-a-thon? What kinds of support do we need?
[//]: # "======================= For those leading projects, please give some more information about what type of support you are specifically looking to get done during the do-a-thon day. Note: Challenge leads will not need to fill out this section and can remove it. ============================"
Advocacy_and_Policy,
Communications,
CommunityGrassrootsOrganizing
How can others contribute?
[//]: # "======================= Please say what the best way to contribute to the project or challenge is, sometimes that will just be 'lets discuss here' or 'Ive started a Google doc'. If you are a challenge lead, give some context on what design thinking tools you will be using, and how other folks can update their ideas onto the thread. If you are a project lead, and you already have clear ways people can contribute it might be worth linking to them here. Language: If your project is regionally based in a non-English-speaking region, clarify here what language you and contributors will primarily be communicating in. If you're leading a project or challenge participating remotely: Use this space to let people know that this is a remote project and that you are not 'in the room' in Berlin. 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. If you are at the in-person meeting in Berlin: Be as inclusive as possible to those outside the room. Use this space to give clear instructions to those participating in the do-a-thon remotely on how they can keep up to date and contribute. ============================"
[//]: # "======================= 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.