Post #31394

Signature verified

The signature from the blockchain entry has been verified against an identity on this server.

The entry content as it exists in the database. This should be verified against the blockchain entry.
Batched Amendment - Strategy and Resource Director Proposal
[QUOTE="Matt Osborne, post: 31390, member: 9"]
Under the council framework, would we have 3 different elections (tech, marketing, Governance) and then just hope the people that got elected could somehow form a solid working relationship? Or, are you thinking that the three-man council would run as a team? Meaning, we'd have something like four councils of three people each running for election. People would then vote for their favorite "council."

I think both are feasible. Under the first, running multiple elections simultaneously (separate subforums) probably sounds harder than it really is. Yes I'd expect them to form solid working relations. Again, they'd have separate responsibilities in which they really wouldn't get in each other's way. There'll be some overlap, sure.

To me, a council is a convention of individuals that make for a fair representation of a certain cause. A permanent meeting. Separately, each member can be a "Director" in whatever it is they are charged with doing. An example is Niels post above. But they talk to each other. Listen to each other. They point down the road and say: let's meet each other there. Under this proposal, there will be some fuzziness in how certain votes are cast, but that was always something you and I'd accept.

Under the second method you listed, I'm not immediately against it, and it guarantees a more streamlined team from the start, but there are many combinations to choose from and if just one person isn't desirable, the other two won't make it either. If we happen to agree on a council, we can let ANOs choose if they want this type of election process instead.

[QUOTE="Matt Osborne, post: 31390, member: 9"]
But, I am against tying our hands together by codifying this into Governance.

I don't think that's needed either. Typically, I think we tend to codify too many details as it is. Which is important in some areas, not in others.

What we'll need some agreement on in the future is how motions/votes are interpreted. For instance, the objectives vote just passed. Does it need inclusion in a governance doc? Not really. But can a Director/Council just straight up ignore it when they present their own roadmap? Well I wouldn't recommend it.

It's fine to have multiple roadmaps/objectives. That's what most decentralized projects do. Look at Tezos. Their foundation might have an internal roadmap. Arthur Breitman once posted what he calls [B]a [/B]roadmap or his personal roadmap. Then there might be a community roadmap to inspire community action.

[QUOTE="Matt Osborne, post: 31390, member: 9"]
So you believe that if these 10,000 companies had employed a council structure, and council members are elected by the employees and product users, that these companies would be just as successful?

If their final decision-making was also split into political parties, then yes.
This is the raw content, without BBCode parsing.