Mfcttrf

I transpose the source code, you transpose the input!

Why is the Common Agricultural Policy unfavourable to the UK?

Installation of ImageMagick software fails with "configure: error: libltdl is required"

"I will not" or "I don't" as an answer for negative orders?

split 1 column input into 5 column bed file

Why is STARTTLS still used?

MaxDetect speed

お仕事に学校頑張って meaning

Does the app TikTok violate trademark?

What does it mean by "my days-of-the-week underwear only go to Thursday" in this context?

Is there a list of world wide upcoming space events on the web?

Sci-fi movie with one survivor and an organism(?) recreating his memories

Is it possible to use && operator in terminal command template loop?

Read-once memory

Why aren't faces sharp in my f/1.8 portraits even though I'm carefully using center-point autofocus?

What in my code changed between MacTeX 2017 and MacTex 2019?

What does `idem` mean in the VIM docs?

What makes learning more difficult as we age?

I reverse the source code, you reverse the input!

Why does it seem the best way to make a living is to invest in real estate?

How far in Advance do I need to book tickets on the West Highland Line in Scotland for a Multi-part Journey?

Can I target any number of creatures, even if the ability would have no effect?

Is it ok if I haven't decided my research topic when I first meet with a potential phd advisor?

Detail vs. filler

GPLv3 forces us to make code available, but to who?

Does using Stanford NER in a website count as distributing it?What do I have to include in the binary package as “corresponding source code” for GPL licensed software?Who owns the copyright to the code which was paid for to write?Of the differences between the GPLv3 and the AGPLv3 texts: what to make of them?Relicensing an MIT licensed project under the GPL that has non code contributions from othersGPLv2 Wordpress Application - SellingUsing iText library with AGPL license to make application open sourcedWho is the copyright holder when GPLv2 project API is used?What widely available software license is appropriate if I want to freely distribute but keep my own right to sell?Commercial license where the code can be seen/edited by others but not monetized by others

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

2

I've read that GPLv3 imposes that we should make the source code of our app available.

But, available to who?
In case we sell our GPLv3 software, does it mean we have to make it available to those we sell the software to? Or to everybody else that didn't purchase it as well? Such as providing a repository online with the code?

licensing gpl distribution

share|improve this question

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

migrated from softwareengineering.stackexchange.com 7 hours ago

This question came from our site for professionals, academics, and students working within the systems development life cycle.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You only have to give the source code to the people you sell your software to. However, the GPL allows those recipients to give it to anyone else for free.
  
  – Brandin
  6 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Brandin: minor nitpick - "... people you distribute your software to." The person you gave a free trial or beta-test copy to is also entitled to the source code, the same as the the person who paid money to buy it from you.
  
  – Stobor
  16 mins ago
  
  

  
  
  
  

add a comment
 | 

2

I've read that GPLv3 imposes that we should make the source code of our app available.

But, available to who?
In case we sell our GPLv3 software, does it mean we have to make it available to those we sell the software to? Or to everybody else that didn't purchase it as well? Such as providing a repository online with the code?

licensing gpl distribution

share|improve this question

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

migrated from softwareengineering.stackexchange.com 7 hours ago

This question came from our site for professionals, academics, and students working within the systems development life cycle.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You only have to give the source code to the people you sell your software to. However, the GPL allows those recipients to give it to anyone else for free.
  
  – Brandin
  6 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Brandin: minor nitpick - "... people you distribute your software to." The person you gave a free trial or beta-test copy to is also entitled to the source code, the same as the the person who paid money to buy it from you.
  
  – Stobor
  16 mins ago
  
  

  
  
  
  

add a comment
 | 

I've read that GPLv3 imposes that we should make the source code of our app available.

But, available to who?
In case we sell our GPLv3 software, does it mean we have to make it available to those we sell the software to? Or to everybody else that didn't purchase it as well? Such as providing a repository online with the code?

licensing gpl distribution

share|improve this question

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

share|improve this question

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

share|improve this question

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

asked 8 hours ago

AlvaroAlvaro

11933 bronze badges

1 Answer
1

active

oldest

votes

7

To any recipients. You do not have to make the source code available to the public, but have to provide the source code to anyone who received the software from you.

The details here depend on how you want to provide the source code (see section 6 of the GPLv3):

• The easiest way is to always bundle the corresponding source code when you give someone a copy of the software.




• If you offer the software for download, you can also offer the corresponding source for download at the same place. For example, any places where you offer your app could link to a GitHub repository with the source code.



• 
  

  Under certain circumstances, you can include a written offer to provide the corresponding source code. This written offer must be valid for at least three years, sometimes longer. You must then provide the software to anyone who contacts you with a copy of that offer, not just to those to whom you gave the software directly.

  
  
  
  • If you only distribute the software “occasionally and noncommercially” in unmodified form, you can also pass along a copy of a written offer that you received.
  
  
  • You can satisfy a written offer either by providing the source code on a physical medium (you may charge postage etc), or by offering the source code for download.
  
  



• Under no circumstances can you charge any fees for the source code itself.

share|improve this answer

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What do you mean by "sometimes longer" for the written offer?
  
  – Brandin
  6 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @Brandin The “certain circumstances” where GPLv3 allows written offers are physical products, and the written offer must be honored “for at least three years and […] for as long as you offer spare parts or customer support for that product model”.
  
  – amon
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't understand the part that says "Under no circumstances can you charge any fees for the source code itself." What if the code itself is the product itself? For example when dealing with a Javascript component for the web? Or a HTML template? Or a PHP script? There's no compilation there at all. The code is all developers need to use it.
  
  – Alvaro
  49 mins ago
  

  
  
  
  

add a comment
 | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "619"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8836%2fgplv3-forces-us-to-make-code-available-but-to-who%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

7

To any recipients. You do not have to make the source code available to the public, but have to provide the source code to anyone who received the software from you.

The details here depend on how you want to provide the source code (see section 6 of the GPLv3):

• The easiest way is to always bundle the corresponding source code when you give someone a copy of the software.




• If you offer the software for download, you can also offer the corresponding source for download at the same place. For example, any places where you offer your app could link to a GitHub repository with the source code.



• 
  

  Under certain circumstances, you can include a written offer to provide the corresponding source code. This written offer must be valid for at least three years, sometimes longer. You must then provide the software to anyone who contacts you with a copy of that offer, not just to those to whom you gave the software directly.

  
  
  
  • If you only distribute the software “occasionally and noncommercially” in unmodified form, you can also pass along a copy of a written offer that you received.
  
  
  • You can satisfy a written offer either by providing the source code on a physical medium (you may charge postage etc), or by offering the source code for download.
  
  



• Under no circumstances can you charge any fees for the source code itself.

share|improve this answer

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What do you mean by "sometimes longer" for the written offer?
  
  – Brandin
  6 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @Brandin The “certain circumstances” where GPLv3 allows written offers are physical products, and the written offer must be honored “for at least three years and […] for as long as you offer spare parts or customer support for that product model”.
  
  – amon
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't understand the part that says "Under no circumstances can you charge any fees for the source code itself." What if the code itself is the product itself? For example when dealing with a Javascript component for the web? Or a HTML template? Or a PHP script? There's no compilation there at all. The code is all developers need to use it.
  
  – Alvaro
  49 mins ago
  

  
  
  
  

add a comment
 | 

7

To any recipients. You do not have to make the source code available to the public, but have to provide the source code to anyone who received the software from you.

The details here depend on how you want to provide the source code (see section 6 of the GPLv3):

• The easiest way is to always bundle the corresponding source code when you give someone a copy of the software.




• If you offer the software for download, you can also offer the corresponding source for download at the same place. For example, any places where you offer your app could link to a GitHub repository with the source code.



• 
  

  Under certain circumstances, you can include a written offer to provide the corresponding source code. This written offer must be valid for at least three years, sometimes longer. You must then provide the software to anyone who contacts you with a copy of that offer, not just to those to whom you gave the software directly.

  
  
  
  • If you only distribute the software “occasionally and noncommercially” in unmodified form, you can also pass along a copy of a written offer that you received.
  
  
  • You can satisfy a written offer either by providing the source code on a physical medium (you may charge postage etc), or by offering the source code for download.
  
  



• Under no circumstances can you charge any fees for the source code itself.

share|improve this answer

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What do you mean by "sometimes longer" for the written offer?
  
  – Brandin
  6 hours ago
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @Brandin The “certain circumstances” where GPLv3 allows written offers are physical products, and the written offer must be honored “for at least three years and […] for as long as you offer spare parts or customer support for that product model”.
  
  – amon
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't understand the part that says "Under no circumstances can you charge any fees for the source code itself." What if the code itself is the product itself? For example when dealing with a Javascript component for the web? Or a HTML template? Or a PHP script? There's no compilation there at all. The code is all developers need to use it.
  
  – Alvaro
  49 mins ago
  

  
  
  
  

add a comment
 | 

To any recipients. You do not have to make the source code available to the public, but have to provide the source code to anyone who received the software from you.

The details here depend on how you want to provide the source code (see section 6 of the GPLv3):

• The easiest way is to always bundle the corresponding source code when you give someone a copy of the software.




• If you offer the software for download, you can also offer the corresponding source for download at the same place. For example, any places where you offer your app could link to a GitHub repository with the source code.



• 
  

  Under certain circumstances, you can include a written offer to provide the corresponding source code. This written offer must be valid for at least three years, sometimes longer. You must then provide the software to anyone who contacts you with a copy of that offer, not just to those to whom you gave the software directly.

  
  
  
  • If you only distribute the software “occasionally and noncommercially” in unmodified form, you can also pass along a copy of a written offer that you received.
  
  
  • You can satisfy a written offer either by providing the source code on a physical medium (you may charge postage etc), or by offering the source code for download.
  
  



• Under no circumstances can you charge any fees for the source code itself.

share|improve this answer

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

share|improve this answer

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges

answered 6 hours ago

amonamon

16k11 gold badge1919 silver badges4242 bronze badges