[GH-ISSUE #597] GPL License #351

Closed
opened 2026-02-27 15:50:00 +03:00 by kerem · 7 comments
Owner

Originally created by @pratik2pris on GitHub (Apr 5, 2017).
Original GitHub issue: https://github.com/quasar/Quasar/issues/597

Hello

I hope you are doing well. I am very much impressed with this tool and want to expand this as per our requirement.

I have few questions regarding the license here

As per GPL License.

For example, if we distribute copies of this program, whether gratis or for a fee, we must pass on to the you the same freedoms that you received. We must make sure that you, too, receive or can get the source code. And we must show you these terms so you know their rights. this means that anything we change has to be publicly available.

with gpl3 anything i pay for has to be offered to the community. How do we fork this so that we can privately develop our own paths and features? Is there is a purchase source code option so that we may do so.

Summary I want to modify this as per our requirement and then we will publish to our partners and we want our own copyright option.

Originally created by @pratik2pris on GitHub (Apr 5, 2017). Original GitHub issue: https://github.com/quasar/Quasar/issues/597 Hello I hope you are doing well. I am very much impressed with this tool and want to expand this as per our requirement. I have few questions regarding the license here As per GPL License. For example, if we distribute copies of this program, whether gratis or for a fee, we must pass on to the you the same freedoms that you received. We must make sure that you, too, receive or can get the source code. And we must show you these terms so you know their rights. this means that anything we change has to be publicly available. with gpl3 anything i pay for has to be offered to the community. How do we fork this so that we can privately develop our own paths and features? Is there is a purchase source code option so that we may do so. Summary I want to modify this as per our requirement and then we will publish to our partners and we want our own copyright option.
kerem 2026-02-27 15:50:00 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@abdullah2993 commented on GitHub (Apr 5, 2017):

https://github.com/quasar/QuasarRAT/issues/499

<!-- gh-comment-id:291763445 --> @abdullah2993 commented on GitHub (Apr 5, 2017): https://github.com/quasar/QuasarRAT/issues/499
Author
Owner

@pratik2pris commented on GitHub (Apr 10, 2017):

@Abdullah2993 Thanks for the information but we are not looking for this solution. We need to Purchase the source code and modify as per our requirement and distribute it. ( Do not want it to public )

@MaxXor as you are the owner let me know how can I reach to your for more discussion. Or could you update me with the solution please.

Looking forward for your response.

<!-- gh-comment-id:292847004 --> @pratik2pris commented on GitHub (Apr 10, 2017): @Abdullah2993 Thanks for the information but we are not looking for this solution. We need to Purchase the source code and modify as per our requirement and distribute it. ( Do not want it to public ) @MaxXor as you are the owner let me know how can I reach to your for more discussion. Or could you update me with the solution please. Looking forward for your response.
Author
Owner

@abdullah2993 commented on GitHub (Apr 10, 2017):

@pratik2pris its an open source project so let alone @MaxXor can't change the license. He has to get the consent from all the contributors...

<!-- gh-comment-id:292914553 --> @abdullah2993 commented on GitHub (Apr 10, 2017): @pratik2pris its an open source project so let alone @MaxXor can't change the license. He has to get the consent from all the contributors...
Author
Owner

@MaxXor commented on GitHub (Apr 14, 2017):

@pratik2pris At the moment when you change the code of Quasar and want to sell it or just give it away for free you have to disclose the source code too. Not only for me, but for everyone. So you can't privately develop it and then only publish the compiled software (binaries) to your partners. To allow this non-public distribution I need to change the license. There is no purchase option for the source code.

@Abdullah2993 I consider changing the license to MIT to allow this.

<!-- gh-comment-id:294130093 --> @MaxXor commented on GitHub (Apr 14, 2017): @pratik2pris At the moment when you change the code of Quasar and want to sell it or just give it away for free you have to disclose the source code too. Not only for me, but for everyone. So you can't privately develop it and then only publish the compiled software (binaries) to your partners. To allow this non-public distribution I need to change the license. There is no purchase option for the source code. @Abdullah2993 I consider changing the license to MIT to allow this.
Author
Owner

@abdullah2993 commented on GitHub (Apr 14, 2017):

@MaxXor that would be amazing

<!-- gh-comment-id:294137947 --> @abdullah2993 commented on GitHub (Apr 14, 2017): @MaxXor that would be amazing
Author
Owner

@pratik2pris commented on GitHub (Apr 18, 2017):

@MaxXor so once you update to MIT license I can publish / develop privately and do not disclose the source code to you and contributor.

Let me know once you are update to MIT license.

Thanks for your support

<!-- gh-comment-id:294861750 --> @pratik2pris commented on GitHub (Apr 18, 2017): @MaxXor so once you update to MIT license I can publish / develop privately and do not disclose the source code to you and contributor. Let me know once you are update to MIT license. Thanks for your support
Author
Owner

@abdullah2993 commented on GitHub (Apr 18, 2017):

@pratik2pris sure. You can

<!-- gh-comment-id:294905440 --> @abdullah2993 commented on GitHub (Apr 18, 2017): @pratik2pris sure. You can
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#351
No description provided.