Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WorxDAO Design #62

Open
n0izn0iz opened this issue Apr 3, 2024 · 1 comment
Open

WorxDAO Design #62

n0izn0iz opened this issue Apr 3, 2024 · 1 comment

Comments

@n0izn0iz
Copy link

n0izn0iz commented Apr 3, 2024

Hey, opening up an issue for collaborative design of worxdao

Here's the latest thoughts from Jae and Manfred

  • Jae:
    I feel like we should have another design session to figure out what that looks like, what worxdao should be. I know we were going in some direction with the worx token or some number but I think it probably makes more sense to recreate something that looks like the GitHub.. when you go to GitHub you can see the green squares, ok? So that works well for GitHub but arguably it make sense to create something that is specialised for our work. Not everything might be on GitHub, we might not even use GitHub.. but it would be nice to see over time what kind of contributions people have made. Imagine this tiles, imagine you can have some sense of how much work you did each day. I feel that instead of worx, we should put hours, just call it hours, you known, “How many hours did you work today” “How much man-hours was put into something”. That make a lot of sense, I don’t see why we need to create something called worx. And that way everyone can see “what weeks”, “what days”, “someone’s been working on what”. And it’s just a tool to assist in evaluating if someone’s contributing to the project or not in much the same way you can do the same by looking at the green tiles on GitHub. And I feel the primary objective or responsibility for worxDAO is to evaluate whether someone is working or not and if they are, then help pay them a salary so-to-speak. I doesn’t have to be salary but “something”. They should get reward for doing work based on some schedule and if they haven’t been doing work, they should.. maybe it also tracks vacation time, like within a year you can say “I’m out of office” so to speak. And then if you haven’t been doing any work, then there should be some comity within workdao that says “Ok this person is clearly not active anymore” and take some action for that person. So if they’re a top tier member that means “they become an inactive member” but it doesn’t mean they can’t vote, they can still vote or participate because they earned that tenure. But maybe it means something different for a lower-tier member, maybe they get booted, it really depends on the tier. That’s something for govdao to decide but it could receive messages from worxdao. So within worxdao there would be some tooling to help assess generally what someone is doing, so notion of some commity evaluating whether someone is still active or not and something like rewards distribution based on if someone is active or not and the tier they’re in. The input to how much rewards you get is not based on worx or hours, it’s based on “what tier are you in” and “are you active or not”. And maybe there’s some component within it that figures out ultimately how many GNOT you get. So some component that has to do with an internal treasury and some algorithm to disperse based on what I just said. All that said I think there needs to be a new design spec for what worxdao is, we need to redo it.

    Source: https://youtu.be/3kjEl91vaoA?si=rmFD6uQ-Io-dwL4p&t=2811

  • Manfred:
    ^worx:

    • symbol for quantifying contributions
    • broadens contribution definition beyond traditional work
    • signifies appreciation for all forms of contribution, fostering engagement, creativity and collaboration
    • plural form for diversity and unquantifiable nature of contributions
    • not tradable (not $WORX), but holds value within the community
    • potential for annotations with tags with tags for automatic quantified expertises
    • empowers contributors, promotes a sense of ownership
    • one of the main metrics used in the Contributors DAO

    Source: https://gnolang.github.io/workshops/presentations/2023-06-06--buidl-asia--manfred/presentations.slide.html#3

You can see Teritori's team explorations report here

@moul
Copy link
Member

moul commented Apr 12, 2024

Thank you, Norman. We will soon organize a workshop to clarify and address various aspects of this project. Let's discuss your points there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants