From toshio:

skvidal's email prompted me to take a look at what precisely is going on with
fesco list. It was a little surprising looking into fesco-list's past;
lot's of things I had forgotten about or didn't know:

• Some people on fesco list were never on fesco
• History of fesco list posts seems to indicate that we've never removed
  people from the list when their term ends yet some people are not on it.
  My assumption is that some people (like knurd when he decided it was
  a conflict of interest) unsubscribed themselves.
• I couldn't find a policy about removing past members from the list and
  judging from the posts, I'd say it was expected that active Fedora
  contributors would continue to post to fesco-list even after their term
  ended.
• fesco-list was thought to be used for too much and should be reserved only
  for non-public posts several times in the past yet each time, we
  eventually started using it for public issues again. I've linekd to one
  such example in the archives but there's at least one older one in the
  fesco meeting logs and others in the archives that I have not linked to.
• I think in the very beginning fesco list was a list where work got done.
  That could be done again but in that case the future archives should be
  made public.

I started to write up the following meeting ticket before doing this
research. The ticket needs to be revised somewhat in light of the research.
I'd add the history I dug up to the overview section and recommend posting
the list of people on fesco list to the wiki as the most desirable option
given the tradition and usefulness of having past fesco members remain on
the list.

I'd also recommend appointing someone to enforce public messages going to
public lists and perhaps having a defined best practice for producing drafts
(Seems we've always been bad about getting stuff started on the fesco-list
into practice. Remember the discussion of making FPC and releng
reports/rubber stamping more sane, possibly delegating the Feature Process,
and otherwise streamlining FESCo? Things were agreed there but not put into
practice) but these are things for another ticket.

What do you all think of all this?

-Toshio

= Proposal topic =

Who should be on fesco list

= Overview =

Current rules for use of fesco-list:

21:31:43 <nirik> #agreed The fesco list is for nonpublic/sensitive matters.
Use trac for public issues. Use of the private list will be kept to
a minimum.

http://meetbot.fedoraproject.org/fedora-meeting/2010-02-02/fesco.2010-02-02-20.01.log.txt

Many past examples going back at least to 2006 that state basically the same
thing. Here's a fesco-list thread that had some substance to it:

https://admin.fedoraproject.org/mailman/private/fesco/2007-October/002395.html

There is no definition of who is on fesco list in this but the idea of being
for nonpublic issues means the list should be small for some definition of
small. We should decide that and document it so that expectations of what
can be sent to fesco list and what should be sent to individuals is properly
set.

Currently, fesco consists of all members of current fesco, some of the
people from past fescos, and two that have never been on fesco:
* Paul Frields -- arguably on it to facilitate communication between the
Board and fesco.
* John Poelstra

= Problem space =

Documenting who is on fesco list so people sending sensitive issues there
know who they are contacting.

= Solution Overview =

Options:
* Simply post the list of people on fesco list publically to the wiki to
set expectations
* Remove everyone but the current members of fesco (probably the current
expectation of people posting to fesco list)
* Remove everyone but current members of fesco and the current Fedora
Project Leader (not a big stretch but should be documented on the wiki)
* Remove everyone but current members of fesco and selected representatives
of other groups -- poelcat as the package wrangler. spot, toshio, or
tibbs as FPC representatives. jwb or f13 as releng representatives.
toshio or mmcgrath as infrastructure representative. stickster as the
* Board representative. (Need to document the subscribers on the wiki)
* Can have rules about whether non-fesco members are supposed to post or
are only included to be informed of fesco issues.
* Close fesco list. Non-public information should be sent to fesco members
via private email.

Additionally, the list admins may need to be adjusted to only have people
who are subscribed to the pruned mailing list.

= Active Ingredients =

• https://lists.fedoraproject.org/mailman/listinfo/fesco
• Members of past and present fesco as well as poelcat and stickster

= Owners =

toshio