Future of GoCD
5 views
Skip to first unread message
Sambit Dash
Apr 4, 2026, 2:02:20 PM (yesterday) Apr 4
to GoCD Users
Hello Chad, Arvind
Apart from the last update GoCD Project Status there hasnt been any direct updates. Where is the project heading and what are you thoughts on its future.
regards,
Sambit
Sriram Narayanan
1:28 AM (13 hours ago) 1:28 AM
to go...@googlegroups.com
On Sun, Apr 5, 2026 at 2:02 AM Sambit Dash <sambitd...@gmail.com> wrote:
Hello Chad, ArvindApart from the last update GoCD Project Status there hasnt been any direct updates. Where is the project heading and what are you thoughts on its future.
Chad is the primary and only active maintainer at the moment.
Some of us have been working on the side to set up an organisation to provide full time commercial support but have made only partial progress on the matter. We have concluded that customers will need more than just support for solely GoCD itself, but we welcome any enquiries from those who are satisfied with only commercial support for GoCD alone.
regards,Sambit--
You received this message because you are subscribed to the Google Groups "GoCD Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/go-cd/425de342-bfcf-4967-8e7b-233dafa53c21n%40googlegroups.com.
Chad Wilson
4:17 AM (10 hours ago) 4:17 AM
to go...@googlegroups.com
Hiya Sambit - is there a specific context to your question, or something you'd like to know - or are worried about?
I should probably do better writing about what I've been doing/not doing, but the release notes are probably the best summary of what's been happening since then, so you can see the type of progress/work that has been done with the project in its current state.
In addition to what Ram has mentioned it's worth noting that neither Aravind nor I are employees of Thoughtworks any longer.
That doesn't majorly change the status of things, as we both retain maintainer access to the project and we made a number of behind-the-scenes changes to decouple the core "open source maintainer" pieces further from Thoughtworks infrastructure. In some areas it actually makes me a bit more flexible than earlier, since I am no longer constrained by employment obligations to Thoughtworks. (e.g earlier I could not accept paid consulting/development/retainer work related to GoCD - whereas now I theoretically can) Thoughtworks technically still own the copyright/IP around GoCD, and I thus maintain relationships with generous Thoughtworkers who can help me with some of the GoCD infrastructure which Thoughtworks kindly-but-informally, continues to sponsor.
Aravind is currently in more of a "back-up" type of function in case something were to happen to me or my access; and performs a type of informal "advisor" to me given his long history with the project.
The status of the project isn't fundamentally different to its status in 2023 - I do bits and pieces as they interest me (and to keep things secure), but the project lacks funding/support, diversity of maintainers/contributors - and honestly not much of a feedback loop (positive or negative!) from users to keep my enthusiasm up. It still needs some dedicated work in some technical areas to improve maintainability around EOL components/technologies (Spring, Hibernate primarily) but I believe otherwise remains secure and technically robust to use.
-Chad
I should probably do better writing about what I've been doing/not doing, but the release notes are probably the best summary of what's been happening since then, so you can see the type of progress/work that has been done with the project in its current state.
In addition to what Ram has mentioned it's worth noting that neither Aravind nor I are employees of Thoughtworks any longer.
That doesn't majorly change the status of things, as we both retain maintainer access to the project and we made a number of behind-the-scenes changes to decouple the core "open source maintainer" pieces further from Thoughtworks infrastructure. In some areas it actually makes me a bit more flexible than earlier, since I am no longer constrained by employment obligations to Thoughtworks. (e.g earlier I could not accept paid consulting/development/retainer work related to GoCD - whereas now I theoretically can) Thoughtworks technically still own the copyright/IP around GoCD, and I thus maintain relationships with generous Thoughtworkers who can help me with some of the GoCD infrastructure which Thoughtworks kindly-but-informally, continues to sponsor.
Aravind is currently in more of a "back-up" type of function in case something were to happen to me or my access; and performs a type of informal "advisor" to me given his long history with the project.
The status of the project isn't fundamentally different to its status in 2023 - I do bits and pieces as they interest me (and to keep things secure), but the project lacks funding/support, diversity of maintainers/contributors - and honestly not much of a feedback loop (positive or negative!) from users to keep my enthusiasm up. It still needs some dedicated work in some technical areas to improve maintainability around EOL components/technologies (Spring, Hibernate primarily) but I believe otherwise remains secure and technically robust to use.
-Chad
Reply all
Reply to author
Forward
0 new messages