@light I certainly wasn’t trying to imply that you all didn’t try hard enough – and indeed the ideas I mention are ones that require more hurdles as external parties are a bit out of owns control!
In thinking about ACT more, the initial proposal had to do with getting a signal from the entire development ecosystem: Flock, Nest, part-time recurring bounty hunters, open source contributors etc. The signal is more valuable if people from all parties buy into it. If the attitude is “go ahead and organize” but don’t count me in, then it does turn into an entirely different dynamic.
So yeah I understand the “no need to ask for permission” stance, but it wasn’t about permission in the first place and it wasn’t about trying to create this body for the purpose of it developing it’s own team, agenda, proposals – I do see the value for both types of bodies now though!
But my point is - “aragon builder community” signal is a bit different than a group of non-flock folks. And hence there does need to be some buy in from the rest of the community to actually try the originally proposed proposal (since an ethereum address is needed from everyone, if you actually want to measure the percentage of people participating). I’m not demanding this at all, but just clarifying the distinction and difference in signalling or voting between the two.
Perhaps it can be the non-flock that is the SRO on the burning situation though, to remove that administrative burden for others to participate that don’t want the bother with the meta governance, but are open minded to try the signalling mechanisms, where all it takes is one extra second to perform the vote on the additional application. I’m actually curious about the reasons why one would want to opt out of receiving the voting token - if all of the votes are just exact copies of any AGP or AIP