RE: Sports Talk Social: The Community's Future
You are viewing a single comment's thread:
What kind of community change is so urgent that it would require a more agile decision path?
Posted using SportsTalkSocial
You are viewing a single comment's thread:
What kind of community change is so urgent that it would require a more agile decision path?
Posted using SportsTalkSocial
For example, finding a dev who says he has some free time today and could make some needed changes to the front end.
I've had contact with cases like these outside Hive so I wouldn't be surprised if this happens someday.
Why does the community need to be consulted for front end changes? The front end is ran by Hive Engine so if you made changes to it you could send them upstream to HE and they could implement.
But doesn't the frontend also fit for being a community asset?
Or is it only the things that are onchain that belong to the community?
So I get confused about decentralization and that the community should have voting power on everything.
One reason would be the payment for that work.
Not really because it can't be held by the blockchain accounts. I am just willing to give it to someone else if the community thought they'd be a better custodian of it. There can be multiple frontends though. You could spin up simplysports.com and use SPORTS your own way. We used to run sportstalksocial.com for the outpost and sportstalk.social for the old style.
More or less. Unless there's a legal entity how would a blockchain own other assets?
Payments should be handled by token fund requests. If a token fund request receives support beyond the funding limit then it will payout on day one. Additionally payment proposals can be made on a future date to build support.
I was expecting since we are a decentralized community I was expecting everything related with the community even what is off chain was part of community assets, but I am wrong.
That was the point. If it is necessary to be agile, we are not able to do it.