Open 0xferit opened 3 years ago
Hi Ferit,
Votes are reset on item-basis. If an item gets closed - the votes on that item will get released. This is running per cron job every 12 hrs to prevent (accidental) closing/re-opening issues.
Does that work for you? Or maybe you could explain how resetting would fit into your process? Also linking #40 - there might be some overlap..
Hi Wesley,
Thanks for the prompt answer. Yeah, I am aware that tokens are reclaimed when the issue gets closed but I was looking for a way to fresh-start. This is because we changed our voting scheme drastically and we want to start over. We can manually close all the issues, wait 12 hours and then re-open them but this is disturbing our issue tracking and it's unnecessary manual labor. So an automatic way would be very handy. If there is no such functionality, please consider this issue as a feature request.
Ah, got it.
There isn't currently such functionality. One of the challenges for resetting would be community approval/consent. That would maybe even require a community vote? Any thoughts?
In the meantime, I have reset a repo previously on request. but would need a bit more info to verify. Feel free to reach out on TG (same handle) or Discord (wslyvh#1059) to discuss further
Thanks, sent a message to you on Telegram.
Repo has been reset.
Leaving this issue open, to hear other thoughts and ideas on resetting repo's without 'gaming' the system.
In my opinion, whoever has write access to repo should be able to reset. Because you can game the system by changing vote scheme already (for example giving infinite vote rights to single account and zero to the rest by changing the contract setting).
Maintainer is the one who enables TokenLog, without his/her consent there would not be a TokenLog configuration. In addition to that, whoever has write access is the one who eventually processess the Github issues. What I mean by that is, being a maintainer of a given repo, one can always reject to implement a feature or reject a bug fix even if the issue has the most votes. So in conclusion, maintainers already have the power to game the system so preventing them to reset does not help. But they don't have any incentive to game the system, if they dislike they can simply remove it.
That makes perfect sense. So a Github integration, where someone can claim ownership of the repo would be sufficient in that case. Added it to the backlog
I want to reset all votes but I couldn't find how to. Is there such functionality?