Introducing the new Developer ID to Marketplace

Completely unrelated from this topic, but this has some history.

A couple of years ago, when CDAC was launched, Atlassian centralised all marketplace comms to this site. Which… was a bit problematic, because this is a forum. For instance, CDAC was also used for reporting cloud incidents, change logs, etc. You can see with the current Platform 7 release what the shortcomings are of using CDAC as a source of documentation.

So Atlassian went on a journey to decentralise comms into multiple channels, including Partner portal, change logs, CDAC, ECOHELP, etc. When that project was halfway, Atlassian decided that it needed to follow industry best practices of laying off staff (because investors) and randomly selected 5% that needed to go. Obviously, this was not so random: it almost completely involved all Marketplace programs staff, incl. marketplace marketing. The ones that were left decided to leave on their own terms.

The whole comms strategy got stuck in limbo, with no driver left in the seat. So now teams can just decided by themselves where to post what and there is nobody left within Atlassian to check if vital information isn’t missed by the Atlassian partners. In the context of “no news is good news”, if you don’t get any pushback because partners never read your announcement, you can just continue as planned!

At some point DevRel / DX teams were still doing some of the heavy lifting, but now the team has been put on tour to sell Forge I don’t think many have time to keep track of all the different comms channels (just like we don’t).

Anyway, so much for some much needed Atlassian history as to why comms are a mess and partners stay uninformed about many changes, despite Atlassian best effort to provide clear and timely communication!

10 Likes