In terms of usage

[123]

Rapid SCADA is an open-source project and can be used for commercial purposes, right?

[manjey73]

That’s right, you can create your own product by agreement with the developer, as well as create paid functionality in the form of modules, plug-ins and drivers.

[Mikhail]

Hi,
Definitely.
More info is here

[123]

So, does that mean I can modify everything, including trademarks and product names?

[Mikhail]

In short, according to Apache License 2.0 you can create a derived product with a new name, but you have to explicitly provide information about the original product.

[123]

On the web interface, clicking the Main Menu reveals options for Reports, Plugins, and About. According to the Apache License 2.0, am I allowed to hide the Plugins and About sections?

[123]

In short, according to Apache License 2.0 you can create a derived product with a new name, but you have to explicitly provide information about the original product.

Hello, please respond to my following questions separately?

1.Based on your response, am I allowed to change the product name and the product name?

2.Regarding providing information about the original product, can I credit the product’s source in the “About” section of the Main Menu? Does this count as providing information about the original product? If not, please provide a concrete example.

[Mikhail]

> 1.Based on your response, am I allowed to change the product name and the product name?
It is not allowed to change the name of the existing product Rapid SCADA. You are allowed to create a new product based on Rapid SCADA with a new name.

> 2.Regarding providing information about the original product, can I credit the product’s source in the “About” section of the Main Menu? Does this count as providing information about the original product? If not, please provide a concrete example.
It should be enough to provide a reference to the original Rapid SCADA in the About page.

Ask, I’ll be glad to clarify any non-obvious points.

• This reply was modified 1 month, 2 weeks ago by Mikhail.

[Mikhail]

If you are planning to make your derived project open source, Apache License 2.0 have some requirements to the source code. I can provide more details.

[Mikhail]

The AI answer:

Apache License 2.0 – Simple Explanation

Apache 2.0 is a very friendly and popular open source license with one main rule and several important requirements.

Imagine you’re taking someone’s open source code (Project A) under this license to create your own project (Project B).

✅ What You CAN Do (Almost Everything):

• Use freely: Copy, modify, distribute, and use the code commercially – for free. You can even sell products containing it.
• Create derivatives: Mix this code with your proprietary code without opening your entire project’s source.
• Patent rights: Original authors grant explicit permission to use related patents. If you sue someone over patent infringement related to this code, your rights automatically terminate.

📋 What You MUST Do (Important Requirements):

When distributing your program (Project B) containing Apache 2.0 code:

• Keep notices: Don’t remove original copyrights, patent notices, and Apache 2.0 license text from source files.
• Include LICENSE file: Include a copy of Apache 2.0 license when distributing your project.
• Show changes: Clearly mark any modifications to original files (usually with code comments).
• Notify users: Clearly indicate which parts of your project are under Apache 2.0 (typically in a NOTICE file).

🎯 In Simple Terms:

“You can take this code and do almost anything with it, even in commercial projects. But you must keep the original copyrights visible and honestly acknowledge you used someone else’s work under Apache 2.0.”

⚖️ Key Differences From Other Licenses:

• Similar to MIT: As permissive as MIT but adds explicit patent terms and formal change documentation requirements.
• Different from GPL: NOT “copyleft” or “viral” – you don’t have to open-source your entire project. You can keep proprietary code closed.

📝 The Bottom Line:

Apache License 2.0 works for both business and community. It protects authors through attribution and protects users with explicit patent rights, while allowing free use in commercial products.

[123]

Suppose I modify the graphical interface of the source code based on Rapid SCADA, make changes to the command display interface code, and even add new code for communication acquisition protocols. Would this be considered a derivative product?

If it is considered a derivative product, am I allowed to modify the names and icons in Image 1 and Image 2 below? I have annotated the modified parts in the images.

Image 1 URL：https://imgur.com/a/8RnjW9e
Image 2 URL：https://imgur.com/a/yfuY8xS

If the above images fail to load, you can download them.

[manjey73]

You can change the caption and the picture. You don’t delete the data “About the program”, and you don’t delete the data in the source code. This is called branding. The store and plugins can be disabled via configuration files.

[Mikhail]

Would this be considered a derivative product?

I think, yes.

[Author]

Posts