public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: ISAR priv became public
Date: Tue, 6 Feb 2024 12:49:41 +0100	[thread overview]
Message-ID: <CAJGKYO6erSvH-n11QPN0pwOeSn1qHAnZ65q+B+1EfVptQYd_+Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]

Hi all,

 the private fork on which I worked between Q4/2022 and Q1/2023 is not
public.

 https://github.com/robang74/isar.priv

 I recently received some money from the German unemployment fund and I
decided that public money implies public code. Therefore, I publish this
git project.

 Please, note that the license is changed more toward freedom and this
means that it is more restrictive for commercial / business purposes, in
some cases. However, at this point, it is quite improbable that someone
would make a merge because that repository has not been updated for a long
time.

 Despite this, it might be useful for inspiration. In the corner case,
integrating a patch containing my own code would be a much easier way
rather than reworking the code in order to avoid license issues: prepare
the patch and submit to me, I will check it and I will publish in this
m-list with the MIT license reverted back.

 Because the MIT license allowed me to change the license of my own rework
without limiting or influencing the original work and I am the sole author
of that rework, I can revert back the license as long as I will remain the
sole author of that code. Therefore, I do not expect nor I am willing to
accept contributions from other people in order to remain free to revert
the license back.

 I hope this will sound reasonable for you as well. If not, please write to
me in private. For this reason, for this time only, I will include after my
full name also my mobile phone contacts.

 Please notice that this m-list is not related to the ISAR.priv. Hence, if
you like to debate or you wish to receive more information or any kind of
support about this specific fork, write to me in private, not here.

 Best regards,
-- 
Roberto A. Foglietta
+49.176.274.75.661
+39.349.33.30.697

[-- Attachment #2: Type: text/html, Size: 2335 bytes --]

             reply	other threads:[~2024-02-06 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 11:49 Roberto A. Foglietta [this message]
2024-02-06 12:00 ` Roberto A. Foglietta

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

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

  git send-email \
    --in-reply-to=CAJGKYO6erSvH-n11QPN0pwOeSn1qHAnZ65q+B+1EfVptQYd_+Q@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.com \
    /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