Problem/Motivation
Creating and communicating a roadmap for the community for several reasons:
Transparency: Open source projects thrive on the shared efforts of their community. By communicating a roadmap, you provide a higher level of visibility into the project's future, which encourages trust and engagement.
Collaboration: When the community is aware of the roadmap, it can identify areas where it can contribute most effectively, leading to higher quality contributions. It encourages community members to take ownership of features or fixes they feel passionate about or competent in.
Prioritization: A roadmap allows the project maintainers to outline their main objectives and timelines. This helps to give the direction and sets the expectations right, ensuring that everyone is focused on achieving the same goals.
Feedback and Innovation: Sharing the roadmap openly allows users and contributors to provide early feedback. This can facilitate innovation, as different perspectives can challenge existing assumptions and introduce new ideas.
Sustainability: A well-communicated roadmap can help ensure the project's continuity. When potential contributors and users can see where the project is headed, they're more likely to get involved and help maintain the project, thus ensuring its long-term viability.
User Adoption: Lastly, a visible roadmap helps potential users see what they can expect from the project in the future. This can be particularly important for businesses or institutions that might want to adopt DG, as they often need a thorough understanding of a project's direction before committing to use it.
Proposed resolution
Create a page for "Plans and roadmap" on drupalgutenberg.org
Update the community through Slack, the project page on d.o and potential other channels.
Remaining tasks