@danielwester definitely interesting to hear other perspectives, thanks! But also curious to hear more about this:
If I look at the #remiebot channel in our Marketplace Partner Slack workspace, the amount of announcements is really limited. If this aggregated space is only about announcements, and not, like CDAC a mesh of everything, everywhere, all at once, do you still reckon you need automated filtering? To me, it seems like the noise would be far limited compared to having to find the announcements in multiple channels in between other types of communications.
Quality and the structure of announcements is all over the place
I guess that will always be the case, right? Regardless of channels. Comms are distributed over a lot of different teams and there is no single team / person responsible for them. That is why I mentioned having a separate FTE solely responsible for the aggregation. That might also bring about a more unified messaging.
Discussions on announcements arenāt necessarily about the announcements which causes the announcements to become zombie announcements
Agreed, and I donāt think discussions on announcements should happen on the (aggregated) announcement space. I liked the suggestion by @tpettersen to add the ādiscuss on CDACā button.
Yes - because we have different personas both within the ecosystem (you and me may not need it because we can easily classify and understand what to ignore) but depending on a userās experience, what theyāre looking for to do their job- having Marketplace licensing rules change announcements next to Connect read scope changes is noisy.
I guess my assumption is that it will be harder for many Partners to find and filter the relevant resources if they are scattered over multiple channels than to learn how to ignore irrelevant announcements, but obviously milage may vary based on experience
Thanks for chiming in mate! Appreciate the additional perspective
want the extra noise ofā¦Bitbucket platform changes
Donāt break my heart Daniel. Iām still waiting for Customizer v2.
Too much filtering required
What if we had something like a dynamically generated RSS feed with:
a giant set of topics with slide toggles that let you opt in or out
a āRemieā toggle that turns them all on (and then you can opt out individually)
a āDanielā toggle that lets you turn them all off (and then you can opt in individually)
Would something like that work for you?
Quality and the structure of announcements is all over the place
This is certainly a problem, but I think we need to solve this in whatever form the announcements take. Even a changelog for just Jira Cloud potentially has a very large number of teams contributing to it. Part of the goal with comms is to standardise the process (with guidance and potentially checkpoints for enforcement) so that the quality and structure is consistent.
Discussions on announcements arenāt necessarily about the announcements which causes the announcements to become zombie announcements (An example of this would be if I was posting about changelings on a thread about scope changes)
I might be misinterpreting this, but wouldnāt the changelog mean youād have a way to just subscribe to announcements without the threat zombie forum threads?
It would be neat if the changelogs was backed by some type of database
ā Iām shocked, have we not spoken publicly about how changelogs are implemented yet? Iāll give you three guesses what itās built on.
The issue is that as soon as there is an announcement discussion - thereās a chance that there is new information exposed in the discussion that may not make it back to the announcement. Even if the chance of this is really low - it means that we then have to have track every discussion around the announcement).
Donāt break my heart Daniel. Iām still waiting for Customizer v2.
ā Iām shocked, have we not spoken publicly about how changelogs are implemented yet? Iāll give you three guesses what itās built on.