search

chocolatey / ChocolateyGUI

A delicious GUI for Chocolatey
https://docs.chocolatey.org/en-us/chocolatey-gui/
Apache License 2.0
1.64k stars 250 forks source link

Is extensibility available? #456

Open another-guy opened 7 years ago

another-guy commented 7 years ago

This project is not very well documented, therefore I only searched for the answer to my question in GitHub issues.

I wonder where to start if I want to create an extension for ChocolateGui? Is there an API or some other "hooks" I can consume? Any examples of trivial extensions?

Thanks!

RichiCoder1 commented 7 years ago

There's currently no extensibility API, or any plans to provide one. What did you have in mind?

another-guy commented 7 years ago

@RichiCoder1 just wanted to write an extension which would allow users to do scheduled setup/update and other fancy things. The GUI is supposed to make users more comfortable with chocolatey, since there's no need to deal with the command line. But the UX is still in the same spot where I saw the tool many months ago.

I would like to contribute, but not directly to ChocolateyGUI, because it's under Apache 2.0 which I don't like at all (but you have your rights and reasons to make your product whatever license you want).

This leaves me with the question of extensibility -- I could write the open source extensions and have them MIT licensed.

If this is not an option too, I will have to leave that idea and write some easy to use PowerShell/bash around choco. It should be pretty easy to build trivial UI around the highly activity-specific scripts.

ferventcoder commented 6 years ago

I would like to contribute, but not directly to ChocolateyGUI, because it's under Apache 2.0 which I don't like at all (but you have your rights and reasons to make your product whatever license you want).

@another-guy honest curiosity, what is it about the Apache v2 license that keeps you at bay from contributing under it?

another-guy commented 6 years ago

@ferventcoder I don't think license discussions would be on topic here. You may think, this is a "religious" question to me. In short, Apache 2.0 is less permissive -- it makes me think about things I don't want to think when dealing with OSS.

ferventcoder commented 6 years ago

Perhaps we find another avenue for discussion. It's not a religious reason at all for us in that we use Apache v2. Yes, it's a bit less permissive than MIT in that it has extra protections for us - someone can't reuse the source code without attribution, nor can they use our trademarks. Both of which are very important when you have a company behind the FOSS product(s). As long as you are not doing either of those things, you typically don't have to think about more than you don't want to think about as compared to MIT.

image

It's your choice not to contribute and I totally respect that. Just wanted to understand the reasoning behind it.

another-guy commented 6 years ago

@ferventcoder I am not a lawyer. The link below has an answer saying that:

... The Apache License has a few more restrictions. Notably, if you change any Apache-licensed code, you must state so. ...

This part is actually seen on your screenshot as well. That is the "state changes" under the Conditions section.

... The Apache license is notable among open-source licenses for including language dealing with patents ...

Simply seeing this limitations makes me think about how to deal with a particular open-source project. I don't have enough energy, competence, and/or motivation to dig into this aspect of software development. That's why I stay away of anything that not BSD or (preferably) MIT. Again, I totally understand that it is my personal preference, so I'm not even remotely thinking about a license change as an option for ChocolateyGUI. Just explaining my way of thinking.

https://www.quora.com/Whats-the-difference-between-Apache-v2-0-and-MIT-license-What-are-the-major-consequences-of-using-Apache-software-over-MIT