As mentioned in this and that thread, and also on the Atlassian Partner Portal, the Atlassian Marketplace team will be taking steps to turn feedback into action with regard to content & communications.
This is primarily the result of feedback from Atlassian Marketplace Partners regarding the (ab)use of CDAC for announcements, discussions, documentation, release notes, cloud incidents, etc.
Looking at the proposed actions, I really applaud the team for looking into which medium / format is best suited for each different form of communications. Critical cloud incidents should indeed go into a (public) service desk. There should be a chronological overview of changes per product in a change log. Architectural changes should be documented in Confluence, which supports versions that allow vendors to see the latest up-to-date implementation details but also review how it changed over time without having to search for separate topics or go through lengthy threads in a discussion.
Obviously, CDAC could/should still be used for discussions (ngl, Iām not looking forward to having lengthy discussions in Confluence).
Butā¦ there is one thing that I find somewhat disturbing from the current plans, which is the fact that not only the content is being moved to separate (and more appropriated) sources, but also the communications.
In the current plans, announcements will move together with the content to the new place. For product changes, this means that announcements will be communicated through a newsletter, a blog post or just through the change log. This means that I will have to keep track of three different sources per product.
In addition, some content will move to the partner portal, which means that I will have to track notifications from Confluence to see which pages changed. Which does not always work if restrictions are used during draft editing to keep a page private and the page gets āpublishedā by removing these restrictions.
For Marketplace Partners, we are moving to a situation in which there are going to be N number of places to track for announcements (Partner Portal, change logs, DAC blogs, email newsletters).
It is currently already really hard for partners to keep on top of everything Atlassian Marketplace Partner related (and I know because Iām curating the #remiebot channel in the partner slack workspace which got me the Devotee badge on CDAC just because I check every day for new announcements).
So here goes my passionate plea: it would like to ask the Atlassian Marketplace team to consider separating content from announcement. Please do move all the content to the appropriate places, being either Partner Portal, DAC blog posts, change logs, whatever. But make sure to create a single place (whether this is CDAC or not I donāt care) in which all teams post their announcements.
I understand that this creates an extra burden on each of the Atlassian teams, but please do take into consideration that from a DX perspective it would really improve lives for Atlassian Partners. Otherwise, you will be placing the burden onto us to find relevant information often required for us to succeed with your platform.
PS: one argument to consider keeping CDAC as the single source for announcement is because a lot of partners have automated scanning of RSS feeds to make sure they keep up to date, as a result of Atlassian saying CDAC would be the single source of truth. Moving away from that would mean a lot of vendors needing to update their scripts to include all these different sources to get the same overview.