<?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"><channel><title><![CDATA[Why the OPF Uses Github]]></title><description><![CDATA[<p dir="auto">The OPF uses GitHub to host and manage all of its software projects. There are several reasons for this:</p>
<ul>
<li>
<p dir="auto">GitHub is the biggest online platform for open source software projects in the world.</p>
</li>
<li>
<p dir="auto">Its toolset, including issue management, contribution tracking and code review, is free for open source projects.</p>
</li>
<li>
<p dir="auto">GitHub provides a sustainable home for our projects. If the OPF were to cease to exist, our projects would continue to be available.</p>
</li>
</ul>
<p dir="auto"><strong>Why Should You Use GitHub</strong></p>
<p dir="auto">GitHub is a great way to get involved in open source software development. It's used by thousands of projects and millions of developers. It's a great way to learn about software development and to build your skills. It's also a way to show off your skills as your work is attributed to you on a public platform.</p>
<p dir="auto"><strong>What if I Can't Use GitHub?</strong></p>
<p dir="auto">If you really can't use GitHub, but want to contribute to the Hackathon, please get in touch with us on <a href="mailto:info@openpreservation.org" rel="nofollow ugc">info@openpreservation.org</a> and we'll see what we can do.</p>
<p dir="auto">We look forward to working and learning with you. We’ll also be listening to you and will cover ad-hoc topics if there is enough interest among the attendees.</p>
]]></description><link>https://community.openpreservation.org//topic/30/why-the-opf-uses-github</link><generator>RSS for Node</generator><lastBuildDate>Tue, 21 Apr 2026 04:52:34 GMT</lastBuildDate><atom:link href="https://community.openpreservation.org//topic/30.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 26 Jul 2023 12:09:28 GMT</pubDate><ttl>60</ttl></channel></rss>