-
Notifications
You must be signed in to change notification settings - Fork 4
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
What should be the rules of the "RepPointsServer"? #1
Comments
I'm happy with the rules how they are currently. |
Also I would like to try a voting system based on the rep. points |
And who wants to do a little frontend? The frontend should feature:
Nice to have would be:
|
i would actually try to do such a thing :-) I understand we have:
It's unclear to me how:
Beside that:It's not clear with how many points we start, we could just start with the same amont of points (e.g. 10 points), but imagine we would not have 5 but 100 participants right now - if what we try was more popular and already proven to work, then a hand full of people who worked already some time to make it happen would basically share with all those new participants who would, at least in the beginning, be "free riders" I think in the chat i tried to write down what has been done so far - which doesn't mean that there has to be points now equal to the work that has already been invested, but it would be nice to hear everyone's opinion on that to start with something that everyone would feel ok with. |
@ninabreznik @derhuerst @vysogot @Nasdneb
@ALL what do we do with that? |
Lets start with flat rate, each has 10 points. Now there is a wall where columns are named by each member and below their name a list of what they did and if they did something together the items should be linked. So anyone can go to a "What's done" wall and click +1 if they think the action was valuable. This way we transfer our points, so you give +1 but you get -1. If the item was done by many, the point divides itself evenly (into a float). Next case. When you have 0 points left you get the basic minimal income but you should be concerned that maybe you are a parricide. People will support you and lend a hand but to gain respect (or a point) you actually have to do something yourself. Now the thing is that there is a total income. From the total, before evaluation we subtract the costs like materials and rents. I wouldn't evaluate "the hours spend on brainstorming" cause with this layer of abstraction it will be difficult to manage it altogether. But! If somebody came up with a great idea during the brainstorm then people should point it out and then he can put on the wall under his name: "I came up with the idea of the algorithm/event/game/video ABC" and then people will rate it by giving him/her points. But no fluffy data, just concrete. So then once a week or a month or some given period of time that will based on the actual activity which now we cannot predict, the rates get gradually flattened. Someone with 20 points now has 18, the guy with 0 now has 1 or 2. The points get flattened straight after the money evaluation. (I just edited it). Aha, now I noticed it - respect points I mentioned = your reputation points. That's my first idea about it. |
yes, I like the idea to put points only on activites |
I would also say lets start with 10 points each. Then everyone makes his list of activities, and we can distribute our points. For the redistribution and creation of points, I suggest a higher rate for the beginning, so we can see how the game works. My suggestion:
|
What is the use of creating new points each week? |
The I think, all the rules (they are technical), should be explained, so that their meaning or the reasons behind become understandable. Below I'll try to give my understanding. Creation Rate [
|
Great :-) So we have one proposal already. I will also think about a proposal, but I already like the one from alexej. @Nasdneb - if I understand correct, you say:
3. Creation: Create 10 new points each week |
Rules
What I did not understand is:
|
I meant this case (let's imagine the UBI = 50 and we don't add new points): End of period 1:
Money gets transferred, paper work done End of period 2:
This way if nobody does any work and no points gets transferred then after maximum 10 redistribution periods every one is on flat 10, 10, 10, 10 again. That's a fresh open thought, let me know which parts of it you resonate with. |
@vysogot You introduce an explicit, fixed UBI. Maybe this is also something nice to think about. The idea in the first place was to have an implicit UBI, that comes from redistribution and creation of points. This way we could avoid voting all the time on how big the UBI should be. |
How about:
|
I like that. @serapath what do you think about it? |
I think we should use the official vocabulary of financial accounting, thus:
Would be great to come up with standard way of writing down what's happening, thus:
The activity over time happens in so called accounting records and a subset of those represents the cash flow which is what you were talking about:
I started https://github.com/serapath/economy a long time ago - and maybe another time we can start brainstorming about that kind of stuff more in detail. I would be interested, but for now i'd like to stay more focused on just a common vocabulary and everything we need to structure our "Reputation Points" :-) |
Very good. I'm bad with financial vocabulary and I appreciate this listing. By savings I meant that if there is any revenue 20% should go for the savings account from which we could make investments. Some hot cash if needed for a project or to sponsor something. By costs I meant things like rents or paper, pens, toys or boards, server etc. |
Otherwise...
Again...There needs to be a high motivation for people to actually earn the cake that we want to distribute. QuestionsFor me, before I maybe come up with my own suggestions (i'm not sure yet), i have a question. |
@vysogot |
I encourage obligatory voting in a community that one joins voluntarily. It is beneficial because people get used to be actively responsible. It also enforces the points rotation. When it comes to motivation I wouldn't count on money. Mission itself and the team goals should be the main drive behind the action. Money is an important outcome. Priorities must be clear otherwise we start to make a regular profit oriented company with personal financial pursuits. For the same reason I would keep a non-personal savings strategy. I also agree that people should not get kicked out easily. But if somebody brings damage and is not willing to change there should be a policy to let him go find his place somewhere else. |
I'm against enforcement, only rewards. So everyone who feels - as you say - mission itself and the team goals - leads and directs and others follow. For leading, the person is rewarded "Reputation Points". I don't believe it's possible to prevent some people starting to follow "personal financial pursuits", so the rules need to be able to cope with that. |
Ok, that's fine. |
We already started discussing in the wizard chat but we kind of need to come to an agreement about the "initial set of rules" with which we start the "RepPointsServer" or how the first implementation of the "RepPointsServer" should actually look like :-)
From then on, we can "vote" on commits to change the "RepPointsServer" and we deploy new versions.
The "RepPointsServer" will basically manage the stuff in the "data folder" :-)
The text was updated successfully, but these errors were encountered: