Hey appreciate your fast answer.
The discussion about the proposals will be in github the right place. i will try to open them there and inform you. So we can go further with it.
i think we need nothing fancy, maybe a description (see bellow) and some hacks will do it.
A good overview about all the proposals, bug, security issues. with an good priority mapping and ranking. which will fit in to a roadmap and future cycles of releases. Where we can also show which ones are under development (on which branch), which ones are already done and which ones are to expect in this cycle (or will be moved to next cycle [then we move it ;)])
I found this one Roadmap :: Concrete CMS - Org but it looks out of date (BTW also Town Hall, which is also sad:() and not in the navigation any more. Can we have it back as a documentation page?
something like this?
- Add your issue (proposal, bug) or Security Issues (check first if it is not already there, if so, give it an upvote)
- Discuss it on the issue, find contributors and get as much up votes as possible for it.
- The issues with the most upvotes go in the Roadmap and will be tracked on priority (top to bottom), release cycles and current state. This means it will be baked in. This will happen ones a month. The amount is done by the burn down rate on the roadmap.
I would love to see also the core stuff in this process? @andrew How do you see all of this?
What i don’t like, is that you need a github account for the voting. I think the Roadmap prioritizing thing needs to be done from the development community, this makes sense. But the voting should be done from all concrete-login community members. Also the guys who “just” use the CMS as an administrator. But the not more app thing is in my opinion more important then the new login thing on github for administrator
Further stuff on the topic
the Roadmap is coming from here: Announcing the GitHub public roadmap - The GitHub Blog
A other thing i found was this Customizing the roadmap layout - GitHub Docs
For my taste a bit too much, but maybe somebody has experience with it?
This would be a other voting system where we maybe could use the concrete-login for it: Issue Voting for github
But i like the idea not to involve to much other systems if not needed
I just realized, that in W3C GC we manly just discuss this stuff, and then the hacking is done by individuals out of the community. But the consensus (HAHA a hard topic at WebAssembly GC at the moment), but the consensus is done in the community with all at the meetings. Which in our case would be the upvotes and roadmap board.