Skip to content

Commit

Permalink
Refine content
Browse files Browse the repository at this point in the history
  • Loading branch information
DrW3RK committed Jan 25, 2024
1 parent 1a0a15c commit 9c3c4b6
Show file tree
Hide file tree
Showing 2 changed files with 39 additions and 29 deletions.
67 changes: 38 additions & 29 deletions docs/learn/learn-polkadot-technical-fellowship.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,60 +9,67 @@ slug: ../learn-polkadot-technical-fellowship

import RPC from "./../../components/RPC-Connection";

## The Polkadot Technical Fellowship

The Technical Fellowship is a self-governing body of experts and developers of Polkadot and Kusama
networks protocols. It operates on-chain through the Polkadot
[Collectives](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/fellowship/referenda)
and off-chain through the [Polkadot Fellows](https://github.com/polkadot-fellows) repository.

:::info Historical Context: From the Technical Committee to the Technical Fellowship

The Polkadot Technical Fellowship was established in 2022. In Polkadot OpenGov, this fellowship
replaces the [Technical Committee](./learn-governance.md#technical-committee) in Governance v1, and
will serve both the Polkadot and Kusama networks. Unlike the Technical Committee in Governance V1
which was limited to three entities, the Fellowship is designed to be far broader in membership
(i.e. to work well with even tens of thousands of members) and with far lower barriers to entry
(both in terms of administrative process flow and expectations of expertise).

For more information about the Fellowship, read through the
system chain and off-chain through the [Polkadot Fellows](https://github.com/polkadot-fellows)
repository.

:::info Historical Context

The Polkadot Technical Fellowship was established in 2022 and plays an important role in the
Polkadot OpenGov. This fellowship replaced the
[Technical Committee](./learn-governance.md#technical-committee) from Polkadot's first iteration of
governance, and will be serving both the Polkadot and Kusama networks. This Fellowship is designed
to be far broader in membership (i.e. to work well with even tens of thousands of members) and with
far lower barriers to entry both in terms of administrative process flow and levels of expertise.
For more information, read through the
[Fellowship Manifesto](https://github.com/polkadot-fellows/manifesto/blob/0c3df46d76625980b8b48742cb86f4d8fa6dda8d/manifesto.pdf).

:::

Apart from the collectives system chain and the GitHub repository, the Polkadot Technical Fellowship
uses multiple public avenues to discuss updates related to the Polkadot protocol. Their public
also uses multiple public avenues to discuss updates related to the Polkadot protocol. Their public
discussions can be viewed on [this chatroom](https://matrix.to/#/#fellowship-members:parity.io) and
their monthly meetings are posted to this OpenDev - Polkadot Fellowship Core Dev Call
[YouTube playlist.](https://www.youtube.com/watch?v=5P6Axm4JrmQ&list=PLtyd7v_I7PGlDJCCCLGLjJ0yv33JAEE_-)

## Technical Fellowship Referenda

Members of the Fellowship can vote on any given Fellowship proposal and the aggregated opinion of
the members (weighted by their rank) constitutes the Fellowship's collective opinion. The list of
current and historic fellowship referenda can be viewed on
[Polkassembly for Collectives.](https://collectives.polkassembly.io/). The fellowship's governance
model has multiple tracks with their own approval and support parameters, where the votes are
weighted by the rank of the member.
The fellowship governance is primarily used for its membership management,
[approving RFCs](https://github.com/polkadot-fellows/RFCs) and whitelisting Polkadot OpenGov
proposals created on the whitelist track.
The fellowship's governance model has multiple tracks with their own approval and support
parameters, where the votes are weighted by the rank of the member. Members of the Fellowship can
vote on any given Fellowship proposal and the aggregated opinion of the members (weighted by their
rank) constitutes the Fellowship's collective opinion. The list of current and historic fellowship
referenda can be viewed on [Polkassembly](https://collectives.polkassembly.io/) or
[Subsquare.](https://collectives.subsquare.io/) The fellowship governance is primarily used for its
membership management, [approving RFCs](https://github.com/polkadot-fellows/RFCs) and whitelisting
Polkadot OpenGov proposals created on the whitelist track.

## Membership and Ranking

## Technical Fellowship Membership and Ranking
The Polkadot technical Fellowship was initally [seeded](https://github.com/polkadot-fellows/seeding)
with its members and their corresponding ranks, and got
[added on to Polkadot's Collectives](https://polkadot.polkassembly.io/motion/403) system chain.

### Becoming a Member

As a member of the Polkadot Technical Fellowship, you expected to faithfully uphold the below
:::note

The fellowship manifesto states that any account may register to become a candidate for a basic
deposit, but that feature has not been added to the collectives runtime yet.

:::

As a member of the Polkadot Technical Fellowship, you are expected to faithfully uphold the below
tenets:

- Sincerely uphold the interests of Polkadot and avoid actions which clearly work against it.
- Respect the philosophy and principles of Polkadot.
- Respect the operational procedures, norms and voting conventions of the Fellowship.
- Respect your fellow Members and the wider community.

Membership to the Polkadot Technical Fellowship is administered through the
[core fellowship](https://github.com/paritytech/polkadot-sdk/blob/master/substrate/frame/core-fellowship/src/lib.rs)
calls on the Polkadot Collectives System parachain.
To be added as a candidate of the Polkadot Technical Fellowship, a pre-existing member with rank
greater than or equal to 2 should initiate the process.

### Ranking System

Expand All @@ -83,6 +90,8 @@ To support these conditions, the Fellowship has a
expectations for individuals to attain and retain any given rank. Higher ranks can vote and promote
lower ranks based on this [manifesto](https://github.com/polkadot-fellows/manifesto).

### Promotion and Demotion

**Demotion** occurs automatically after a given period has elapsed, and the member is unable to
defend their position to their peers.

Expand Down
1 change: 1 addition & 0 deletions polkadot-wiki/sidebars.js
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,7 @@ module.exports = {
items: [
"learn/learn-polkadot-opengov",
"learn/learn-polkadot-opengov-origins",
"learn/learn-polkadot-technical-fellowship"
],
},
"learn/learn-polkadot-opengov-treasury",
Expand Down

0 comments on commit 9c3c4b6

Please sign in to comment.