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

Reputation Point Rules + App Features #6

Closed
serapath opened this issue Nov 11, 2015 · 2 comments
Closed

Reputation Point Rules + App Features #6

serapath opened this issue Nov 11, 2015 · 2 comments

Comments

@serapath
Copy link
Member

Summary from #1

Work in Progress - please comment

Reputation Points Journal [RPJ]

https://github.com/wizardamigosinstitute/RepPointsServer/blob/master/data/dis_snapshot.json

e.g. Nina and Myself started the wizard school in April/May this year, thought kids, created website + texts + logos, went around with lots of flyers and invested some energy into social media (twitter/facebook/blog/....) and even paid for domains, flyers, logo design on fiver.de. Then Yannis helped with a little re-design of the website and was brainstorming with us. With Alexej we know were co-organizing the CodeMotion Event and we built some marketing materials and concepts for activities we could do with kids + we brainstormed about how we could do the shares or co-ownership. Alexej now created a repository for the server (see above)

Reputation Point Rules [RP]

The RP work a bit like shares in a company.
https://github.com/wizardamigosinstitute/RepPointsServer/blob/master/data/rules.json

Point Creation Rate [CR]

We need a way to create new shares and a CR is one way of creating new shares. A CR is voted on by all users and determined choosing the median. It "waters down" the value of all points currently held by users, but allows for a "higher resolution" (more fine grained control) when transfering points to others. The change in ownership is calculated by dividing ones own points through the total amount of points which currently exist.

Point Redistribution Rate [RR]

Everyone respecting RP's of others is a service everyone offers and should be paid. A Point Redistribution Rate is setting the service price and is voted on by all users and determined choosing the median. The change in ownership is directly visible through the points people currently hold.

@ninabreznik
Copy link
Member

Great job, went through everything and really sorry I didn't manage to join in before, but I still have my dad here and we're still fixing our flat (which was completely empty when we came).

Ok, to the point now.

Things that are blurry in my head and can't be put into anything concrete yet:

  • I want to make pros/cons for options
    We each earn her/his own money with our workshops for kids and put
    a) all the money on the pile and then redistribute it (we work as a team and not only "earners" matter)
    b) put % of our earnings on the pile and redistribute that (each is accountable for his earnings, but we put (i.e. 50%) into the greed and then redistribute that). Probably this is the better option but just didn't go through all ifs of both options yet...

Creation rate

  • I see that if we just create 10 new points for each member each month we are actually rewarding seniority (older members are worth more than newer).
  • Problem I see here: what if new member invests all his time and old member is just here on the side for the long time, but doesn't really contribute.
  • Suggestion: maybe (i.e.) 100 points could be created each month and they would be divided by the Respect Points (if x has 1200 RP and y 600 RP, then 100 new points: 2/3 for x and 1/3 for y). In this case we would reward the ones that contribute most and not the ones that are there longest.

Redistribution

  • I like the idea that we just reward the projects we support.
  • Suggestion: We need to have a common strategy/agreement what we want to reward. Otherwise it can easily happen that we just give back points to someone who gave them to us or we just randomly reward some tasks that sound nice to us (specially if tasks are more technical: i.e. someone is working on accounting things or some server stuff or some marketing strategy - because we don't all understand everything) and then the whole "game" loses its purpose.
  • UBI: When I think of it, I imagine, there should be a minimum income for every member. If we say each should get at least 300 each month, then we each get equal shares until we reach this amount and then afterwards we divide based on RespectPoints. Example: it is 5 of us and we got in 1000€. We divide this on equal 200€ incomes. Second example - we got in 2000. Each gets 300 (300x5 = 1500; 2000-1500 = 500) and 500 we split based on ReputationPoints (those who are higher on the ladder get more).
  • Ladder
    We give each other each week points for tasks we do for Wizard Amigos Institute. As said before we need some common strategy to see where we are trying to get with the project ( I can at least say for marketing that if we just communicate a bit here, a bit there, result is way weaker than if we make a strategy and do stuff synchronised and in the right time and connected with other communication activities).
    Maybe we could also give points when tasks are offered (in advance) so each can see and explain why she/he thinks this is important. Then if someone sees there is no interest, she/he can rethink if this is really a priority (synched with the strategy) and is not angry/sad after she/he invested lots of her/his time into it. And after the task we could then confirm the points and could have a possibility to give +- 30% of points we gave in advance (if task was poorly done or if it didn't bring us results we were hoping for, we give less, otherwise same or more).

Ok, I will update this later, but just to put first thoughts out finally :)

@serapath
Copy link
Member Author

Added to SPECIFICATION/README.md in upcoming pull request -> please discuss it there.

UPDATE:
The latest updates are to be found here: #9

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