public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Items for Council Agenda, May 14
Date: Sun, 30 Apr 2017 15:52:20 +0200	[thread overview]
Message-ID: <1663903.3hoEA2dtjj@pinacolada> (raw)
In-Reply-To: <0ac908a7-9875-f629-fa0c-0c85945e1185@gentoo.org>

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

Am Samstag, 29. April 2017, 19:00:34 CEST schrieb Anthony G. Basile:
> Hi everyone,
> 
> The Gentoo Council will be meeting in two weeks.  If anyone has any
> issues we need to discuss, please let me know and I'll put it on the
> agenda.  Thanks.

Guidelines for the council summaries

This is the result of reading (and improving) way too many horrible old 
council summaries [*]. I see it as recommendation for best practices, not 
really something we need a written-and-stamped-approved policy for. Anyway we 
should maybe talk about it once.

1] Anything that was decided by the council outside the logged council meeting 
within the last month (e.g. a vote on a bug) needs to be added to the summary 
with reference to the source. 

2] A link to the meeting agenda on archives.gentoo.org should be included in 
the log and/or summary.

3] Agendas and similar documents should be posted to the mailing list(s) as 
part of the main e-mail body, not as attachment (since the attachments are not 
shown on archives.gentoo.org).

4] Referenced documents (e.g. policy drafts available in somebody's devspace 
or on a pastebin) should be included in the log and/or summary (at the end). 
The only exception is texts available on archives.gentoo.org, in our VCSs or 
on our bugzilla.

5] If there was a formal vote, the summary should list voting results (x yes, 
y no, ...) and the exact wording that was voted on.

Anything else?

Cheers, Andreas

[*] http://dev.gentoo.org/~dilfridge/decisions.html  (work in progress)

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2017-04-30 13:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 17:00 [gentoo-project] Items for Council Agenda, May 14 Anthony G. Basile
2017-04-30 13:52 ` Andreas K. Huettel [this message]
2017-05-03 21:26   ` Daniel Campbell
2017-05-06 14:34 ` arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) Andreas K. Huettel
2017-05-06 16:35   ` [gentoo-dev] " Michał Górny
2017-05-06 17:36     ` Andreas K. Huettel
2017-05-06 20:23       ` Michał Górny
2017-05-07  2:53         ` Kent Fredric
2017-05-07 20:30       ` Michał Górny
2017-05-08 11:46         ` Andreas K. Huettel
2017-05-13  0:03     ` Andreas K. Huettel
2017-05-13  7:44       ` Michał Górny
2017-05-13 22:48         ` Andreas K. Huettel
2017-05-07 15:47   ` Roy Bamford
2017-05-14 15:38     ` Andreas K. Huettel
2017-05-11  7:17 ` [gentoo-project] Items for Council Agenda, May 14 Matthias Maier
2017-05-11  7:52   ` NP-Hardass
2017-05-11  8:02     ` Michał Górny
2017-05-11  9:16       ` Raymond Jennings
2017-05-11 10:08   ` Kent Fredric
2017-05-11 10:52     ` Rich Freeman
2017-05-11 15:03       ` Gregory Woodbury
2017-05-11 16:45   ` Luis Ressel
2017-05-11 19:57     ` Rich Freeman
2017-05-11 20:24       ` William L. Thomson Jr.
2017-05-11 20:28       ` Michał Górny
2017-05-13  9:26       ` Kent Fredric
2017-05-14  1:46         ` M. J. Everitt
2017-05-11 18:55   ` Roy Bamford
2017-05-11 19:09     ` Raymond Jennings
2017-05-11 19:54       ` Rich Freeman
2017-05-13  9:14       ` Kent Fredric
2017-05-11 20:25   ` William L. Thomson Jr.
2017-05-11 23:07   ` Daniel Campbell
2017-05-12  8:52     ` Roy Bamford
2017-05-12 10:41       ` Andreas K. Huettel
2017-05-13  9:36         ` Daniel Campbell

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=1663903.3hoEA2dtjj@pinacolada \
    --to=dilfridge@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