<?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 Greg Colvin on Medium]]></title>
        <description><![CDATA[Stories by Greg Colvin on Medium]]></description>
        <link>https://medium.com/@gregcolvin?source=rss-bb12ab54c0e6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o-D-IlNg7YYhU7IETzGypg.png</url>
            <title>Stories by Greg Colvin on Medium</title>
            <link>https://medium.com/@gregcolvin?source=rss-bb12ab54c0e6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:35:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gregcolvin/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[An open invitation to participate in a Fellowship of Ethereum Magicians]]></title>
            <link>https://medium.com/@gregcolvin/an-open-invitation-to-participate-in-a-fellowship-of-ethereum-magicians-44ee1af97af5?source=rss-bb12ab54c0e6------2</link>
            <guid isPermaLink="false">https://medium.com/p/44ee1af97af5</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Greg Colvin]]></dc:creator>
            <pubDate>Mon, 12 Feb 2018 18:51:03 GMT</pubDate>
            <atom:updated>2018-02-24T22:01:48.967Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*pVa6iWKZo77Eq1NAorKI7Q.gif" /><figcaption>Artwork © Ian John Meikle</figcaption></figure><p><em>James Pitts and I would like to invite the community to come together and participate in improving the Ethereum improvement process (and so much more).</em></p><p><em>Some notes to the reader:</em></p><ul><li><em>This proposal is to jump-start the process. Help us shape this effort by getting involved at </em><a href="https://ethereum-magicians.org/"><em>ethereum-magicians.org</em></a><em>, the ethereum/governance Gitter channel and attending our workshop at </em><a href="https://ethcc.io/"><em>EthCC</em></a><em>.</em></li><li><em>This proposal is written up in a Google Doc located at </em><a href="https://goo.gl/DrJRJV"><em>goo.gl/DrJRJV</em></a><em>. Feel free to make suggestions.</em></li></ul><p><em>And now for the proposal:</em></p><h3>✨ Towards a Fellowship of Ethereum Magicians ✨</h3><p><em>Any sufficiently advanced technology is indistinguishable from magic.</em><br> — Arthur C. Clarke</p><p>We propose to create a Fellowship within which the Ethereum community can self-organize to maximize technical opportunities, share ideas and work together effectively, online and in person, across national, organizational and other boundaries.</p><h3>Fellowship Vision</h3><p><strong>The Goal.</strong> To keep Ethereum <em>The Best It Can Technically Be</em>.</p><p><strong>The Mission.</strong> To <em>Nurture Community Consensus</em> on the technical direction and specification of Ethereum.</p><p><strong>The Work.</strong> Primarily, high-quality <em>Ethereum Improvement Proposals</em> (EIPs), accepted by a consensus of the Community.</p><h3>Fellowship Principles</h3><p><strong>Open Process.</strong> Any interested person can participate in the work, know what is being decided, and make his or her voice heard on the issue.</p><p><strong>Individual Participation.</strong> Membership is not formal. We are a Fellowship of individuals rather than organizations, companies, governments or interest groups.</p><p><strong>Technical Responsibility.</strong> The Fellowship accepts responsibility for all aspects of the Ethereum protocol specification. The Fellowship may take responsibility for related specifications proposed to it in the future.</p><p><strong>Technical Competence.</strong> The Fellowship seeks consensus on proposals where we have the necessary competence. The Fellowship is willing to listen to technically competent input from any source.</p><p><strong>“Rough Consensus and Running Code.”</strong> Consensus is not unanimity or majority vote. Rather, it is based on the combined technical judgement of our participants and our real-world experience in implementing and deploying our specifications.</p><h3>Fellowship Practices</h3><p><strong>Online Presence</strong></p><ul><li>Curated web pages, including information about the Fellowship, a calendar of upcoming events, and links to useful resources.</li><li>Accessible discussion forums, with at least a threaded web interface and email integration.</li></ul><p><strong>In-Person Work</strong></p><ul><li>Triannual meetings, two coordinated with Devcon and EthCC and one in July.</li><li>Meetups, discussions, presentations, workshops, hackathons, and other relevant activities. These can organized by participants on an ad-hoc basis or with the sponsorship of the Fellowship.</li></ul><p><strong>Iterative Workflow</strong></p><ul><li>Participants do research, gain experience, present their work, and make proposals.</li><li>Proposals are discussed and reworked, online and in person, until consensus is reached.</li></ul><p>✨</p><p><em>Call to action: please contribute to the Google Doc located at </em><a href="https://goo.gl/DrJRJV"><em>goo.gl/DrJRJV</em></a><em>. Also, please ask questions in the </em><a href="http://gitter.im/ethereum/governance"><em>ethereum/governance Gitter Channel</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44ee1af97af5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>