public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: [gentoo-project] meeting agenda -- council meeting 2020-02-09
Date: Mon, 3 Feb 2020 20:55:42 -0600	[thread overview]
Message-ID: <20200204025542.GA11627@linux1.home> (raw)

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

All,

here is the agenda for the 2020-02-09 council meeting:

1. roll call

2. Licensing ebuilds as gpl 2+

a. Can developers individually decide to license their ebuilds as GPL-2+
rather than 'GPL-2 only' (provided that they fulfill relicensing
requirements)?

b. Should developers be encouraged to use GPL-2+ for new ebuilds
(whenever possible)?

c. Should we start collecting permissions from contributors to relicense
their GPL-2 work as GPL-2+?  This will be helpful both to 1. and 2.

3. open bugs with council participation

https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

4. open floor


Thanks,

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

                 reply	other threads:[~2020-02-04  2:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200204025542.GA11627@linux1.home \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.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