<?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[maintainer.io - Medium]]></title>
        <description><![CDATA[Guides to maintaining code on GitHub - Medium]]></description>
        <link>https://medium.com/maintainer-io?source=rss----65e2d9a16696---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>maintainer.io - Medium</title>
            <link>https://medium.com/maintainer-io?source=rss----65e2d9a16696---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:38:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/maintainer-io" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Your Seat On The Rollercoaster: Getting Started with A Blockchain Open Source Project]]></title>
            <link>https://medium.com/maintainer-io/the-following-is-the-first-in-a-series-of-posts-about-open-source-blockchain-projects-73e7728a68be?source=rss----65e2d9a16696---4</link>
            <guid isPermaLink="false">https://medium.com/p/73e7728a68be</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Randall Mardus]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 15:24:49 GMT</pubDate>
            <atom:updated>2018-03-21T15:24:49.021Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The following is the first in a series of posts about open source blockchain projects. Our goals are to highlight projects of note, to get our hands dirty by actively contributing to them, and to share our experiences with our readers so they can, if they so wish, do so as well.</em></p><p>In the startup world the saying goes, “If you’re offered a seat on a rocket ship, don’t ask what seat.” In the blockchain world the saying may as well be, “If you’re offered a seat on a roller coaster, walk straight past the sign that says you need to be this high to ride this ride to your seat on said rollercoaster.”</p><p>The last couple of years the popularity of the blockchain has experienced a roller coaster ride to say the least. And I’m not talking about a roller coaster of the <a href="https://www.youtube.com/watch?v=5Q5w78rEsZQ">Wacky Worm</a> variety, more like the <a href="https://en.wikipedia.org/wiki/Kingda_Ka,%20https://www.youtube.com/watch?v=ysHXnVoS7JI">Kingda Ka</a> variety. The well-documented fluctuations in the price of such blockchain-backed cryptocurrencies as <a href="https://bitcoin.org/en/">Bitcoin</a>, <a href="https://ripple.com/">Ripple</a>, and <a href="https://ethereum.org/">Ethereum</a> have brought people to the blockchain and made others run away from it. The same can be said of open source blockchain projects.</p><p><a href="https://www2.deloitte.com/insights/us/en/industry/financial-services/evolution-of-blockchain-github-platform.html">According to a report</a> by the consulting firm <a href="https://www2.deloitte.com/us/en/services/consulting.html">Deloitte</a>, developers created over 26,000 new open source blockchain projects in 2016. Unfortunately, only 8% of those are actively managed.</p><p>With such uncertainty, where does one go to learn more about the blockchain by participating in one of its open source projects?</p><p>We’ve done some research and have come up with seven active and interesting open source blockchain projects around today.</p><p>We have chosen the following open source blockchain projects based on a number of criteria. The criteria are projects that are active, that have more than just a handful of members, that have a good number of commits, and that have an easy to understand focus. Projects that do not meet these criteria are more difficult to participate in as they may have been abandoned, may have a high flake factor among members, and may be difficult to work on if their goal is not clear.</p><p>And so, without further ado, here are eight open source blockchain projects, in no particular order, to look into if you want to look under the blockchain hood and build up some blockchain developer experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*UCtAV3cW_38CzogbzYksRA.png" /></figure><ol><li>If cryptocurrency and smart contracts are of interest to you, a good place to start is the <a href="https://www.ethereum.org/;%20https://github.com/ethereum">Ethereum</a> blockchain application platform.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*7qRguGvnGomhBvdH4mYeQw.png" /></figure><p>2. If you are interested in learning more about private enterprise blockchains, the <a href="https://github.com/hyperledger">Hyperledger Project</a> under the aegis of the <a href="https://www.linuxfoundation.org/">Linux Foundation</a> has a number of different projects for you to contribute to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jW63R9tNbZiwVEgh6WcFOQ.png" /></figure><p>3. Want to work on Bitcoin? You can do so at <a href="https://github.com/bitcoin/bitcoin">Bitcoin Core</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*EFtpQ_JSNMX60hV2BoYR1w.png" /></figure><p>4. Want to help build a software library for working with Bitcoin? Then dig in to <a href="https://bitcoinj.github.io/,%20https://github.com/bitcoinj/bitcoinj">bitcoinj</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/215/1*Y1L01YWBDUwwhl8khM6bmw.png" /></figure><p>5. Want to get a little further out there with Bitcoin? Then check out the <a href="https://github.com/ElementsProject/elements,%20https://elementsproject.org/">Elements</a>, a collection of feature experiments and extensions to the Bitcoin protocol.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*DvAgEsI3Fy6AcECDqMKM6g.png" /></figure><p>6. Interested in digital assets of the non-cryptocurrency variety? Then there is <a href="https://www.factom.com/,%20https://github.com/FactomProject">Factom</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*cbRtphBbtkxy8t712zrqbA.png" /></figure><p>7. Want to help build the next great internet browser? Then <a href="https://brave.com/index/,%20https://github.com/brave/browser-laptop">Brave</a> is the project for you. Brave uses its token (BAT, Basic Attention Token) to let readers reward content makers whose websites they visit instead of relying on ads that interrupt readers’ experiences and load times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/167/1*eF3pf8d18O61RQlCJWd45w.png" /></figure><p>8. The <a href="https://github.com/ipfs/ipfs,%20https://ipfs.io/">InterPlanetary File System</a> is a “peer-to-peer hypermedia protocol to make the web faster, safer, and more open” that “could complement or replace HTTP.” <a href="https://www.youtube.com/watch?v=8CMxDNuuAiQ">Here</a>’s a video that goes into more detail about how it works and what it hopes to achieve.</p><p>In future posts we will pick a blockchain open source project to contribute to, jump in, and then walk you through how you can do the same.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73e7728a68be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maintainer-io/the-following-is-the-first-in-a-series-of-posts-about-open-source-blockchain-projects-73e7728a68be">Your Seat On The Rollercoaster: Getting Started with A Blockchain Open Source Project</a> was originally published in <a href="https://medium.com/maintainer-io">maintainer.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Deprecate A Repository on GitHub]]></title>
            <link>https://medium.com/maintainer-io/how-to-deprecate-a-repository-on-github-8f0ceb9155e?source=rss----65e2d9a16696---4</link>
            <guid isPermaLink="false">https://medium.com/p/8f0ceb9155e</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[guide]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[maintenance]]></category>
            <dc:creator><![CDATA[Richard Littauer]]></dc:creator>
            <pubDate>Mon, 14 Aug 2017 14:27:58 GMT</pubDate>
            <atom:updated>2017-08-14T14:35:26.154Z</atom:updated>
            <content:encoded><![CDATA[<p>Once, you had a shining, beautiful repo, full of hope and joy. But now you need to state cleanly and clearly that a repository is no longer going to be maintained, isn’t going to be looked at, and should no longer be of interest to anyone. It is kept for archival purposes.</p><p>GitHub needs to get around to making a DEPRECATED tag. They haven’t done this yet, although there’s clearly a gross amount of interest - just look at <a href="https://github.com/isaacs/github/issues/144">isaacs/github#144.</a>.</p><p>There’s a few reasons you could be deprecating a repository, and the steps you should take for them are different. For a project that no one uses, some simple documentation changes should do the trick. For a project that is actively in use which you want to step away from or deprecate entirely, there’s a bit more legwork.</p><p>Note: I have made a <a href="https://gist.github.com/RichardLitt/741cb6f2fd6c75c0c5f51958160853a9">checklist</a> from this article you can follow. You can edit this article on <a href="https://github.com/RichardLitt/knowledge/blob/master/how-to-deprecate-a-repository-on-github.md">GitHub</a>.</p><h4>Deprecating a project no one uses</h4><p>Here’s what you do to deprecate an inactive repository.</p><ul><li><strong>Change the GitHub description</strong>. This is often the first thing people see for the repository, and the first line that people will see if looking at the repository in the Organization view. The most important thing to do is to add the word DEPRECATED at the front of the description. This clearly marks it will not be updated. You can also add an emoji to it. ⛔️ DEPRECATED &lt;former description&gt; makes it pop out a bit more.</li><li><strong>Add GitHub topics</strong>: deprecated, obselete, and archived are all good ones.</li><li><strong>Edit the title of the README</strong>. Remove the current title, and instead write # DEPRECATED.</li><li><strong>Add a reason to the README</strong>, at the top, stating that: “This is no longer supported, please consider using XXX instead.” If there is a reason for deprecating the repository, add it here. It should be unambiguous to anyone visiting the repository that it will not be maintained or updated again.</li><li><strong>Update any licenses or liability wavers</strong>. By updating them, you make sure that they are legally valid, going forward. This can stop questions popping up in the years to come, if people rediscover the project and want to use it. Note: I am not your lawyer. If you have questions, seek legal counsel.</li><li><strong>Add a </strong><strong>no-maintenance-intended badge.</strong> This is another visible way of pointing out that you’re not going to keep updating this project, and the idea comes from <a href="http://unmaintained.tech/">unmaintained.tech</a>.</li></ul><p>I’ve also heard of people add a large image saying Deprecated in some way to the README. This might be a good move, if you’re so inclined. Have fun with it.</p><h4>Deprecating active projects</h4><p>You, as an open source contributor, are not under any moral obligation to continue the work, in most cases, even if people are using a project. You have a right to walk away from your project. However, you can still be kind, and the way you walk away from a project can determine how you remember a project. It is important to feel that you did all you could to make the project thrive, if it could have.</p><p>If you are no longer interested in maintaining the repository, but users are still actively using it, open an issue a few weeks or a month before you plan on deprecating the repo. State clearly that you are not interested in continuing maintenance of the project, and you are going to close the project down. You can do a few things:</p><ul><li><strong>Ask people to use a different project</strong>, which solves the same problem as yours (and hopefully has more features and better UX).</li><li><strong>Ask people to fork</strong> the project and take over maintenance going forward.</li><li><strong>Ask contributors to step up</strong> to become collaborators and maintainers. Offer them access to the repository, so that they can maintain it for you, while you offload your responsibilities.</li></ul><p>If you are interested in the project continuing, but don’t need it to be tagged with your name anymore, you can do this:</p><ul><li><strong>Move ownership</strong> of the repository to another maintainer. If, for instance, the project was at RichardLitt/awesome-project, you could give it to someone you trust who is maintaining it. Do this in the repository settings. For instance, I could ask my friend Gregor to take it over, and move it to gr2m/awesome-project.</li><li><strong>Set up an organization</strong> to take over the project. If the project is large, and there is an ecosystem around it, it is sometimes smart to set up an organization to take if over, so that it is clear that you are not in charge of it, but all the members of the organization. This is a similar option to moving it to another maintainer, but it stops you from needing to choose one sole maintainer to take it over.</li></ul><h4>If it is a JavaScript project on npm</h4><ul><li><strong>Use </strong><a href="https://docs.npmjs.com/cli/deprecate"><strong>npm deprecate</strong></a> to deprecate it. Don’t forget to publish.</li><li><strong>Edit the description</strong> to include the badge, as on GitHub. ⛔️ DEPRECATED &lt;former description&gt; would be useful. Don’t forget to publish a patch with the new metadata.</li></ul><h4>Other options</h4><p>Until GitHub implements an archive feature publicly, there are a few other options for deprecating repositories.</p><ul><li><strong>Change the repo name</strong>. I would not recommend changing the title of the repository to something like &lt;project&gt;-deprecated, although I have seen this before and it is something you could consider. I find it affects recall for anyone who knew of the project and wants to find it later, and it is not as useful given the above steps are done.</li><li><strong>Make an archive organization</strong>. One is to make a project-archive organization, and move all repositories there. This makes it clear in the name that the repo has been archived, but doesn’t let the old cruft stick around in your old organization.</li><li><strong>Make it private.</strong> Another possible step is to make any deprecated repository private. This is useful if the code could be considered dangerous, or if the information in it will lead new developers astray in ways which really aren’t useful. The benefits of making a repository private is that your team — the people who are most likely to have known about the project and least likely to misunderstand it — can still see it.</li></ul><h4>Anything else</h4><p>Nope, that’s it. You’ve deprecated your project. Go and enjoy your life, make new things, and don’t lose any sleep over it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f0ceb9155e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maintainer-io/how-to-deprecate-a-repository-on-github-8f0ceb9155e">How To Deprecate A Repository on GitHub</a> was originally published in <a href="https://medium.com/maintainer-io">maintainer.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>