@veskuh, thank you for the responses. As an example of a properly failed communication we have Changes needed to merge the project names to Sailfish OS which had completely irrelevant title and irrelevant introduction when you take into account the main message - closure of OBS and moving away from gitlab instance. The matter was discussed on the meeting between Jolla and community with the idea of continuing the discussion in this forum.
In particular, reasoning behind the decisions is not known to us. While that thread does deserve “that escalated quickly” sticker, I was personally expecting a reply today with the reasons behind OBS shutdown process. Namely, it is hard to propose the solution to the problem or finding a new working formula when the reasons are not known. Even if @maajussi was not able to reply today, I presume someone from the office could just step in and say “we are preparing the reply, please give us few hours/days/weeks”. Although, the reasons should be clear if such decision is made.
As a result of irrelevant title and introduction, we still don’t know whether OBS shutdown is decided. Thus, as a part of communication exercise with the community, please state in the title what is the message about and provide as much specific information as you can. An example of such communication is A New Policy for Mozilla Location Service where as much as they could, for legal reasons, we were given reasoning for a policy change. For a company that presents itself as open, Jolla should do better and not hide behind irrelevant titles something that is considered as not pleasing the community. We should be able to handle a bad news, just don’t try to hide it and let us work around the problem and find solutions to it.
So, in case of that “escalated quickly” announcement, I would propose:
Title: OBS is shutting down and Gitlab instance is moved
Text:
"
We have to announce, with the great sadness, that for several reasons we start the process of closing community OBS. This is due to
In addition, we have few other reasons that we cannot disclose, but would make it impossible for us to … . Before we close OBS, … We will work with the community of porters and developers to …
In addition, due to … , we are moving our repositories to "
Don’t know about others, but that type of straight communication is something that I would expect.
Anyway, I hope that the changes in communication will work out. As for OBS shutdown, I would like to get a conformation regarding it and please disclose why is it happening. In the relevant thread, though.