Then perhaps Core should consider the significant number of no votes on both sides, use their discretion and void both submissions.
Well... I personally was very surprised and disappointed by the fact that new vote rules were introduced - IMO rules should not be changed on a per proposal basis unless there is a clear mechanism for this built into the system (and we don't have one). Otherwise what stops me from creating a proposal which "passes" if it was downvoted to say less then 10% (i.e. yes - no > -10%) like "Not so many people disliked it, so it's fine" rule? This doesn't work this way, rules are called rules for a reason. The one we have in place basically says "You need non-negligibly more people who support changes than people who oppose them for changes to be applied". Deviating from this to a "simple majority with enough votes" is not just about the way you count votes, it's a conceptual shift and I don't think that any proposal owner have such power, being from Core or not.it looks like the T&C logo will be adopted by Core....
That would be fair though regardless of the acceptance of the logo/style they proposed by the network imo. It was not a freelance competition for a prize afaik, they had some work done and they should be paid....and T&C will get paid...
Why an unvoted status quo must be preserved? Who decided that?If not - status quo _must_ be preserved.
<governance proposal>
A new governance decision which is put into a vote and gets more "yes" than "no", should be promoted against the status quo that has not been voted (or denies to be voted).
Yes/no/abstain
</governance proposal>
That would be fair though regardless of the acceptance of the logo/style they proposed by the network imo. It was not a freelance competition for a prize afaik, they had some work done and they should be paid.
Well... I personally was very surprised and disappointed by the fact that new vote rules were introduced - IMO rules should not be changed on a per proposal basis unless there is a clear mechanism for this built into the system (and we don't have one). Otherwise what stops me from creating a proposal which "passes" if it was downvoted to say less then 10% (i.e. yes - no > -10%) like "Not so many people disliked it, so it's fine" rule? This doesn't work this way, rules are called rules for a reason. The one we have in place basically says "You need non-negligibly more people who support changes than people who oppose them for changes to be applied". Deviating from this to a "simple majority with enough votes" is not just about the way you count votes, it's a conceptual shift and I don't think that any proposal owner have such power, being from Core or not.
This being said, with new rules (manually) defined within these 2 proposals I see them only as a poll, as a primaries in a NewLogo party between two candidates, so to say, which has no real power over the network. If we are going to "adopt" the new logo based on these results, to me, this will be an abuse of the governance system, so don't expect me to merge anything like that into Dash Core wallet. My understanding is that the winner of the "primaries" (T&C) should now apply final tweaks and finish all formal task etc. and then they should present full final pack (together with someone from Core?) in a new proposal. This final proposal _must_ pass with 10% majority vote for changes to be applied. If not - status quo _must_ be preserved.
That would be fair though regardless of the acceptance of the logo/style they proposed by the network imo. It was not a freelance competition for a prize afaik, they had some work done and they should be paid.