Hi both @huw and @JoelKalmanowicz,
Thank you for your kind answers.
I am not sure Atlassian project managers have identified that there was a 6-months gap between announcing the deprecation of Server (so customers rush to the Cloud) and publishing Forge 6 months later. It means in the meantime, we have to develop temporary Connect apps.
Each time, we have to divert developers from serving customers to supporting:
- Data Center
- Various badges, security review, etc.
- Bug bounties
- Server deprecation / Connect
- Migration assistant
- Now Forge
- Apply to Atlassian Ventures
- And the Covid lockdown has a hit on our productivity.
We’re extenuated. We haven’t had time to program actual new big features for customers for the last year, and it is hard to recruit given Atlassian closed the Server revenue, and given the techs for Forge are non-sexy.
We’re bored of doing migration tasks and tired of the lockdowns. It would be nice, although as I understand the opposite is going to happen, if Atlassian could give vendors a bit of time to stabilize on Connect and have a very progressive migration path to Forge.
I’m afraid your marketing is instead going to push large, GDPR-sensitive customers to enforce a Forge-only policy as early as April, thereby threatening all vendors who didn’t grow quick enough to have enough developers to move to Forge in April.
Best regards,
Adrien Ragot
PS: Case in point, I had recruited to be 5 developers in total, but we had to cut back from 5 to 3 developers after Atlassian killed off the Server revenue stream, and we’re not sure of keeping the 3 people if our Cloud products don’t replace the Server revenue.