Open Science UMontreal - Githubissues

SamGuay commented 4 years ago

Project Lead: @SamGuay & @DannyColin

Mentor: @ajstewartlang

Welcome to OLS-1! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Life Science program :tada:.

Before Week 1 (Jan 20): Meet your mentor!

[x] Create an account on GitHub
[x] Complete your own copy of the open leadership self-assessment and share it to your mentor

[x] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Jan 27): Cohort Call (Welcome to Open Life Science!)

[x] Create an issue on the OLS-1 GitHub repository for your OLS work and share the link to your mentor.
[x] Draft a brief vision statement using your goals

This lesson from the Open Leadership Training Series (OLTS) might be helpful
[x] Leave a comment on this issue with your draft vision statement & be ready to share this on the call
[x] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Feb 3): Meet your mentor!

[x] Look up two other projects and comment on their issues with feedback on their vision statement
[x] Complete this compare and contrast assignment about current and desired community interactions and value exchanges
[x] Complete your Open Canvas (instructions, canvas)
[x] Share a link to your Open Canvas in your GitHub issue: Open Canvas here
[x] Start your Roadmap
[ ] Comment on your issue with your draft Roadmap
[x] Suggest a cohort name at the bottom of the shared notes and vote on your favorite with a +1

Before Week 4 (Feb 10): Cohort Call (Tooling and roadmapping for Open projects)

[ ] Look up two other projects and comment on their issues with feedback on their open canvas.

Week 5 and more

[x] Create a GitHub repository for your project: OSUMontreal
[x] Add the link to your repository in your issue
[ ] Use your canvas to start writing a README.md file, or landing page, for your project
[ ] Link to your README in a comment on this issue
[ ] Add an open license to your repository as a file called LICENSE.md
[x] Add a Code of Conduct to your repository as a file called CODE_OF_CONDUCT.md
[ ] Invite new contributors to into your work!

This issue is here to help you keep track of work as you start Open Life Science program. Please refer to the OLS-1 Syllabus for more detailed weekly notes and assignments past week 4.

SamGuay commented 4 years ago

Vision statement

We are working with and for the members of the University of Montreal to establish an inclusive and collaborative community where students and researchers at all stages of their careers feel welcome to learn, share, and discuss open science values, principles, and practices. As open science is a broad and wide-ranging concept with domain-specific definitions, we will provide opportunities to meet and encourage the exchange of ideas within and across fields because we can all learn from each other. By raising awareness, we hope this project will instigate a culture shift and help people realize how they can immediately benefit from using open and reproducible practices, making science more accessible, transparent and reproducible in the long run.

ChiaraBertipaglia commented 4 years ago

Your project sounds so interesting, I think we are moved by the same vision! I'd love to see how you're mapping stakeholders to obtain necessary buy-in (or perhaps you are already past that point?)

It would be great if you had time to take a look at my roadmap, so we could exchange ideas. Thanks! #9

It also looks like you might be involved in community management tasks? Do you know the community of community managers that Lou Woodley has put together https://www.cscce.org/? You are welcome to join our slack channel https://cscce-slack-invite-bot.herokuapp.com/

cassgvp commented 4 years ago

We're totally having a culture-shift / community building party! This is definitely a key part of my work too on #15 . I'd love to work closely with both this project and issues #9 #11 #16 and #6. I'm sure there is a lot of material we could share 🥰

Karvovskaya commented 4 years ago

I love your vision statement! Something I was thinking about for my institutions, not sure how it is applicable to your situation: it would be nice to bridge the gap between the researchers and the support staff. In Dutch universities, we have more and more employees who contribute to the research process (data librarians, data engineers, data stewards, data managers, etc) but they are not seen as belonging to the same community as "true academics". What are your thoughts on this?

cassgvp commented 4 years ago

I love your vision statement! Something I was thinking about for my institutions, not sure how it is applicable to your situation: it would be nice to bridge the gap between the researchers and the support staff. In Dutch universities, we have more and more employees who contribute to the research process (data librarians, data engineers, data stewards, data managers, etc) but they are not seen as belonging to the same community as "true academics". What are your thoughts on this?

Totally. This is a massive conversation that I'd love to pick up.

SamGuay commented 4 years ago

Thanks y'all for the positive and valuable feedback! :) So motivating! I will definitely follow and comment on your issues.

@ChiaraBertipaglia

I'd love to see how you're mapping stakeholders to obtain necessary buy-in (or perhaps you are already past that point?)

Unfortunately, we are very far from being past that point! However, we did get in touch with key students/researchers/librarians here and there during 2019 to test the water. I had the chance to get invited on panels and give presentations to audiences I wouldn't have thought were interested in our initiatives (e.g., researchers in the nursing department were truly amazed to learn about the world of possibilities on how to open their science so they asked us if they could eventually invite us to teach some workshops in their summer school!). For now, we are focusing on getting core members hooked and we will go from there. In fact, we are waiting to have some concrete content / website before going wild :cowboy_hat_face:. What about you?

It also looks like you might be involved in community management tasks? Do you know the community of community managers that Lou Woodley has put together https://www.cscce.org/?

Thanks for sharing, I didn't know about it! This seems to be a truly useful resource, especially when you don't have much experience in community management. I just signed up on Slack.

@cassgvp

We're totally having a culture-shift / community building party! This is definitely a key part of my work too on #15 . I'd love to work closely with both this project and issues #9 #11 #16 and #6. I'm sure there is a lot of material we could share 🥰

The more the merrier as they say?! :fireworks: Feels so good to see other like-minded people. We should think of a way to facilitate material sharing / working closely.

@Karvovskaya

it would be nice to bridge the gap between the researchers and the support staff. In Dutch universities, we have more and more employees who contribute to the research process (data librarians, data engineers, data stewards, data managers, etc) but they are not seen as belonging to the same community as "true academics". What are your thoughts on this?

This is an excellent point. I feel this is a widespread phenomenon. The community we're trying to establish aims to fix that fracture. I'd say that I consider these employees even more valuable than the true academics (e.i., Principal Investigators) in the realm of Open Science. If we're being honest here, we know that the majority of PIs don't have time to learn and do everything, so employees do most of the day-to-day jobs. However, I don't think it's necessarily the PIs' job to do everything, refer to this Twitter thread who puts it well. Though I think PIs/employers should encourage employees (and trainees) to learn and apply more open science practices. By encouraging, I mean with more than just words... :upside_down_face: To summarize my thoughts: everyone belongs to our community.

That being said, it did give us some hard times when we were doing our Open Canvas. I don't know whether it was hard because we couldn't find the proper French word to convey our thoughts/describe the community we want to establish as inclusive as possible (i.e., students/employees/PIs, OS curious, etc.). I have a feeling the term researchers isn't right, neither is research community. Would contributors to the research process be inclusive enough? In my lab, it's straight forward, employees and trainees alike are encouraged to develop their OS skills, but I know we're pretty lucky to have a supervisor willing to open his mind. By organizing activities where everyone feels welcome will hopefully "force" the different communities to merge.

These are my raw thoughts on this. Let's keep the discussion going. What are your thoughts on the matter? Do you have solutions in mind? What can we do to improve the situation as grad students?

KristinaRiemer commented 4 years ago

This is a great initiative!

I don't know if this will be helpful for getting buy-in across diverse domains and departments, but the Data Science Institute at the University of Arizona has instituted an ambassadors program (for data science specifically, but it could be ported to open science!). They found graduate students across a range of fields to act as ambassadors who could be the key person that people in the department could reach out to for help with data science, and the ambassadors meet regularly to break down those domain boundaries. I don't think it involves any money, but it is something for the ambassadors to put on their resume. And grad students are probably a good target for open science because they are probably going to more aware and accepting of recent trends.

+1 to @ChiaraBertipaglia's comments about CSCCE. They're doing great work on building and maintaining scientific communities! And they're using Slack as an effective communication tool, which is great to see when there are so many that go nearly totally unused.

MagicMilly commented 4 years ago

Just to jump in here - we have been building an open science community and space for an exchange of ideas and skills with Research Bazaar Arizona (our website and twitter), and we have been having quite a lot of fun with it! I became involved with ResBaz before I joined the University as a staff member, and we have a great mix of academics (researchers, students, and staff) and community members / citizen scientists. I'm so excited to hear about this happening at UMontreal and within other universities and communities! 🎉

christinerogers commented 4 years ago

👍 upvoting research community -- in the larger labs it's the ecosystem, including support staff, not just the researchers, who are instrumental in facilitating the open sharing. Building up these teams to think open (by default or by design) is key, and diffuses the goal in a good way.

yochannah commented 4 years ago

Hi Project Leads,

  This is your project report file:

https://hackmd.io/j4WNYpM0T064caMUVi1CZw?both

Please start working on it for the final presentation. We will send more info in the weekly email.

  Best, 

OLS team 

ChiaraBertipaglia commented 4 years ago

Hi team,

I’m receiving links in separate emails with other people’s projects…

Thanks, Chiara

— Chiara Bertipaglia, PhD Scientific Program Manager Zuckerman Institute https://zuckermaninstitute.columbia.edu/ - Columbia University c.bertipaglia@gmail.com @ChiaBertipaglia she/her/hers - see www.mypronouns.org http://www.mypronouns.org/ to learn more

On Apr 6, 2020, at 12:46 PM, Yo Yehudi notifications@github.com wrote:

Hi Project Leads,

 >  > This is your project report file:

https://hackmd.io/j4WNYpM0T064caMUVi1CZw?both https://hackmd.io/j4WNYpM0T064caMUVi1CZw?both Please start working on it for the final presentation. We will send more info in the weekly email.

 >  > Best, >

OLS team >

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/open-life-science/ols-1/issues/4#issuecomment-609908419, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMBBELJK7M4OKSYPOZJGTTRLIBN7ANCNFSM4KK337CA.

open-life-science / ols-1

Open Science UMontreal #4

Vision statement