Thanks for sharing your ideas, after many rejections and no feedback I feel the pain points.
I think the proposed improvements would be very valuable, however I would be picky in the technical implementation details and not let OpenGov close itself and be dependent on specific platforms and centralized solutions. We should make some parts direct changes to the on-chain protocol and the bits that don’t make sense to have in the runtime part of an off-chain, yet decentralized, new protocol.
Like I suggested in How to limit altering proposals after they are posted? - #18 by olanod I propose creating a decentralized “Governance API” that is easy to deploy by anyone and uses a decentralized storage backend under the hood, I suggest using Matrix as the backend as it can cover every proposed functionality(e.g. including notifications) and is widely used by many people in the ecosystem(for communications via Element).
To keep runtime changes minimal I would only suggest making the preparation period longer and allow editing the proposed preimage during that time, making it the official period to receive feedback and make adjustments.
The Governance API is in Virto’s roadmap so we would be happy to collaborate in the implementation including any runtime change needed. We use the API to give any DAO their own OpenGov but it would work just the same for the relay chain’s governance.