RE: Developing a community that develops code - organization first
In the generally perceived spirit of optimism, it actually seems possible to change things for the better (both socially and platform-related ;-))
I have always been a friend of the model of a council republic. All the things you name as representatives, but in changing formations. This brings me back to the fact that rigid teams, routines and habitual processes can make life and responsibility much easier. But they also harbour the danger of becoming blind to the business and getting stuck in a rut.
Incidentally, the council republic is based on a combination of elective functions and rotation. In other words, representatives elected by the wider community and a longlist, on the basis of which each individual is temporarily integrated.
If I am now correct in my perception that the Steemit team is no longer happy with its self-elected and then poorly established role here in the Steemit universe, the way is clear for real decentralisation and will certainly be supported accordingly...
I'm not familiar with the "council republic" concept. A quick scan of search results is interesting, because the concept seems a lot like "federalism" which has been used in the United States, since its founding, but the search results are dominated by examples from places like the USSR, China, and North Korea. I'll have to learn more about this.
The one thing that occurs to me is that we would have a very hard time implementing democratic voting here because it's so easy to create alternate accounts. I guess the councils would have to be small enough that it's possible for members to know one another personally.
0.00 SBD,
0.10 STEEM,
0.10 SP,
0.00 TRX