Avalonia Accelerate and Open Source project usage and licensing #17149
Replies: 2 comments 1 reply
-
I'll try my best to answer below: Licensing approach Visual Designer Per-seat licensing For open-source projects, I'd recommend using open-source controls that align better with your project's licensing model if using paid controls isn't viable. This is typically how it's been done with other OSS projects using frameworks like WinForms and WPF. Regarding tools like the visual designer, OSS projects can still benefit from it as it generates XAML. This means projects can be shared in the same way as they are today without requiring licenses for all contributors. We understand the complexities this introduces for open-source projects, especially those with diverse contributor bases. We're committed to supporting the open-source community while balancing the sustainability of our pro offerings. |
Beta Was this translation helpful? Give feedback.
-
I know there will likely be more forthcoming info but relating to this quote: Say I have 10 separate clients who I develop different commercial applications and all contain AA features such as web dialog. Each of those 10 clients sell the software to thousands of customers. If I am the only dev that builds the project is only 1 licence required? The terminology 'consume any Avalonia Accelerate features' is a little vague on who the consumer is, the dev or the app end users. |
Beta Was this translation helpful? Give feedback.
-
It's great to hear that there's large amount of effort being done to improve Avalonia via Accelerate project, but I have some questions about use of Accelerate components in open source projects.
I develop OSS project currently built with WPF that I'm in process of rewriting from scratch and I was initially redoing everything in Avalonia, but for various reasons I'm staying on WPF for now. One of the reasons being not so great developer experience, mainly in terms of user friendly designer support, which is why I was quite happy to see that this is being addressed via Accelerate somewhat.
I don't mind personally paying for these Accelerate components, but my project also has two separate groups of external contributors and I'm interested in knowing how it's going to work, license wise, if I decide to include Accelerate components in my OSS project. The groups are:
Lets say I decide to include video player Accelerate component in my project, will now every person contributing code to the project need to acquire Accelerate license since it's being licensed "per seat" and that developer is technically new "seat" on the project? What about theme developers that will make new themes for views that include video player component? Or plugin developers wanting to use video player in their plugins?
I kind of expect theme developers to be required to buy a license for visual designer, which is honestly not great since majority of add-on developers on my project are non-programmer hobbyists, but the main question is about components being built into the core project, like video player or web view.
Lastly, bit on a technical side, how do play for license verification to work with OSS projects? How are licenses going to be verified and issued? Would just any drive by developer be able to fork the project and build it with included Accelerate components or are there going to be some special checks and verifications needed?
Beta Was this translation helpful? Give feedback.
All reactions