forked from anoma/namada-docs
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Namada community & GitHub actions deploy
- Loading branch information
1 parent
2b575f2
commit a123fcb
Showing
26 changed files
with
879 additions
and
101 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
name: Publish namada-community | ||
|
||
on: [push] | ||
paths: | ||
- "packages/community/**" | ||
|
||
jobs: | ||
publish: | ||
runs-on: ubuntu-latest | ||
permissions: | ||
contents: read | ||
deployments: write | ||
name: Publish namada-community to Cloudflare Pages | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v3 | ||
|
||
- name: Set up Node.js | ||
uses: actions/setup-node@v4 | ||
with: | ||
node-version: "16" | ||
|
||
- name: Install dependencies | ||
run: npm install | ||
|
||
- name: Install next-on-pages | ||
run: npm install -g @cloudflare/next-on-pages@1 | ||
|
||
- name: Build page community page | ||
run: npm run build:community:page | ||
|
||
- name: Publish to Cloudflare Pages | ||
uses: cloudflare/pages-action@v1 | ||
with: | ||
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }} | ||
accountId: ${{secrets.CLOUDFLARE_ACCOUNT_ID }} | ||
projectName: namada-community | ||
directory: ./packages/community/.vercel/output/static | ||
# Optional: Enable this if you want to have GitHub Deployments triggered | ||
gitHubToken: ${{ secrets.GH_TOKEN }} | ||
wranglerVersion: '3' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
name: Publish namada-docs | ||
|
||
on: [push] | ||
paths: | ||
- "packages/docs/**" | ||
|
||
jobs: | ||
publish: | ||
runs-on: ubuntu-latest | ||
permissions: | ||
contents: read | ||
deployments: write | ||
name: Publish namada-docs to Cloudflare Pages | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v3 | ||
|
||
- name: Set up Node.js | ||
uses: actions/setup-node@v4 | ||
with: | ||
node-version: "16" | ||
|
||
- name: Install dependencies | ||
run: npm install | ||
|
||
- name: Install next-on-pages | ||
run: npm install -g @cloudflare/next-on-pages@1 | ||
|
||
- name: Build page community page | ||
run: npm run build:docs:page | ||
|
||
- name: Publish to Cloudflare Pages | ||
uses: cloudflare/pages-action@v1 | ||
with: | ||
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }} | ||
accountId: ${{secrets.CLOUDFLARE_ACCOUNT_ID }} | ||
projectName: namada-community | ||
directory: ./packages/docs/.vercel/output/static | ||
# Optional: Enable this if you want to have GitHub Deployments triggered | ||
gitHubToken: ${{ secrets.GH_TOKEN }} | ||
wranglerVersion: '3' |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
import { withLocales } from 'nextra/locales' | ||
|
||
export const middleware = withLocales((request) => { | ||
}) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
{ | ||
"index": "Introduction", | ||
"trusted-setup": "Trusted Setup", | ||
"validators": "Validators", | ||
"community-builder-handbook": "Community Builder Handbook", | ||
"cb-rpgf-round-1": "CB RPGF Round #1" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
{ | ||
"index": "Введение", | ||
"trusted-setup": "Доверенная настройка", | ||
"validators": "Валидаторы", | ||
"community-builder-handbook": "Руководство для строителей сообщества", | ||
"cb-rpgf-round-1": "CB RPGF Раунд #1" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
{ | ||
"index": "Введення", | ||
"trusted-setup": "Надійне налаштування", | ||
"validators": "Валідатори", | ||
"community-builder-handbook": "Посібник розбудови спільноти", | ||
"cb-rpgf-round-1": "CB RPGF Раунд #1" | ||
} | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# CB RPGF Round 1 | ||
|
||
The Namada protocol could not be built without public goods and the community wouldn’t be where it is today without the help of the early Community Builders – brought together by the [shared mission](https://namada.net/vision) of using, educating, and collaborating to build privacy. Namada’s native token is not only used for proof-of-stake and governance, but also to [align the incentives](https://namada.net/blog/namada-s-positive-sum-economics) of the community with the network. | ||
|
||
The [Anoma Foundation](https://anoma.foundation/) has announced they will allocate 10,000,000 of Namada’s native token in the genesis block proposal to the selected recipients of the first Namada Community Builder RPGF Round – every active Community Builder member can be a potential recipient, dating back to the beginning of the community’s history. This includes early validators who have participated in previous testnets and have meaningfully worked to assist other validators in gaining access to, raising issues with, or triaging solutions for previous testnets. | ||
|
||
If you’re interested in joining the Community Builders: | ||
1. Fill in this [form](https://namada.deform.cc/communitybuilders/) | ||
2. Follow [@namada](https://twitter.com/namada) on twitter | ||
3. Join the Namada [Discord Server](https://discord.gg/namada) | ||
4. Checkout the Namada [CB Handbook](https://namada.net/community/docs/community-builder-handbook) | ||
|
||
## Voting process | ||
For this RPGF round, the early PGF stewards and the Community Builders will use Coordinape. Your participation in the Community Builders program means that you have a voice in what is important and impactful to Namada. The results of this voting process will inform which Community Builders will receive an allocation for their efforts and the amount. Early PGF stewards will inform the Anoma Foundation about the results so they can be included in the genesis block proposal. | ||
|
||
### How voting works | ||
> Remember, to participate in voting, you must be an active Community Builder | ||
1. As part of the onboarding process, CBs are added to the Community Builder Circle (CB Circle) on Coordinape by Early PGF Stewards using the ETH address submitted in the form | ||
- Remember: this ETH address is **only** used to authenticate your access to Coordinape. | ||
2. As soon as you’re part of the CB Circle on Coordinape, you can start logging your contributions to your profile. During this period, no voting will take place. | ||
- Before logging a contribution, see the [guidelines](https://namada.net/community/docs/community-builder-handbook#contributing). | ||
- Inactivity during the contribution period: A re-evaluation of the CB membership can be conducted (you [can lose your CB membership](https://namada.net/community/docs/community-builder-handbook#losing-cb-membership) during this period). This happens, though - if you haven’t submitted any contributions before the voting period begins. | ||
3. Voting starts as soon as the 1-week Epoch begins. During this period: | ||
- Each CB member will receive a fixed amount of GIVE on Coordinape (aka points on the platform). This amount of GIVE is the same for every CB. | ||
- Note: if you haven’t submitted any work over the course of an Epoch, you’ll be pruned out of the CB circle and will not receive GIVE. | ||
- CBs will have 1 week to allocate their GIVE to other CB members based on their contributions. | ||
- In parallel, Early PGF stewards will also have 1 week allocate their GIVE to CB members. | ||
4. Voting weights: | ||
- CBs will have 40%, while Early PGF stewards will have 60% of total voting weight. | ||
- The amount of GIVE distributed across CBs and the Early PGF stewards will reflect these weights. | ||
![Voting Weights](/voting-weights.png "Voting Weights") | ||
5. End of Epoch and voting: | ||
- At the end of the epoch, the results will be published. | ||
- These results will determine the recipients and amounts. | ||
- The early PGF stewards will inform the Anoma Foundation on the final proposed recipients and respective allocations to be included in the genesis block proposal. | ||
|
||
## Timelines | ||
|
||
If you’d like to participate in the RPGF round, here are the dates to keep in mind: | ||
1. Those who want to be Community Builders can [sign up now](https://namada.net/community/docs/community-builder-handbook) | ||
2. **Starting Thursday, Oct 19th 2023** contributions are open | ||
3. The contribution period will begin, totaling approximately 5 weeks through **Sunday, Nov 19th 2023.** | ||
- Accepted submissions can go back to the beginning of the community, if you have been a participant member of the community | ||
- Accepted submissions will also include all submissions over this **5 week period** leading up to the first voting period | ||
4. Once this period ends, a Coordinape voting epoch will begin on **Sunday, Nov 26th** and will proceed for 1 week, through **Monday, Dec 5th 2023 at 23:59 UTC** | ||
- Last minute community Contributions can be submitted until **Wednesday Nov 28th 2023 at 23:59 UTC**, all submissions after this date can be considered for future potential RPGF rounds, but with no guarantee on the amount allocated from the pool. *(These submissions will have a different date appended)* | ||
5. Recap and results to be published shortly after. The results of this vote will be used to inform the allocation of NAM to early Community Builder participants and inform the Anoma Foundation about the final recipients and respective allocations to be included in the genesis block proposal. | ||
6. Recipients of this RPGF round should wait for instructions on how to generate keys before genesis. |
Oops, something went wrong.