How to Magician

Resource management: a necessary evil

To operate, shared resources must be directed.
Organizing people and resources involves 🔥power🔥.

• Power attracts
• Power agglomerates
• Power corrupts

Self-organizing

Social coordination between individuals.
Guide and displace power accumulation.

Challenges:

• Computationally expensive for humans
• Requires taking responsibility

How To Self-organize

• find your shared culture, goals, values
• declare your principles
• establish processes, frameworks

An Invitation to Participate

Towards a Fellowship of Ethereum Magicians

We propose to create a Fellowship within which the Ethereum community can:

• self-organize to maximize technical opportunities
• share ideas
• work together effectively, online and in person, across national, organizational and other boundaries

Fellowship Vision

The Goal: To keep Ethereum The Best It Can Technically Be.

The Mission: To Nurture Community Consensus on the technical direction and specification of Ethereum.

The Work: Primarily, high-quality Ethereum Improvement Proposals (EIPs), accepted by a consensus of the Community.

Fellowship Principles

1. Open Process
2. Individual Participation
3. Technical Responsibility
4. Technical Competence
5. "Rough Consensus and Running Code"

Fellowship Principles

1. Open Process. Any interested person can participate in the work, know what is being decided, and make his or her voice heard on the issue.

2. Individual Participation. Membership is not formal. We are a Fellowship of individuals rather than organizations, companies, governments or interest groups.

3. Technical Responsibility. 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.

Fellowship Principles

4. Technical Competence. 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.

5. "Rough Consensus and Running Code." 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.

Fellowship Practices

1. Online Presence
2. In-Person Work
3. Iterative Workflow

Fellowship Practices

Online Presence

• Curated web pages, including information about the Fellowship, a calendar of upcoming events, and links to useful resources.
• Accessible discussion forums, with at least a threaded web interface and email integration.

 

Fellowship Practices

In-Person Work

• Triannual meetings, two coordinated with Devcon and EthCC and one in July.
• 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.

Fellowship Practices

Iterative Workflow

• Participants do research, gain experience, present their work, and make proposals.
• Proposals are discussed and reworked, online and in person, until consensus is reached.