Create keybaseLabels.json

[sepu85]

json file for labeling members within the DAO DApp

[sepu85]

@bingen @lkngtn pls approve :-)

[lkngtn]

Approving this as I think its useful. Though we should revisit how we keep it up to date as we revisit the membership onboarding processes.

[bingen]

Yes, I'm approving not block anything (sorry for the late response) but I have some concerns:

• Do we have to mantain 2 lists now (README and this json file)? Actually, they are already out of sync.
• How has this been generated? It would be good to provide a script along with this PR.
• What's the order in this file? It's different than in README file, so it makes it harder to spot differences.

[sepu85]

Do we have to mantain 2 lists now (README and this json file)? Actually, they are already out of sync.

For the moment, I'd say yes!! although we still need to pullish/optimize/simplify the membershing onboarding process.

How has this been generated? It would be good to provide a script along with this PR.

it was generated through the new labeling funcionality of the last aragon version and exporting it from the AragonCoop DAO. what kind of script do you @bingen have in mind?

What's the order in this file? It's different than in README file, so it makes it harder to spot differences.

seems to be a random order actually (it was automatically generated from the DApp :-)

[bingen]

what kind of script do you @bingen have in mind?

I was thinking one that extracts json file from README, or the other way around, so we don't have to maintain both.

[lkngtn]

I was thinking one that extracts json file from README, or the other way around, so we don't have to maintain both.

This would definitely be nice.

It may also be nice to rethink how people actually apply for membership, the current process does not seem very intuitive, most people have had some issue with the commit itself or the keybase verification method, and some are not familiar with how to create a PR.