public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "Andrija Vranić" <andrija.vranic@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: Kawa future and governance
Date: Sun, 15 Nov 2020 09:51:48 +0100	[thread overview]
Message-ID: <CAHOG-LdVgZULbW278ywx4O0DOudSj8gmZ3aA_xVMDcxQ2syJnQ@mail.gmail.com> (raw)
In-Reply-To: <80ad8ede-ef66-3b5c-84e4-d2356b33abc9@bothner.com>

I said it, but one more time: as a beginner I am willing  to be put to use
for any task I can help with!
Cheers,
Andrija

On Sat, 14 Nov 2020 at 20:33, Per Bothner <per@bothner.com> wrote:

> On 11/14/20 10:11 AM, Helmut Eller via Kawa wrote:
> > On Mon, Nov 09 2020, Per Bothner wrote:
> >
> >> I can see my role becoming a Benevolent Dictator For Life (like van
> >> Rossum's role in Python), but ideally getting less dictatorial as others
> >> gain experience.
> >
> > Apparently you have the copyright on most of Kawa's code.
>
> Yep - because I wrote most of it.
>
> > Would contributors have to assign copyrights if they change something?
>
> I have not required copyright assignments.  My informal policy is if a
> file is
> substantially the work of one person, only that person is credited with
> a copyright note in the file.  If multiple people have contributed
> substantially
> (say 20%) they should be listed too.  A change/fix of a few lines does not
> get copyright credit.
>
> But this is more about openness and giving credit where due.  Legally what
> matters is the license.  All contributions must be compatible with the
> appropriate license.  New files must be compatible with the overall
> (software or
> documentation) license, and changes to existing files must preserve the
> license
> of the file (unless those listed in the copyright agree).
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/
>

      reply	other threads:[~2020-11-15  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 17:06 Per Bothner
2020-11-09 17:40 ` Lassi Kortela
2020-11-09 22:03 ` Duncan Mak
2020-11-12  5:39   ` Jamison Hope
2020-11-13 18:27     ` Damien MATTEI
2020-11-14 18:11 ` Helmut Eller
2020-11-14 18:53   ` Per Bothner
2020-11-15  8:51     ` Andrija Vranić [this message]

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=CAHOG-LdVgZULbW278ywx4O0DOudSj8gmZ3aA_xVMDcxQ2syJnQ@mail.gmail.com \
    --to=andrija.vranic@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).