0 Members and 1 Guest are viewing this topic.
I'd just go with a yes/no dialog in the next wallet version on first launch."Would you like default votes set to support the developer team?"Or something to that effect. Doing it silently could be bad PR.
Or a "slate list" after open the wallet for the first time Dialog : Which build in voting slate you like to use ?1\I don't want to choose any of these 2\core developers 3\Xeroc's4\xxxxxxxx's5\yyyyyy's
I support a dialog on initial load, giving the user the ability to see who are in the slate, and a link to a thread describing the roles of each dev.
I think eventually the client needs a 'Delegate Campaigns' tab which shows delegate bids right in the client, possibly also with 'Delegate Slate Campaigns'. We could have a semi-annoying reminder every once in a while, or the delegate campaigns tab glowing a different color until they vote.
As per Rune.. keeping the controversy outside the client might be best. Pointers on how to in the wiki and have the forum host detail of slates, with perhaps a sticky slate detail of the core devs by way of strong indicator.I think there is some advantage in making the core devs more apparent.. perhaps biographies, even if fictional can help their getting votes. Are the ~business cases put somewhere easy to navigate?.. Perhaps could add those to the wiki.There's a rather good exhibition on at the London V&A about political movements and identity Disobedient Objects, which had me wonder that part of the way community and identity is encouraged is by tokens that acknowledge roles. Perhaps the forum could acknowledge people's roles in some way, so devs are less anonymous among the crowd.
There's no need to censor this thread.
There's no need to censor this thread. It's obvious that BM just wants a discussion about this since a lot of the core devs are getting scared of losing their paycheck. QuoteThe Devs SHOULD get scared of losing their paycheck if they don't continue to do their job as everyone else in real life. Having the devs automatically get elected and paid will make many people very uneasy.. QuoteLosing a core dev is still a lot worse than putting default votes in the official client, but I don't think either needs to happen. We just need to vote these guys in.Of course we all need to make sure that all of these guys are always voted since they are doing a great job. But these guys need also to keep having a large BTS stake to vote for themselves. What happens if they all dump their shares and are still get voted?QuoteHow about instead of having default votes, our entire community makes sure to make a lot of noise here in general discussion over the next couple of weeks to get everyone to vote for our core devs. They'll all be voted in soon enough.Whenever one of the Devs is risking to get voted out, the people managing their delegate should make a lot of noise to the community so they get elected back.Don't kill the democracy of the voting system by applying these kind of rules. This proposal I feel is contradicting the core principles that BM is evangelizing all this time.
The Devs SHOULD get scared of losing their paycheck if they don't continue to do their job as everyone else in real life. Having the devs automatically get elected and paid will make many people very uneasy.. QuoteLosing a core dev is still a lot worse than putting default votes in the official client, but I don't think either needs to happen. We just need to vote these guys in.Of course we all need to make sure that all of these guys are always voted since they are doing a great job. But these guys need also to keep having a large BTS stake to vote for themselves. What happens if they all dump their shares and are still get voted?QuoteHow about instead of having default votes, our entire community makes sure to make a lot of noise here in general discussion over the next couple of weeks to get everyone to vote for our core devs. They'll all be voted in soon enough.Whenever one of the Devs is risking to get voted out, the people managing their delegate should make a lot of noise to the community so they get elected back.Don't kill the democracy of the voting system by applying these kind of rules. This proposal I feel is contradicting the core principles that BM is evangelizing all this time.
Losing a core dev is still a lot worse than putting default votes in the official client, but I don't think either needs to happen. We just need to vote these guys in.
How about instead of having default votes, our entire community makes sure to make a lot of noise here in general discussion over the next couple of weeks to get everyone to vote for our core devs. They'll all be voted in soon enough.
Many of the core developers are critical to the success of BTS and they are implicitly trusted by everyone who downloads the wallet. For this reason I would like to suggest that the next release of the BTS wallet set the "default" approval for the following core developers:Me, Toast, Nathan, Vikram, Valentine, James, Ben, Dan N., Eric F. Each of these guys is implicitly trusted and contributing directly to the github source. This would really help the core team to get and keep the votes necessary without having to worry much about their salary. Users could always "unvote" them. Thoughts?
Quote from: mf-tzo on January 03, 2015, 06:13:32 pmI can't believe that we even discuss this... I don't even want to mention why this is a bad PR idea as I will give bad actors and FUDers food for thought..I have another proposal as well... Let's make a delegate that is always voted and pay AGS shareholders every week. AGS shareholders were the ones who supported the project without expecting anything in return anyway..Please delete this thread before too many people see it..There's no need to censor this thread. It's obvious that BM just wants a discussion about this since a lot of the core devs are getting scared of losing their paycheck. Losing a core dev is still a lot worse than putting default votes in the official client, but I don't think either needs to happen. We just need to vote these guys in.How about instead of having default votes, our entire community makes sure to make a lot of noise here in general discussion over the next couple of weeks to get everyone to vote for our core devs. They'll all be voted in soon enough.
I can't believe that we even discuss this... I don't even want to mention why this is a bad PR idea as I will give bad actors and FUDers food for thought..I have another proposal as well... Let's make a delegate that is always voted and pay AGS shareholders every week. AGS shareholders were the ones who supported the project without expecting anything in return anyway..Please delete this thread before too many people see it..
Quote from: Troglodactyl on January 03, 2015, 05:47:44 pmI'd just go with a yes/no dialog in the next wallet version on first launch."Would you like default votes set to support the developer team?"Or something to that effect. Doing it silently could be bad PR.That sounds reasonable and would achieve the same goal.