Closed mi-hol closed 1 year ago
FYI: A from my view good example for a communication plan is the part copied below
Maybe also consider actually maintaining the resources for the community, such as answering issues (see the last few in this repo), the (in the past) open deployments or fixing the CI and release links on the README.md of this repository …
It would've also been nice to communicate the background of the change behind going from hpi-schulcloud.de to dbildungscloud.de within the cloud as a global notification or something similar.
Thanks for your feedback. We understand, that engaging a community on Github is something we haven't really been focusing on as much as would have been necessary to actually grow a community. While I cannot really promise that we'll improve on that to the extent that would be necessary, we will make sure that the input we provide on our blog over at blog.hpi-schul-cloud.org will make it over to Github.
For our Q1/2022 roadmap, see this article: https://blog.hpi-schul-cloud.de/wir-wunschen-ein-frohes-neues-jahr-2022/
closing due to lack of interest
@bastihirsch The official project home page states:
From other successful open source projects a learning is "engage with your community by publishing roadmaps and project milestones". This has been voiced in a number of issues but has not resulted in a published roadmap yet.
In other projects a project or community manager owns the tasks to make that happen.
May I kindly asks for a comment on communication plans?