feat: create `contributors/moul/profile.md` #5

moul · 2023-10-12T15:27:13Z

Here is an example of a manual LinkedIn profile for GNO. This section can be easily updated by individuals. We can include a CI/CD script that checks if the path is contributors/$pr-author/profile.md.

Next, the GitHub bot can generate contributors/$pr-author/gh-contributions.md.

Lastly, we can include a notable-contributions.md file. This time, the CI/CD script should verify if the individual giving "mad props" is a whitelisted leader and not praising themselves.

Once we have a combination of manual and automated files, we can create aggregates based on individuals (contributors/$name/README.md) or projects (root/README.md).

waymobetta · 2023-10-12T22:02:07Z

is a whitelisted leader

Some questions

Who manages this whitelist? (ie, TCR via Evaluation DAO)
What is the criteria for making it into this whitelist?
Can you be kicked out of this whitelist?
Do you imagine each repo having its own notable-contributions.md file or just one that lives within this repo?
^ Same question but now regarding the contributors/$pr-author/profile.md file.

@leohhhn @MichaelFrazzy

MichaelFrazzy

Great, thank you. @waymobetta covered a lot of my questions besides if you'd like the GitHub contributions md file to be the singular destination for automatic data collection. Or would you like to have a separate automated .md file per repo... originally all repos that qualify for GoR and post-launch any that relate to PoC? Either should work great with the scripts, it is more of a preference and organization decision.

moul · 2023-10-13T12:24:07Z

Who manages this whitelist? (ie, TCR via Evaluation DAO)

Jae and I will start by drafting the initial "projects' directory" and assigning official maintainers and facilitators for each project.

Later -> the worxDAO.

The objective is to determine the top-level organization based on the most trusted peers. Then, grant greater power and autonomy to subnodes, enabling them to create children or potentially fork under certain conditions.

What is the criteria for making it into this whitelist?

Being elected to the whitelist by the DAO means being recognized for one's experience and skills as a competent manager, reviewer, or expert in a specific project or area. This recognition is based on merit and results in inclusion in the whitelist.

Can you be kicked out of this whitelist?

Yes, you're elected. After that, you need to be regularly re-elected. If you perform a series of bad actions, you can be removed as a punishment.

Do you imagine each repo having its own notable-contributions.md file or just one that lives within this repo?
^ Same question but now regarding the contributors/$pr-author/profile.md file.

I envision each subDAO being on-chain with their own reports. For off-chain matters, I propose centralizing them exclusively in the "game-of-realms" (this) repository.

if you'd like the GitHub contributions md file to be the singular destination for automatic data collection. Or would you like to have a separate automated .md file per repo...

The "Game of Realms" is a repository that contains off-chain v0 of on-chain PoC and profiles. The repository serves as metadata for contributions made.

originally all repos that qualify for GoR and post-launch any that relate to PoC

Proof of Contribution (PoC) is not limited to repositories. Repositories are merely operational and organizational details. A contribution refers to anything that has been reviewed and approved by worxDAO as valuable for the ecosystem. It can come from another organization or event, and it doesn't have to be on GitHub at all.

waymobetta · 2023-10-13T15:40:16Z

Being elected to the whitelist by the DAO means being recognized for one's experience and skills as a competent manager, reviewer, or expert in a specific project or area. This recognition is based on merit and results in inclusion in the whitelist.

Great, this is helpful context. Having an off-chain example of what this discussion looks like would be equally helpful when we are ready for that.

@jaekwon

## Current Status ```console $ cd ./misc/list-gnophers $ ./main.sh ``` ```csv 1617467419,[email protected],./examples/gno.land/p/demo/flow/flow.gno 1651096034,[email protected],./examples/gno.land/p/demo/grc/grc721/igrc721.gno 1673524438,[email protected],./examples/gno.land/p/demo/grc/grc721/basic_nft.gno 1677669053,[email protected],./examples/gno.land/p/demo/grc/grc1155/basic_grc1155_token.gno 1678259597,[email protected],./examples/gno.land/r/demo/deep/very/deep/render.gno 1678709422,[email protected],./examples/gno.land/r/demo/groups/group.gno 1684921090,[email protected],./examples/gno.land/p/demo/merkle/merkle.gno 1687179019,[email protected],./examples/gno.land/r/x/nir1218_evaluation_proposal/category.gno 1687263124,[email protected],./examples/gno.land/p/demo/microblog/microblog.gno ``` ## Future Plans - Translate into GitHub usernames. - Share the gnopher list on `r/gh` (#1134). - Create a new `r/gnoland/gnophers` page with the following features: - Add a widget on `r/gnoland/home` displaying the "latest gnophers." - Create a helper function like `r/gnoland/gnophers.NumberByAddr("g1u7y667z64x2h7vc6fmpcprgey4ck233jaww9zq`) -> `(2 int)` to use this info on other meta profiles, such as the future "gnolinkedin" mixing facts and personal presentation (gnolang/game-of-realms#5). - Create a `r/gnoland/gnophers:username` route that returns a badge with the username, gnopher number, "gnopher since <date>," and a `gnoface` (#690). - Stop checking and order t-shirts for the first 100 official gnophers. ### Example Gnopher Badges ```markdown # @jaekwon proudly became the 1st gnopher on Oct 3, 2021. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#1 ``` ```markdown # @moul proudly became the 2nd gnopher on May 24, 2022. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#2 ``` cc @gnolang/devrels Signed-off-by: moul <[email protected]>

```console $ cd ./misc/list-gnophers $ ./main.sh ``` ```csv 1617467419,[email protected],./examples/gno.land/p/demo/flow/flow.gno 1651096034,[email protected],./examples/gno.land/p/demo/grc/grc721/igrc721.gno 1673524438,[email protected],./examples/gno.land/p/demo/grc/grc721/basic_nft.gno 1677669053,[email protected],./examples/gno.land/p/demo/grc/grc1155/basic_grc1155_token.gno 1678259597,[email protected],./examples/gno.land/r/demo/deep/very/deep/render.gno 1678709422,[email protected],./examples/gno.land/r/demo/groups/group.gno 1684921090,[email protected],./examples/gno.land/p/demo/merkle/merkle.gno 1687179019,[email protected],./examples/gno.land/r/x/nir1218_evaluation_proposal/category.gno 1687263124,[email protected],./examples/gno.land/p/demo/microblog/microblog.gno ``` - Translate into GitHub usernames. - Share the gnopher list on `r/gh` (gnolang#1134). - Create a new `r/gnoland/gnophers` page with the following features: - Add a widget on `r/gnoland/home` displaying the "latest gnophers." - Create a helper function like `r/gnoland/gnophers.NumberByAddr("g1u7y667z64x2h7vc6fmpcprgey4ck233jaww9zq`) -> `(2 int)` to use this info on other meta profiles, such as the future "gnolinkedin" mixing facts and personal presentation (gnolang/game-of-realms#5). - Create a `r/gnoland/gnophers:username` route that returns a badge with the username, gnopher number, "gnopher since <date>," and a `gnoface` (gnolang#690). - Stop checking and order t-shirts for the first 100 official gnophers. ```markdown ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#1 ``` ```markdown ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#2 ``` cc @gnolang/devrels Signed-off-by: moul <[email protected]> SetTokenURI wip

@jaekwon

## Current Status ```console $ cd ./misc/list-gnophers $ ./main.sh ``` ```csv 1617467419,[email protected],./examples/gno.land/p/demo/flow/flow.gno 1651096034,[email protected],./examples/gno.land/p/demo/grc/grc721/igrc721.gno 1673524438,[email protected],./examples/gno.land/p/demo/grc/grc721/basic_nft.gno 1677669053,[email protected],./examples/gno.land/p/demo/grc/grc1155/basic_grc1155_token.gno 1678259597,[email protected],./examples/gno.land/r/demo/deep/very/deep/render.gno 1678709422,[email protected],./examples/gno.land/r/demo/groups/group.gno 1684921090,[email protected],./examples/gno.land/p/demo/merkle/merkle.gno 1687179019,[email protected],./examples/gno.land/r/x/nir1218_evaluation_proposal/category.gno 1687263124,[email protected],./examples/gno.land/p/demo/microblog/microblog.gno ``` ## Future Plans - Translate into GitHub usernames. - Share the gnopher list on `r/gh` (gnolang#1134). - Create a new `r/gnoland/gnophers` page with the following features: - Add a widget on `r/gnoland/home` displaying the "latest gnophers." - Create a helper function like `r/gnoland/gnophers.NumberByAddr("g1u7y667z64x2h7vc6fmpcprgey4ck233jaww9zq`) -> `(2 int)` to use this info on other meta profiles, such as the future "gnolinkedin" mixing facts and personal presentation (gnolang/game-of-realms#5). - Create a `r/gnoland/gnophers:username` route that returns a badge with the username, gnopher number, "gnopher since <date>," and a `gnoface` (gnolang#690). - Stop checking and order t-shirts for the first 100 official gnophers. ### Example Gnopher Badges ```markdown # @jaekwon proudly became the 1st gnopher on Oct 3, 2021. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#1 ``` ```markdown # @moul proudly became the 2nd gnopher on May 24, 2022. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#2 ``` cc @gnolang/devrels Signed-off-by: moul <[email protected]>

@jaekwon

## Current Status ```console $ cd ./misc/list-gnophers $ ./main.sh ``` ```csv 1617467419,[email protected],./examples/gno.land/p/demo/flow/flow.gno 1651096034,[email protected],./examples/gno.land/p/demo/grc/grc721/igrc721.gno 1673524438,[email protected],./examples/gno.land/p/demo/grc/grc721/basic_nft.gno 1677669053,[email protected],./examples/gno.land/p/demo/grc/grc1155/basic_grc1155_token.gno 1678259597,[email protected],./examples/gno.land/r/demo/deep/very/deep/render.gno 1678709422,[email protected],./examples/gno.land/r/demo/groups/group.gno 1684921090,[email protected],./examples/gno.land/p/demo/merkle/merkle.gno 1687179019,[email protected],./examples/gno.land/r/x/nir1218_evaluation_proposal/category.gno 1687263124,[email protected],./examples/gno.land/p/demo/microblog/microblog.gno ``` ## Future Plans - Translate into GitHub usernames. - Share the gnopher list on `r/gh` (gnolang#1134). - Create a new `r/gnoland/gnophers` page with the following features: - Add a widget on `r/gnoland/home` displaying the "latest gnophers." - Create a helper function like `r/gnoland/gnophers.NumberByAddr("g1u7y667z64x2h7vc6fmpcprgey4ck233jaww9zq`) -> `(2 int)` to use this info on other meta profiles, such as the future "gnolinkedin" mixing facts and personal presentation (gnolang/game-of-realms#5). - Create a `r/gnoland/gnophers:username` route that returns a badge with the username, gnopher number, "gnopher since <date>," and a `gnoface` (gnolang#690). - Stop checking and order t-shirts for the first 100 official gnophers. ### Example Gnopher Badges ```markdown # @jaekwon proudly became the 1st gnopher on Oct 3, 2021. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#1 ``` ```markdown # @moul proudly became the 2nd gnopher on May 24, 2022. ||||||| ////////\ | | | ~ . | )| X X |. | | | C | | | | __/ | | | \~~~~~~~/ Gnopher#2 ``` cc @gnolang/devrels Signed-off-by: moul <[email protected]>

feat: create contributors/moul/README.md

d118ef3

moul requested review from waymobetta, leohhhn and MichaelFrazzy October 12, 2023 15:27

Update and rename README.md to profile.md

42529f8

moul changed the title ~~feat: create contributors/moul/README.md~~ feat: create contributors/moul/profile.md Oct 12, 2023

Update profile.md

96b00da

waymobetta approved these changes Oct 12, 2023

View reviewed changes

MichaelFrazzy approved these changes Oct 12, 2023

View reviewed changes

moul mentioned this pull request Oct 14, 2023

add notable contributions to moul #8

Merged

moul self-assigned this Oct 14, 2023

leohhhn approved these changes Oct 16, 2023

View reviewed changes

moul merged commit ff610ac into main Oct 18, 2023

moul deleted the moul-patch-1 branch October 18, 2023 11:04

This was referenced Oct 18, 2023

Create an Offchain Profile/Contributor/Contribution System #10

Open

chore: add misc/list-gnophers and .mailmap gnolang/gno#1265

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: create `contributors/moul/profile.md` #5

feat: create `contributors/moul/profile.md` #5

moul commented Oct 12, 2023 •

edited

Loading

waymobetta commented Oct 12, 2023

MichaelFrazzy left a comment

moul commented Oct 13, 2023 •

edited

Loading

waymobetta commented Oct 13, 2023

feat: create contributors/moul/profile.md #5

feat: create contributors/moul/profile.md #5

Conversation

moul commented Oct 12, 2023 • edited Loading

waymobetta commented Oct 12, 2023

MichaelFrazzy left a comment

Choose a reason for hiding this comment

moul commented Oct 13, 2023 • edited Loading

waymobetta commented Oct 13, 2023

feat: create `contributors/moul/profile.md` #5

feat: create `contributors/moul/profile.md` #5

moul commented Oct 12, 2023 •

edited

Loading

moul commented Oct 13, 2023 •

edited

Loading