<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tiphaine Boyer on Medium]]></title>
        <description><![CDATA[Stories by Tiphaine Boyer on Medium]]></description>
        <link>https://medium.com/@tiphaine.boyer?source=rss-1fdda277d65------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yg9BxQkDKJxJ7wIOjaZmfg.jpeg</url>
            <title>Stories by Tiphaine Boyer on Medium</title>
            <link>https://medium.com/@tiphaine.boyer?source=rss-1fdda277d65------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:44:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tiphaine.boyer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Get Started with Open Source Contributions]]></title>
            <link>https://medium.com/oviohub/how-to-get-started-with-open-source-contributions-57c4170f0c41?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/57c4170f0c41</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Wed, 30 Sep 2020 00:37:31 GMT</pubDate>
            <atom:updated>2020-09-30T00:37:31.466Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re looking to get started with open source contributions, it can be difficult to know where to start. To make a positive impact on a project, you need to have an understanding of how contributors and maintainers interact in the open source community, as well as their expectations and guidelines. This article will help you pinpoint how to find the right project, search for issues with Ovio’s recommended search methods and be a quality contributor to the open source community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*sb6Hpqq-HUDvRt5O" /></figure><p><strong>Get to know GitHub (for first-timers only)</strong></p><p>In order to get the most out of your open source software (OSS) experience, make sure you have a good understanding of how GitHub works. Developers constantly make changes to their code, and GitHub manages them in a central repository. This way, everyone involved with the project can download a given piece of software, make changes and submit updates throughout the development process. This article does not focus on how to use GitHub. If you’re not familiar with the platform, we recommend reading <a href="https://guides.github.com/activities/hello-world/#:~:text=GitHub%20is%20a%20code%20hosting,%2C%20commits%2C%20and%20Pull%20Requests.">this 10-minute guide</a>.</p><p><strong>Find a project</strong></p><p>To maximize your potential for success, take time finding a project on Ovio that matches your personal goals and values. Indeed, finding an open source project to which to contribute isn’t simple. Before selecting a project, it’s important for anyone who wants to get involved to set up goals as well as define requirements such as interests, skills and time availability. Goals are very personal and can range from finding a mentor to practice communicating with developers.</p><ol><li>Choose average-sized projects</li></ol><p>It’s important to choose the right sized project for you. Oftentimes, developers try to work on a project where the code base is too robust or too many people are competing to submit issues. Keep your OSS experience as simple as you can. When there are more contributors than there are issues, it makes working on a project difficult and less productive. Targeting less popular GitHub repositories that are often overlooked can be an easy and effective way to contribute. These projects are more accessible and provide you with a greater opportunity to make a sizable impact.</p><p>2. Use Ovio curated list of contributor-friendly projects</p><p>Target projects that focus on specific technologies you’re interested in working with or learning more about to make your search process simpler. You can also look at projects you already use or enjoy. Using Ovio, you can filter your searches according to your personal skills and interests. By choosing a code language you’re interested in and a topic that matters to you, you’ll have a much more focused list of project options to explore. Once you have access to an organized list of repositories, select a project that has been updated within the past month. This is a good indicator of community health, maintainer engagement and overall dynamism. Ovio’s curated list of repositories is meant to highlight active, ongoing projects. Finally, look for projects with tags, like “good-first-issues” or “help-wanted.” Issue tagging is a strong indicator of maintainers’ efforts to attract external contributors like you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YDjDIifma099oO7W" /></figure><p><strong>Find an issue</strong></p><p>Because every issue is associated with a project, when you discover errors or bugs, you’ll inevitably discover a project. This is an efficient way to get started immediately, but deciding which issues to work on isn’t easy. There are a lot of projects out there, meaning you’ll have plenty of issues to choose from.</p><ol><li>Filter your search with Ovio</li></ol><p>After you’ve filtered your search, according to code language and topics, you can narrow your results by filtering issues based on difficulty level, priority, length of work, etc. One of the easiest ways to search is by filtering issues labels. Many open source projects label their issues to conveniently track them. Make sure the issue has not been claimed yet by looking at the orange tag on the upper left corner. On Ovio, the list of issues is pre-filtered on unassigned issues to make your search easier.</p><p>2. Start Small</p><p>As you filter through issues to find a good one for you, remember to start small. Open source contribution is not a race. Small issues lead to quicker payoff and better chance of success. It will be rewarding when your first contribution is accepted by the maintainer or the community. The more complicated is an issue you select, the longer you’ll postpone getting a payoff.</p><p>3. Select the best match</p><p>If you’re interested in working on the issue, add a comment on GitHub to let the maintainer know you’re interested. You can also save the issue directly on Ovio, so you can jump right back in where you left off next time. Before you start working on the issue, don’t forget to review your selection and choose one that seems achievable considering your experience and time availability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*PBIL5CNapu85cDq-" /></figure><p><strong>Read the project’s guidelines</strong></p><p>Your impact depends upon your ability to adhere to the community’s guidelines. Above all, respect the working conditions of others in the open source community. Many projects include documents, titled “CONTRIBUTORS.md,” which present the preferred way of making contributions. If the project you wish to join does not have a similar document, check other possible places, like the “README.md” or project’s wiki page. Get acquainted with the maintainer’s rules and follow them accordingly. If your work doesn’t meet the project’s criteria, outlined in the contributor’s guidelines, it’s likely to be declined even before the review. These guidelines and conditions serve to protect the time and work of the maintainers. Respecting the rules will reflect positively on your reputation within the community, as well as your contributions.</p><p><strong>Get involved with the community</strong></p><p>Join Slack or Gitter. Because most projects come from an organization, they’re often linked to a community of people. The best way to get noticed and start forming connections is by joining their social network. You can do this by joining their preferred communication channel, which is often a platform, like Slack or Gitter. Some projects use Twitter or Facebook groups as well.</p><p><strong>Show respect for others</strong></p><p>Be inclusive, polite, and express a positive attitude when commenting, coding or discussing with other members of the open source community about a project. If you’re not compliant with the community rules, your contributions might not be integrated.</p><p><strong>Ask questions request feedback</strong></p><p>Don’t hesitate to ask questions or for help from other contributors or maintainers. It demonstrates your commitment to the project and expedites your contributions to the project. Asking for feedback is the best way to improve and show that you care.</p><p><strong>Join the Hacking League (for students only)</strong></p><p>If you are a student looking for an internship, look for the <a href="https://news.mlh.io/introducing-the-mlh-fellowship-externship-09-10-2020">Major League Hacking Externship</a>.</p><p>Whether you’re an experienced developer or a first-time contributor, Ovio can help you throughout the process of making your contribution. Once you become comfortable navigating GitHub and interacting with others in the community, you’ll be able to support the execution of a project and make an impact. To get started today explore <a href="https://ovio.org/">Ovio’s project list</a>.</p><p>Citations</p><p>Red Hat. (2020). <em>The State of Enterprise Open Source</em>. <a href="https://www.redhat.com/en/enterprise-open-source-report/2020"><em>https://www.redhat.com/en/enterprise-open-source-report/2020</em></a>.</p><p>Jeff Stern. (2020). <em>How open source software is fighting COVID-19.</em>Opensource.com. <a href="https://opensource.com/article/20/3/open-source-software-covid19">https://opensource.com/article/20/3/open-source-software-covid19</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57c4170f0c41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oviohub/how-to-get-started-with-open-source-contributions-57c4170f0c41">How to Get Started with Open Source Contributions</a> was originally published in <a href="https://medium.com/oviohub">Ovio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Should Contribute to Open Source Projects]]></title>
            <link>https://medium.com/oviohub/why-you-should-contribute-to-open-source-projects-acfb6e69d301?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/acfb6e69d301</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Tue, 15 Sep 2020 19:05:26 GMT</pubDate>
            <atom:updated>2020-09-30T00:30:01.312Z</atom:updated>
            <content:encoded><![CDATA[<p>With an increasing amount of industry leaders turning to open source solutions, comes more opportunities for developers to invest in their own expertise. Contributing to open source projects, gives you the chance to play a role in the modernization of a variety of IT approaches, such as cloud computing, automation, big data, artificial intelligence and machine learning. By joining this ecosystem of innovation and collaboration, you can make a positive impact on a project that’s right for you. Let’s walk through some of the motivations behind open source collaborating and the value in making a contribution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*sfQ7bjyttONH_TXz" /><figcaption>Thousands of developers have come together in the fight against covid, using, and developing open-source solutions: <a href="https://ovio.org/covid-19">Covid collection</a></figcaption></figure><ol><li><strong>Develop new skills and sharpen existing ones</strong></li></ol><p>Actively participating in an open source project, whether you’re writing code, drafting documentation, or creating graphics, provides a learning opportunity. Whether you’re a student or a senior developer, you’ll gain valuable experience engaging with an ongoing project. You will receive feedback from experienced developers, as well as have the chance to establish yourself in a community with other collaborators. In addition to sharpening your tech skills, the people skills you can learn from participating in an open source project can serve you for work as well.</p><p><strong>2. Boost your visibility</strong></p><p>Because these projects live in open repositories on social coding sites, like Github, you have the chance to build a track record of your work, which anyone can view. Today, tech recruiters are using Github to find new talent. Some teams even use open source contributions to test candidates for software developer jobs. In other words, by making your code public and working on open source code, you’re building an online portfolio easily accessible to potential employers. It’s essential to create a portfolio that represents your work on your own terms. It will supplement your resume and show how you have developed your skills over time.</p><p><strong>3. Get involved with a community</strong></p><p>OSS project participation provides the opportunity to meet a broader variety of people than you are likely to at work or at home. Many projects have contributors from all over the world. When you join an open source community, you immediately become acquainted with solution-oriented people, who also share a common interest in the project. You can learn from each other while working towards a common goal — to do something for others that makes an impact. By simply joining a community, contributing to a PR or commenting on an issue, you will network and engage with new acquaintances!</p><p><strong>4. Make an impact</strong></p><p>The open source community brings people from around the world together to find solutions to today’s most complex challenges. Currently, the open source community plays a vital role in the fight against the Covid-19 pandemic. With thousands of projects and millions of contributors, open source software is being used to support case tracking efforts with models, datasets, visualizations, and digital applications. You can play a part in supporting the healthcare system and our government’s understanding of Covid-19.</p><p><strong>Many ways to contribute</strong></p><p>Open source contributions are not only about code! There are plenty of ways contributors can get involved with a project. Of course, rather a lot of code is involved, but there is more than code to a successful OSS. Here is a list of some contributions:</p><ul><li><strong>Submitting issues</strong> means sending messages about errors in applications and suggesting ways to fix them with a bug report.</li><li><strong>Contributing code</strong> involves sending pull requests with your corrections and improvements.</li><li><strong>Documentation edits</strong> help maintainers provide more information about the technology itself.</li><li><strong>Q&amp;A</strong> …the nature of an open source project is to encourage feedback, questions and suggestions for improvement.</li><li><strong>UX/UI design</strong> is often needed for a variety of projects to improve their functional and visual design</li><li><strong>Code review</strong> and code testing is essential to make sure the software works properly.</li><li><strong>Marketing</strong> initiatives help promote a project to attract more contributors, grow its visibility and increase its credibility within the community.</li><li><strong>Release management</strong> involves managing, planning and controlling the stages of a software build for consumption.</li><li><strong>Security reviews </strong>involve testing the source code for vulnerabilities and analyzing it for weaknesses.</li></ul><p>Bug triage is necessary to address flaws in the function of the software.</p><p>If you’re looking to develop new skills, collaborate with like-minded individuals, distinguish yourself in the open source community, or make an impact on a project that matters to you, consider participating in an open source project. By establishing connections between passionate volunteers and innovative tech projects, Ovio is here to make open source more accessible to you. Get started and see our <a href="https://ovio.org/">curated list of projects</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acfb6e69d301" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oviohub/why-you-should-contribute-to-open-source-projects-acfb6e69d301">Why You Should Contribute to Open Source Projects</a> was originally published in <a href="https://medium.com/oviohub">Ovio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can insufficient open source contributions impact modern businesses?]]></title>
            <link>https://medium.com/oviohub/can-insufficient-open-source-contributions-impact-modern-businesses-d5dd125ebeb1?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5dd125ebeb1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 23:31:59 GMT</pubDate>
            <atom:updated>2020-07-27T23:31:59.023Z</atom:updated>
            <content:encoded><![CDATA[<h3>From ‘consumer only’ to ‘all contributors’</h3><p>Today, open source is integral to product development for a majority of companies. <strong>More than 90%</strong> of professional applications are created using open source components. It seduces every company that wants to build better software more efficiently. Those that contribute are gaining a competitive edge in their own markets as they get to know the technology at a much deeper level than they would by “simply” using the technology. That’s why modern businesses are no longer wondering how many OSS they should integrate but rather how much they want to contribute to OSS. The entire ecosystem is shifting from ‘consumer only’ to ‘all contributors’.</p><h3>A two-sided problem</h3><p>At a time when corporations are consuming open source software at a higher rate than ever, the average OSS project has <strong>less than one</strong> external contributor. It’s a huge pain for developers to know where they can be useful, and it’s incredibly hard for maintainers to find the help they need. Open source development relies on the work of a few, despite the fact that <strong>over 90%</strong> of developers are willing to contribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KTq9-w298ACuUEcp" /></figure><p>Where does this gap come from? Well first, no tool exists to filter projects and find the right opportunities at the intersection of <strong>contributors</strong>’ skills and interests. Finding a matching project is rare and finding the right issue fit is even harder. In other words, contributors spend more time looking for the right opportunity than getting involved. Even when a developer finds a good project match, they are often dissuaded by lengthy, opaque, and difficult onboarding processes that differ wildly from project to project. And this is only one side of the picture…</p><p>… <strong>Maintainers</strong> also have a hard time identifying the right talent. Most project owners don’t have access to sufficient tools or incentives that will support their work. They do their best to increase the visibility of their projects, and if they succeed, they soon feel overwhelmed with the management of a new community. This can lead to a “boom and bust” cycle, however, as many new recruits quickly disappear from the project. Matching specific contributors with their most pressing needs can quickly jam the desired outcome.</p><p>This two-sided problem translates into a poor contribution strategy for<strong> tech companies</strong>. Because there are too many high-value projects with sparse communities, it’s a complex challenge for companies to find and choose which projects to support. This results in having both in-house developers not incentivized to contribute and in-house maintainers not empowered to activate their communities.</p><h3>Why companies should care</h3><p>Open source contributions have a significant impact on companies’ visibility in the wider developer ecosystem, and also affect internal development velocity. Indeed, more contributions decrease risks and create opportunities for software development:</p><ul><li>It lowers the risk that a project maintainer quits causing a company to be stuck with an unmaintained project,</li><li>It lowers the risk of a poor external image when in-house projects are no longer updated,</li><li>It creates the opportunity to shape projects and add new features that can make a solution better, more robust, and more in line with the goals of the company,</li><li>It creates opportunities for stronger branding,</li><li>It creates opportunities for hiring talented developers….</li></ul><p>At Ovio, we believe that more meaningful connections will enable the open source ecosystem to thrive. This is why we created a platform with a curated and personalized selection of open source projects to accelerate contributors matching and revolutionize the way open technology grows. This platform makes it easy for developers to find the right open source tasks and get involved in a project while providing maintainers the tools to attract tech talent and build their communities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L1Kyt8HnxF5kw10J" /></figure><p>Ovio helps companies grow, manage, and showcase their open source program so they can attract and hire a more diverse team. Providing a platform where companies are empowered to build a robust contribution strategy results in positive outcomes:</p><ul><li>Matching talent with specific issues helps drive direct open source engagement.</li><li>Showcasing open source contributions improves project visibility and accelerates velocity.</li><li>Providing OSS performance metrics enables the evaluation of both internal and external contributions and thus, stronger prioritization.</li></ul><p><a href="https://ovio.org/companies/">Discover more</a></p><p><a href="/service/mailto:tiphaine@ovio.org">Reach out to learn more</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5dd125ebeb1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oviohub/can-insufficient-open-source-contributions-impact-modern-businesses-d5dd125ebeb1">Can insufficient open source contributions impact modern businesses?</a> was originally published in <a href="https://medium.com/oviohub">Ovio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[English] My first hike to the top of Mount Shasta]]></title>
            <link>https://medium.com/@tiphaine.boyer/english-my-first-hike-to-the-top-of-mount-shasta-6d953df39a2f?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d953df39a2f</guid>
            <category><![CDATA[hiking]]></category>
            <category><![CDATA[california]]></category>
            <category><![CDATA[mountains]]></category>
            <category><![CDATA[mountaineering]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Thu, 02 Jul 2020 01:19:16 GMT</pubDate>
            <atom:updated>2022-02-05T00:44:49.280Z</atom:updated>
            <content:encoded><![CDATA[<h3>My first hike to the top of Mount Shasta</h3><p>June 20th, 2020, after being confined in my apartment for 4 months because of the COVID pandemic, I decided to ascent Mount Shasta (14,179 ft) with a group of friends from San Francisco. We made up our minds only 3 weeks before the challenge, which left me very little time to get back in shape. I started doing pilates and going for runs in Twin Peaks almost every day.</p><p>Thursday night, after packing our bags, our friends Trinelle and Vic picked us up and we drove four hours towards Shasta. We met with the rest of the group in a cabin near the trail. We’ll spend the night there before starting our first-ever mountaineering experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kasUG0-Ol1Zu1_xd" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sjk50SfXYLRxpZBd" /><figcaption>First view of Shasta / Our cabin</figcaption></figure><p>At 8 am, everyone wakes up and starts packing up their gears aiming to start the hike at 9 am.</p><p>11:30 am, we are starting the hike… We got delayed when we picked up our crampons and ice axes at the rental shop. The first part is called Bunny Flat and begins at 6,800 feet of elevation. It looks much like a classic hike. We walk for 1.7 miles before reaching a cabin, Horse Camp, at 7,880 feet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bl9HZT5lpY7dWzRs" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cMeeYE6PcmL5P11D" /><figcaption>Beginning of the trail with view / Thomas arriving at Horse Camp</figcaption></figure><p>We refill our water bottles for the last time before St Helen lake (10,400 ft) where the camping site is located. The second part of the hike is harder. We have to walk on a sandy trail under a blazing sun. We start feeling the weight of the backpacks on our shoulders.</p><p>Half-way up, we decide to take a lunch break and get some energy. After devouring our sandwiches, we discover the first snowy trail. After only a few minutes, we decide to put on our crampons to ease our ascend. This part is taking longer than expected and we all feel slowed down by our heavy backpacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FJgtGiYtbM0DX99l" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*anm7at3Ovr2VCV9B" /><figcaption>Our group led by Max / Thomas just before reaching the camping site</figcaption></figure><p>Finally, we made it! We already see a lot of tents set up, and no more scooped spots. To avoid spending a chilly night, hikers dig small nests and put the extra snow as a wall around it. It allows to sleep on flat grounds and protect the tents from strong winds. We find a nice area and start digging for our tents. We soon realized that we settled right in the middle of the restroom area… It’s too late; we’ll get used to the smell. While some continue setting up the sleeping area, others boil water to fill our water bottles and cook our diner: couscous with masala sauce.</p><p>But before we can eat, Max explains to the group some self-arrest techniques. Using an ice ax, we can stop ourselves from sliding down the hill. It wasn’t reassuring to practice this, but once we got it, it became quite entertaining. After just a few attempts, we start feeling the impact of elevation: dizziness, stomachache, and headache.</p><p>We quickly eat our food before getting to bed at 9 pm. Unfortunately, none of us will manage to sleep. It’s not because of the cold or because of the lack of comfort. There is no wind, and we carried heavy winter material to be in the best conditions. For me, it’s because of the stress. I started thinking of the self-arrest techniques; I was envisioning the movie <em>Everest</em> and dramatizing the adventure awaiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cxp8M2CCdU3TscWM" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z1ddw6BzFMh4oxf2" /><figcaption>Thomas, Arthur, Cecile, Max, Sebastien, Trinelle et Victoria / Our tents in the snow</figcaption></figure><p>3:30 am, waking up in the middle of the night is not that hard if it’s a sleepless night. We take some strength with protein bars and bananas for breakfast. My teacup is icy; I leave it aside. While getting out of the tent, we can observe the line of lights getting up the mountain already. We realize that we are the last ones to leave. I feel reassured to see that other people are showing us the way. We just need to walk on their steps. I adjust my headlamp and start this night hike, which is a first-ever for me!</p><p>The first steps on the snow are exhausting; I think that my body isn’t awake yet. My legs are okay, but my breath isn’t catching up. After a few meters, Max starts feeling dizzy because of the elevation. With Cécile, his other half, they decide to wait and give themselves more time to adjust. We are a group of 8, but we all have a buddy that will support the other during hard times or an emergency. We pursue the climb while the sunrise is arising. We are getting an incredible view that fills me with joy. At this moment, realizing that I am on Mount Shasta makes me so happy. It’s probably the excitement of the first time or just the feeling that the worst is behind me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PDYzyjTofRP5ItWG" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mKQS3bZbnNB3B5Ck" /><figcaption>First hikers going up / The view</figcaption></figure><p>The hill is getting steeper, but we are hanging in there! We regularly have to take brakes so our breaths can catch up. The oxygen is running scarce.</p><p>I can see the Red Banks on the top, which means the end of the first part. It is said that the first part is the steepest of all, so reaching the end would be such a relief. I tell myself if I can make it to the Red Banks, I’ll be able to go all the way to the Summit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L8UHsr-663cvpqX1" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*93GSAZHj8ScBnJUi" /><figcaption>Victoria and Tiphaine facing the Red Banks / The shadow of Shasta on other mountains</figcaption></figure><p>The first part achieved, we are at Thum Rock (12,923 ft)! It’s an excellent time to take a break. Max and Cécile are catching up; the dizziness dissipated. The wind is getting stronger. We are adding layers and adjusting our coats. I feel my body needs energy, but I cannot eat anything. I manage to eat two dates, which will do the trick for now.</p><p>The next hills are less steep, but that doesn’t make it easier to walk up. The higher we get, the less oxygen there is. On top of that, my lack of sleep is adding weight to my legs. We continue to walk, but motivation is declining. Victoria is getting weaker, and she is thinking of heading back. Her climbing buddy (and life buddy) is making sure she won’t give up, though. Thomas is motivating me as well. He is stunned by my progress (I kept saying I will never make it to the top) and congratulates me every step of the way. It’s a victory for everyone when we reach the end of Misery Hill and arrive at the last part of the ascend: a long plateau and the summit climb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qlY0n0LNcLu8LLNt" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WYc7lvdGjrnq0GKT" /><figcaption>Our group on Misery Hill / Thomas and Tiphaine in front of the summit</figcaption></figure><p>Seeing the Summit, I feel that my body won’t make it. A night without sleep and my incapability to eat is impacting me. I give myself one goal: reaching the end of the plateau, it will be my personal victory. Everyone is exhausted except Thomas, who suddenly feels energized.</p><p>But once I reached my goal, I feel guilty not doing the last meters that separate me from the top. Fine! I will push myself and walk the final steps with my crampons, all the way to the top (14,179 feet elevation).</p><p>Up there, the weather is perfect, and the view stunning! We stay for a while and take in the moment. It’s a magical time; we fell like we can see the whole world above the clouds. The height is imposing, I almost fear it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gmFccVbmbhJ-JK6U" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NdNia0ddNvvFrB5n" /><figcaption>Thomas and Tiphaine at the summit / Sebastien, Arthur, Max, Cécile, Thomas, and Tiphaine at the summit</figcaption></figure><p>The way back down is much lighter for our legs. We just have to slide down to the camping site. It’s a very fun and fast way to hike down a mountain. We are using our ice axes to slow the speed just like a handbrake. After a small break, we start to pack and get ready for the last walk. It’s also the time we decide to test the pooping bags. Yes, you read correctly. We are using bags as toilets as there can be no trace of our presence in the wilderness of California.</p><p>Against all the odds, the way down is psychologically much harder than I thought. My back, feet, and knees are hurting, and it feels as though the pain will never go away. I end up finishing the trail barefoot. When I finally arrive at the parking lot, I find Max lying on the ground, Cécile cheering us, Trinelle and Victoria already unpacking while Sebastien and Arthur are patiently waiting to get in the car, so we can all get a pizza.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zM6lygdWCOHnM2a0" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*btTnjfgx92aBqYKb" /><figcaption>Thomas on the way back / Arthur sliding down the hill</figcaption></figure><p>This first mountaineering experience was an incredible adventure. I felt all the emotions my grandmother would describe every time she showed me her photo albums of mountains she used to climb. Young, she would ascend mounts all over Europe. Her pictures are all impressive, and she always has a good story to share. So yes, the following day, I feel that I made her proud. Indeed, “going above 13,000 feet is something,” she tells me on the phone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L1doVkPLCFkTfvld" /><figcaption>Map of Mount Shasta</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d953df39a2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ma première ascension du Mont Shasta]]></title>
            <link>https://medium.com/@tiphaine.boyer/ma-premi%C3%A8re-ascension-du-mont-shasta-1021eb0f9d68?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/1021eb0f9d68</guid>
            <category><![CDATA[mountains]]></category>
            <category><![CDATA[hiking]]></category>
            <category><![CDATA[california]]></category>
            <category><![CDATA[shasta]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Wed, 24 Jun 2020 16:54:43 GMT</pubDate>
            <atom:updated>2020-07-01T21:37:21.515Z</atom:updated>
            <content:encoded><![CDATA[<h3>[French] Ma première ascension du Mont Shasta</h3><p>Le 20 Juin 2020, après avoir passé 4 mois confinée à cause de la pandémie mondiale, je suis partie faire l’ascension du Mont Shasta (4322 mètres) avec un groupe d’amis de San Francisco. Nous avons pris la décision 3 semaines plus tôt, ce qui me laissait peu de temps pour me remettre en forme après cette longue pause sportive… J’ai fait du pilates et de la course presque tous les jours pour être sûre d’être au niveau.</p><p>Après avoir fait nos sacs le jeudi soir, Trinelle et Victoria passent nous prendre et nous attaquons les 4 heures de route qui nous séparent du Mont Shasta. Nous retrouvons le reste du groupe dans un refuge au pied de la montagne. Nous y passerons la nuit avant de nous lancer dans ce qui sera notre première expérience d’alpiniste.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d62L8oy2dXqRn2cv" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L9tPx9HVEbZoSONn" /><figcaption>Gauche: première vue de Mont Shasta / Droite: notre refuge</figcaption></figure><p>8h, tout le monde se réveille et commence à se préparer pour attaquer la randonnée à 9h.</p><p>11h30, nous débutons la randonnée… Petit retard au démarrage lorsque nous sommes allés chercher l’équipement: crampons, piolet, chaussures et casques. Nous commençons à 2,000m d’altitude la première partie de l’ascension (Bunny Flat), qui ressemble à une randonnée classique. Nous marchons 3.6km avant d’atteindre le premier refuge, Horse Camp à 2,400m d’altitude.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*erD0iLHw0qCHjgxgHxYssw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdIxx50ro8Tf9wL4__sQZA.jpeg" /><figcaption>Gauche: début du chemin avec vue sur Mont Shasta / Droite: Thomas en arrivant à Horse Camp</figcaption></figure><p>On fait une recharge en eau, la dernière avant d’atteindre le campement du Lac St Helen à 3,170m d’altitude. La deuxième partie de cette montée se fait de plus en plus difficile. On commence déjà à sentir le poids des sacs à dos. Nous marchons sur un long sentier de terre en serpentin sous un soleil de plomb… La pause déjeuner est la bienvenue pour recharger les batteries.</p><p>Après avoir englouti nos sandwichs, on découvre le premier chemin enneigé. Il nous faudra que quelques pas pour décider d’enfiler les crampons et gravir la dernière colline avant le campement. Cette montée est dure car nous sommes tous ralentis par le poids de nos gros sacs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0D1oKhmGDQesZpKB" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8pETOri7ZJjZ53HCMUZTRQ.jpeg" /><figcaption>Gauche: le groupe avec Max en tête / Droite: Thomas avant d’atteindre le campement</figcaption></figure><p>Enfin le lac St Helen! On découvre déjà beaucoup de tentes installées et il ne reste plus de places creusées. [Pour essayer de passer une bonne nuit, les randonneurs creusent dans la neige et construisent un petit mur autour de la tente. Cela permet de protéger du vent et de dormir à plat.] Ce n’est pas grave, nous trouvons un petit coin sympa et nous nous mettons à creuser notre nid. C’est à ce moment la que l’on découvre que c’est le coin pipi du campement… Trop tard, nous finirons bien pas nous habituer à l’odeur. On finit de monter les tentes, on fait bouillir de la neige (15 minutes/1 litre) pour remplir nos gourdes et surtout on prépare le festin du soir: semoule et sauce masala.</p><p>Avant de passer à table, Max nous explique comment il faut faire pour s’arrêter avec un piolet, si jamais on glisse sur la pente glacée. C’est pas rassurant, mais lorsqu’on prend le coup de main ça devient un jeu d’enfant! D’ailleurs, l’altitude commence à se faire ressentir au travers d’un mal de tête ou d’un mal de ventre.</p><p>Après le dîner, c’est l’heure du coucher, il est 21h. Malheureusement, personne ne va vraiment dormir. Ce n’est pas à cause du froid ou de notre installation, car il n’y avait pas de vent et on avait apporté et porté un super matériel de camping. Pour ma part c’est à cause du stress. Je ressasse les techniques de <em>self-arrest</em> (planter le piolet dans la neige en cas de glisse), je pense au film Everest, et je dramatise l’aventure qui nous attend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tiNEO-I7ytRG38O0" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HV_dLaXgU7QwzWN0" /><figcaption>Gauche: Thomas, Arthur, Cecile, Max, Sebastien, Trinelle et Victoria / Droite: nos tentes igloo</figcaption></figure><p>Réveil 3h30 du matin. Finalement, quand on a pas fermé l’oeil, c’est pas si difficile de se lever en plein milieu de la nuit. On prend des forces avec des barres et des bananes pour le petit déjeuner. Mon thé en thermos a gelé, je décide de le laisser sur le côté. En sortant de la tente, on aperçoit la colonne de lumières frontales qui gravit la montagne. On réalise qu’on est les derniers à partir, mais je trouve ca rassurant de voir que d’autres êtres humains sont passés avant nous. Surtout que grâce à eux on peut marcher dans leurs traces de pas. J’ajuste ma lampe frontale et c’est parti pour une randonnée de nuit (une première pour moi)!</p><p>Les premiers pas dans la neige sont épuisants, je pense que mon corps n’est pas encore prêt. D’ailleurs, c’est surtout ma respiration qui n’arrive pas à suivre, mes cuisses, elles, ont l’air de résister au choc. Après plusieurs mètres, Max a du mal à s’ajuster à l’altitude et se sent nauséeux. Avec Cécile, son binôme, ils décident d’attendre que cela passe. Nous sommes un groupe de 8, mais nous avons tous un partenaire désigné en cas de coup dur, le mien c’est Thomas. Nous continuons l’ascension et déjà le jour se lève. Nous avons une vue magnifique et c’est un moment de joie intense! Réaliser que j’y suis, sur le fameux mont Shasta, me remplit de bonheur. Ça doit surement être l’excitation du débutant et surtout l’idée que le pire était passé.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NQXHks8aQQiT5UGe" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ofjI0Ot07-RhtcBY" /><figcaption>Gauche: Les premiers randonneurs de la nuit / Droite: la montagne</figcaption></figure><p>La pente est de plus en plus raide, mais on tient le coup! On doit régulièrement s’arrêter pour reprendre notre souffle, l’oxygène se fait rare… Nous apercevons les Red Banks au loin, cela signifie que la fin de la première partie est proche. C’est la plus difficile, alors franchir cette étape serait pour moi un gros soulagement. Si j’atteins les Red Banks, c’est certain, je serais capable d’aller jusqu’au sommet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N7vyVoHpm09HcG26" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ktW9OkKapbZ4GZmKORPxjA.jpeg" /><figcaption>Gauche: Victoria et Tiphaine face au Red Banks / Droite: l’ombre de Shasta sur les autres montagnes</figcaption></figure><p>Première étape franchie, nous sommes à Thumb Rock (3,940m d’altitude)! C’est le bon moment pour prendre une pause. Max et Cécile nous rattrapent, la nausée a fini par passer. Le vent commence à souffler de plus en plus fort, il est temps d’enfiler la cagoule et de fermer le col du manteau. Je n’arrive pas à manger et pourtant je sens que mon corps a besoin de sucre pour continuer… Deux dattes feront l’affaire pour le moment.</p><p>Après avoir franchi les Red Banks, les passages ont moins de dénivelé, mais cela reste tout aussi difficile car la fatigue et le manque d’oxygène ajoutent une lourdeur aux jambes. On continue progressivement mais la motivation décline… Victoria se sent de plus en plus faible et pense à faire marche arrière. Mais c’était sans compter sur le soutien mental de son fiancé. Thomas aussi me motive, il est surpris par ma progression (je n’avais cessé de répéter que que je n’y arriverais pas) et m’encourage à chaque étape! C’est donc une victoire pour toute l’équipe sur la fin de Misery Hill (qui porte bien son nom) lorsque nous arrivons enfin à la dernière étape de cette aventure: un long plateau qui nous mènera jusqu’au sommet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAEMybduzSMvcaDHJqzw-Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nlc5mPrFYnd0g3ts" /><figcaption>Gauche: notre groupe sur Misery Hill / Droite: Thomas et Tiphaine devant le sommet</figcaption></figure><p>En voyant le sommet, je me dis que mon corps ne supportera pas la dernière montée. Ma nuit blanche et l’incapacité de manger me pèsent. Je me donne un objectif: le haut du plateau, ca sera ma victoire! Tout le monde est exténué, sauf Thomas qui trouve un regain d’énergie.</p><p>Mais dès mon objectif atteint, je me dis que c’est dommage de pas faire les derniers mètres, je suis si proche du but. Allez, on attaque le dernier bout de chemin, les derniers coups de crampons, avant d’atteindre le tant attendu sommet du Mont Shasta situé à 4,322 m d’altitude! Il fait un temps magnifique, le vent ne souffle pas si fort et on a une vue incroyable sur 360 degrés. C’est un moment magique et c’est surtout un soulagement. Nous sommes au dessus des nuages et même au dessus de certains avions. C’est une sensation de hauteur impressionnante, d’ailleurs, j’ai un peu le vertige.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iQF1dP-Vq-_jppUy" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Aio6mI_2XgOWageH" /><figcaption>Gauche: Thomas et Tiphaine au sommet / Droite: Sebastien, Arthur, Max, Cécile, Thomas et Tiphaine au sommet</figcaption></figure><p>Le retour sera beaucoup plus agréable pour nos cuisses. Il nous a suffit de glisser sur les fesses jusqu’en bas! C’est un moment très agréable et surtout bien amusant. On utilise le piolet comme frein à main et en un rien de temps on retrouve le campement. Après une courte pause où tout le monde prendra le temps de faire ses besoins dans des sacs en papier (et oui, en Californie on ne laisse pas de traces dans la nature), on reprendra nos gros sacs pour finir la descente à pied.</p><p>Contre toute attente, cette descente est vraiment un moment difficile psychologiquement pour moi. Mon dos, mes pieds et mes genoux souffrent et j’ai l’impression que cela n’en finit pas… Je vais même finir par retirer mes chaussures et marcher pied nus. Lorsque j’arrive enfin au parking, je retrouve Max allongé sur le sol, Cécile qui a encore de la force pour encourager les derniers arrivants, Trinelle et Victoria qui vident déjà leur sacs pendant que Sebastien et Arthur attendent patiemment de pouvoir reprendre la route direction la pizzeria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bzHW36ABsGPpE6BFcynyg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wL5ULSbeE0GcvF7p" /><figcaption>Gauche: Thomas sur le retour / Droite: Arthur en pleine glissade</figcaption></figure><p>Cette première expérience en montagne à été une belle découverte. J’ai ressenti toutes les émotions que ma mamie Monique me décrit chaque fois qu’elle sort l’album de ses aventures d’alpiniste. Elle a parcouru les pics et montagnes d’Europe. Son album regorge de photos impressionnantes et elle a toujours une nouvelle histoire à raconter. Alors oui, le lendemain de l’ascension, j’ai le sentiment d’avoir pris la relève depuis la Californie. En effet, “passer la barre des 4,000 ce n’est pas rien”, me dit-elle au téléphone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PlGoDaPN7kXNL1JtYkgpLg.jpeg" /><figcaption>Carte du Mont Shasta</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1021eb0f9d68" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to engage engineers with digital volunteering opportunities?]]></title>
            <link>https://medium.com/oviohub/how-to-engage-engineers-with-digital-volunteering-opportunities-c402dc79968e?source=rss-1fdda277d65------2</link>
            <guid isPermaLink="false">https://medium.com/p/c402dc79968e</guid>
            <category><![CDATA[impact]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[digital-volunteers]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Tiphaine Boyer]]></dc:creator>
            <pubDate>Wed, 06 May 2020 16:22:16 GMT</pubDate>
            <atom:updated>2020-05-06T16:22:16.335Z</atom:updated>
            <content:encoded><![CDATA[<p>Anyone should have the possibility to make a positive social impact if they want to. At <a href="https://explore.ovio.org/">Ovio</a>, we empower developers to find the perfect open-source software project. We ensure that talented developers can use their most valuable skills to support the causes they care about and where they will have the most impact. Achieving the <a href="https://www.un.org/sustainabledevelopment/sustainable-development-goals/">UN Sustainable Development Goals (SDGs)</a> with technology is the core of our mission.</p><p>We believe that companies have also their part to play. Sharing technology, talent, and money could highly contribute to building a truly collaborative Tech For Good community. That is why we started working with Amazon Web Services (AWS) and their employees. To step up and see how — by giving the proper collaborative tools — an organization can contribute to Open-source software projects.</p><p>In this post, we’ll be highlighting four key elements that enable developers to engage their skills in digital volunteering opportunities:</p><ol><li>Discovering impactful open-source projects</li><li>Matching developers and projects</li><li>Transforming interest into real engagement</li><li>Bringing out the power of open-source</li></ol><p>You will discover the challenges and successes of our collaboration with AWS and its engineering team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycNuYNJEz2osIGjUME4kLA.png" /><figcaption>The Ovio Platform</figcaption></figure><ol><li><strong>Discovering impactful open-source projects</strong></li></ol><p>Curating and vetting meaningful projects takes time and resources. That’s why we spent months looking for projects, organizations, and interesting initiatives. The power of open-source allowed us to quickly build a community of do-gooders and find a variety of technology solutions with important social and environmental impact.</p><p><a href="https://explore.ovio.org/project/WattTime/pyiso">WattTime</a>, for example, creates technology solutions that make it easy for anyone to achieve emissions reductions without compromising cost, comfort, and function. They invented Automated Emissions Reduction (AER), a cutting-edge technology powered by algorithms and machine learning that can shift the timing of flexible electricity use to reduce emissions by synchronizing with times of cleaner energy generation and avoiding dirtier times.</p><p>Another example, the <a href="https://explore.ovio.org/project/WFP-VAM/HRM">World Food Program</a> PRISM project is a platform that combines remote sensing satellite data, government surveys, on-the-ground reports, and machine learning to create alerts, dashboards, and recommendations for countries dealing with environmental disasters. This actionable information enables policymakers to better prepare for and more efficiently respond to disasters and save countless people from displacement, loss of livelihood, or death.</p><p><strong>2. Matching developers and projects</strong></p><p>AWS employees have various passions, different interests, and very specific skills. We set out to create perfect project matches that cater to these individual differences, but we ran into a few difficulties that complicated the process. First, many individuals had fixed ideas of what their involvement in a new project would look like. Second, each project had urgent needs that were changing continuously. Creating a perfect match between skills, interests, and roles demands a strong understanding of both project owners’ expectations and developers’ volunteering capacities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aIPIYexGi6jqRANt" /><figcaption>Mojgan, volunteer from AWS — Amit, project manager at WFP — Eric, CEO at Ovio</figcaption></figure><p>We offered different options for developers. They could be <em>contributors</em> coding to solve issues on Github. Others would be <em>mentors</em> sharing tech recommendations on specific issues. Finally, a few became <em>group leaders</em> engaging their team on one or two projects.</p><p>Val, who’s a Cloud Infrastructure Architect at AWS, created team volunteering sessions. She organized <em>Good Will Wednesday</em> with her team. Every Wednesday, 5 to 20 volunteers would gather via video conference, solve tasks, provide advice, create an architecture diagram, and discuss challenges with the WattTime team.</p><p>We also developed recommendations and useful tips for project owners to make their repos (a project on Github, a folder that holds code) more contributor friendly and their issues more informative. Establishing a tagging strategy and indicating priority needs are among the most important recommendations we provided. We also created project descriptions allowing volunteers to clearly see what impact they would have if they got involved.</p><blockquote>I was looking for an opportunity to give back and join a community of folks willing to do the same while leveraging my experience. I was immediately excited about Ovio because it helped me find the right opportunity for me right away! They matched me with a project that aligns with my technical expertise, delivering values on things that I find important.</blockquote><p>Tyler, a volunteer from AWS</p><p><strong>3. Transforming interest into real engagement</strong></p><p>We had to make projects exciting to get developers’ attention. Creating intelligent matching and describing the impact of each project worked as a strategy to get developers interested, but it was not enough to create sustainable contributions from them. We quickly discovered that developers needed feedback, rewards, or comments about the work they provided to move forward and continue contributing. They had to be able to measure their impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y7BpF7v7jJNvMFk8" /><figcaption>Developer profile dashboard</figcaption></figure><p>We then started working on reporting developers’ contributions. We created a dashboard, both for developers and their managers, where they could track engagement. This dashboard allows developers to evaluate their work and feel rewarded for their actions. They are able to share some key metrics with their colleagues, family, and friends. It also allowed AWS managers to measure their employees’ motivation levels as well as their company’s overall impact.</p><blockquote>Our volunteer is super passionate and engaged with the project! We have added her to our Slack and integrated her into our engineering workflow, we also have a weekly sync, at her request, to answer questions she has.</blockquote><p>Jack, a project manager at Replate</p><p><strong>4. Bringing out the power of open-source</strong></p><p>Thinking about a project in an open and collaborative way attracts outside contributions and accelerates technology development. Without a strong community of open source developers behind them, many organizations building software for important challenges lag behind the needs of users. By inviting the world to collaborate on a project, the open-source community invites people from all around the globe to not only help develop an impactful solution but also adapt and re-use it, wherever they are. Thanks to open-source, we were able to discover impactful and innovative projects (1), match developers to the right opportunities (2), and track their contributions (3). Open-source enabled us to create these meaningful matches and fulfill developers’ ambitions while empowering projects to develop faster.</p><p>When a crisis like COVID-19 strikes, open collaboration and digital volunteering strives. Indeed, during these challenging times, open-source revealed its power to help those fighting the pandemic by developing cross-border solutions. Github alone gathers more than 30,000 repositories related to the virus and the number keeps growing. For engineers, developers, designers, managers, and tech companies looking for ways to get involved, open-source is the most efficient way to do so. Our collection of <a href="https://explore.ovio.org/covid-19">COVID-19 projects</a> will help you find out how!</p><p>Register with Ovio <a href="https://explore.ovio.org/users/profile">https://explore.ovio.org/users/profile</a> and contribute now!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c402dc79968e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/oviohub/how-to-engage-engineers-with-digital-volunteering-opportunities-c402dc79968e">How to engage engineers with digital volunteering opportunities?</a> was originally published in <a href="https://medium.com/oviohub">Ovio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>