Apache PLC4X author "propaganda": will stop providing any free support | call on enterprise users to pay for open source

Recently, Christofer Dutz, the creator of Apache PLC4X, issued a statement on GitHub saying that due to the lack of any form of return, he will stop maintaining PLC4X and will also stop providing free community support to PLC4X enterprise users.

This is another software author disappointed by other companies using his open source project with no return, after the Faker.js author emptied the project repository code.

About Apache PLC4X

Apache PLC4X is a library for integrating PLCs (Programmable Logic Controllers). Interaction with the outside world (IT/Internet) becomes difficult due to the large number of incompatible communication protocols used by most industrial programmable logic controllers (PLCs). The PLC4X project emerged to provide a unified set of APIs through which drivers to communicate with most PLCs (through various PLC native communication protocols) can be implemented.

PLC4X Project: Open Source Software, Although Free, Needs Industry Support

Unlike pure software projects, PLC4X involved the Internet of Things and complex automation hardware, and Christofer had to buy some expensive hardware and software to test and maintain the PLC4X project, which put him in a dire financial situation. So Christofer registered an independent IT consulting firm called c-ware to help other companies design and implement PLC4X software related businesses.

However, the company did not do well. Christofer often receives emails like this:

"Thank you for this great PLC4X, it makes our lives a lot easier, I work for the biggest steel mill/aerospace/automaker in my country, and now the company has a problem like this, I Hope you can help."

"You're open source software, right? Can you help me?"

......

According to reports, the c-ware consulting firm is in good financial shape in 2020, with some institutional funding and the development and maintenance of PLC4X still on track. But in 2021, due to the global epidemic, the only sponsorship was withdrawn, and last year Christofer only accepted one paid speech. By 2022, Christofer is starting to tire of the days of not being able to make ends meet: "I don't want to waste my precious time on things that consume me and don't give me anything in return."

Therefore, he made a new development plan for PLC4X: no more buying hardware at his own expense to develop new drivers or integrated modules, no more porting PLC4X/drivers to new languages, and absolutely no longer offering companies free Consulting, training and support. He will only provide commercial technical support and training if required by the company.

In addition, Christofer has set up a crowdfunding program "when they will be available" for every new PLC4X feature frequently asked by company users, and will only start developing the corresponding feature once sufficient funds have been raised.

According to the crowdfunding announcement, "A fundamental principle of open source is not only to share code, but also to collaborate on things that cannot be achieved individually. ... We have listed multiple scenarios in the context of ApachePLC4X from c-ware, and users have already The schemes have been asked many times on the official site... If you or your company are interested in participating in this fascinating project, please contact the open source site's project mailing list at dev@plc4xapache org...".

It is reported that this kind of crowdfunding is Christofer's last attempt. If the corresponding funds are still not raised in 2022, he will no longer develop and maintain the Apache PLC4X project, and will no longer provide any form of support.

"If the industry doesn't support the techies behind open source, I can stop supporting them blindly and for free, at least for now."

As of January 15, the crowdfunding results for PLC4X are as follows:

Regarding the further development of this event, this site will also continue to pay attention. If you have any views on this event, please leave a message in the comment area.