Ironically, the first thing we want to say is that we’re not fans of forking projects. We have been the core developers of the Activiti Java Business Process Management (BPM) project right from its beginnings to its current state, so this has not been an easy or quick decision. We acknowledge Alfresco’s stewardship of the Activiti.org project, and as employees we enjoyed considerable freedom to develop the project over several years. However, things didn’t work out as we expected or hoped. We came to the conclusion the only way to continue evolving our ideas was to fork.
There are many examples of forks in open source, as Swapnil Bhartiya has recently described in May the Fork Be with You, including mention of one of the live topics of discussion currently within the Docker community. With Docker, the main concern appears to be the mixing of competitive and commercial elements into a core used by different commercial organizations, with people voicing pros (e.g. [Rob Hirschfeld] (https://robhirschfeld.com/2016/08/31/why-fork-docker-complexity-wack-a-mole-and-commercial-open-source/) and cons (e.g. Doug Davis). Let’s be clear about our intentions – the Flowable fork will remain liberal and open, and will be the focus of our future efforts in BPM, hosted on GitHub.
In the past, Matt Assay pointed out that forking is often good for innovation, which very much underpins our hopes. By keeping to our business process-oriented roots, we can innovate in the core of the BPM engine far more readily. Not all forks are successful, as Matthew Hughes highlights in Forking Good Great Ugly, but another recent fork, ownCloud / Nextcloud, where the development team became unhappy with the commercial management, seems to be succeeding NextCloud release OwnCloud fork ahead of schedule. In a similar vein, we have just pushed our first release of the fork for the V5 engine, including a powerful new feature, transient variables. We will be releasing an update to V6 soon as well.
Obviously, our biggest worry is the confusion to developers that a fork can introduce. Only time will tell if that can be overcome. If you’re unsure of jumping in, take a look at the authors in the code and the people working on the Flowable project. We are the people that know it best, and who have been driving the community, contributions and evolution over the years.
We’ve had a whole bunch of people contact us about their concerns with how things had been going (or more accurately, not going) and to show support in what we’re doing with this fork. Please take a look and get involved. Now’s the time to make your business processes Flowable.
In this post, I’m going to show you how to run Microsoft’s RPA product from Flowable. The full and complete way of doing this is by using Microsoft Power Automate Cloud to remotely drive Microsoft …Read more
The 6.7.0 release is a long awaited new version of the Flowable Engines. This release has taken longer than it was initially planned and we will try to meet timelines better for the next release. …Read more
When anyone uses the word “open” in the same sentence as “Flowable”, people usually assume they’re talking about open source. Often, that will be true, but there are other aspects of openness that are also …Read more