Thanks a lot for reaching out and apologies for any inconveniences caused on our part. We want to acknowledge that recent changes have complicated things for third-party developers so your feedback is definitely warranted and welcome!
It’s still important to us that third-party developers can be productive with Atlaskit. The team is actively looking for opportunities to improve in that regard whilst also balancing our internal requirements. It’s worth sharing the motivation behind why that decision was made. This is summarised in the README.md of the atlaskit-mk-2 repository:
In an effort to improve how we manage frontend code across Atlassian, we needed to first co-locate all our front end code in the same place. As a result, we decided to close the Atlaskit repo for a short period of time before re-opening it. You can still view the source
To shed some light on what’s going on behind the scenes, these changes are still rolling out internally. Tooling, logistics and security measures are being put in place to ensure the transition happens in a secure and non-disruptive way. One sacrifice we had to make however was the introduction of the public (one-way) mirror, intended to act as a “window” into our codebase for reference purposes. External contributions have been paused as a result.
That being said, we really want to stress that Atlassian are continuing to invest in the Design System, and we are still building new features and improvements as well as fixing issues. We plan to share that exciting work with our ecosystem and vendor partners in the future, just as we have in the past.
To elaborate on some of the specific points you raised:
packages are not updated frequently
While our public mirror is only updated on a weekly basis , our packages are still updated and published to NPM as per usual.
I’m curious though, would increasing the update cadence of the public mirror help you find the source of bugs and various behaviours? Are our docs missing important pieces of information that lead you to look through the source code?
packages have been marked internal-only, or have even disappeared from the public repository
Atlaskit has grown over time to include the source code of many Atlassian teams, admittedly the terminology for Atlaskit, Design System and ADG has become somewhat blurry. The distinction I would like to make here is that the Design System and ADG are intended for internal and external use, while other packages which previously were public and have seemingly disappeared were designed for internal use only. We’ve had to make the difficult decision to formalise this distinction and as a result feel we have potentially made some holes in our feature coverage more apparent. My question is what functionality are you now missing? Could you please share the packages that have disappeared which you still need access to?
community contributions (like creating issues) is no longer possible
It is definitely still possible to create issues and ask questions via our Jira Service Desk. Please let me know if you’re unable to access this.
While we love the idea of contributions, we’ve intentionally prioritised efforts that are more worthwhile first ahead of a revamped contribution process, based on the fact that we’ve had so few contributions in the past. There is a desire to enable this again, but currently the one-way mirror is the compromise we’ve made for the foreseeable future. I’ll be sure that any changes in this space are promptly communicated with the community.
We really appreciate your patience and understand your frustration while we work through these challenges. In the meantime we’ll be sure to keep our channels of communication open with the community, don’t hesitate to reach out! The best place for that is always our Jira Service Desk.
Daniel Del Core,
Design System Developer