Hey!
I think maybe I wasn’t being clear enough with the way I put things. I’m not trying to say any of these things are good or bad - it’s neither a feature nor a bug. It’s a very valid opinion to say that the social cost is a good thing, and I can see many reasons why it is so. It’s just as important to understand the deficiencies of such a setup, because that may work against the larger goals.
It’s more that we need to understand how the system works in practice to see how we can adjust for different behaviors and outcomes, so that we can iterate towards a better system.
Are we doing well enough today to get to the following outcome:
Probably not, so we should figure out where to adjust.
Yes, very much so
I agree, there are many ways to get involved. But again, I’m not talking about whether one way is a “feature” or a “bug” - instead, are we (Polkadot) getting the results out of the system that we want today (status quo)? If the system is ok today, then no changes are needed. Alternatively, maybe we just need education or encouragement for people to contribute more. Perhaps we need to do a deeper dive into why people are or are not contributing more. Whatever path we go down, risk being tied to reward should still be the case.
I don’t mean the “needs of the ecosystem” as there is no way to get consensus on that at the present. I just mean factors such as the level of detail/specification required in proposals, the hourly rates, the commitment to open source, the focus on hourly-based actions vs impact.