unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: law question
Date: Sat, 22 May 2021 00:09:32 +0300	[thread overview]
Message-ID: <YKghjFMNjErbk+Yl@protected.localdomain> (raw)
In-Reply-To: <87tumvdcqz.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-05-22 00:00]:
> What happens if there is a company only when the code gets
> released just moments before it is rewritten as FOSS?

What happens is that people start asking about it...

Author may change the licensing of some software, but not for previous
versions already distributed and received. But if you have never
received it and nobody else received it who can give it to you, bad
luck.

Example is the SugarCRM, they had community version and they stopped
making a community version, so they discontinued free software
releases and sell only proprietary. However, nobody can take you away
the license once granted for the previous version. See example:
https://github.com/matthewpoer/SugarCRM-Community-Edition/tree/master/OldFiles 

Same thing would be if some company arrives and wish to take over the
software, it does not matter for the recipient. If you have downloaded
it with specific license you have got your rights. And then you could
make your own fork if you wish: https://suitecrm.com/


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2021-05-21 21:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 20:59 law question Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:09 ` Jean Louis [this message]
2021-05-21 21:17 ` Christopher Dimech
2021-05-21 21:21   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:30     ` Jean Louis
2021-05-21 21:37       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:46     ` Christopher Dimech
2021-05-21 23:15       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 23:31         ` Christopher Dimech
2021-05-21 23:56         ` Christopher Dimech
2021-05-22  0:12           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 22:34     ` Christopher Dimech
2021-05-22  6:14       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YKghjFMNjErbk+Yl@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).