<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The only real thing I can think of would be discussions of potential future wheel people. <div class="">Current list memebers might be less candid if it's going to be archived for the subject to see later.<div class=""><br class=""></div><div class="">Cheers,</div><div class="">Matt<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Wed 15/5/2019, at 9:46 pm, Felix von Perger <<a href="mailto:frekk@ucc.asn.au" class="">frekk@ucc.asn.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><div class=""> <br class="webkit-block-placeholder"></div><p class="">Moved to committee list since it's not really wheel- or
tech-related beyond the name of the mailing list in question.</p><p class="">I was thinking of enabling private archives, since it's a private
list anyway, and anything sent to the list is insecure to the
extent that the archives are equally accessible to someone with
root access as another person's inbox.<br class="">
</p><p class="">Bob's point is fair - although I don't see any reason why
committee-only needs to be an alias and non-archived, beyond the
fact it is already set up like that way and is therefore
convenient.</p><p class="">One reason to enable private archives is that past discussions
can be used for later reference by current/future wheel/committee
members, which has many possible (beneficial) uses. If anything,
having those private archives is especially important since they
could contain useful insights on how unusual or sensitive issues
have been dealt with in the past, where public records are either
nonexistent or deliberately censored. Certainly with committee,
this would be useful in combination with the existing public
committee archives, wiki, etc.<br class="">
</p><p class=""> Also it acknowledges that people should have to uphold a certain
standard of communication in those (official?) channels on the
basis it is potentially subject to future scrutiny. I guess it's
not really transparent unless it's actually public, but you can't
necessarily guarantee that will be possible depending on what sort
of sensitive stuff there is. In any case, it's probably a step in
the right direction.<br class="">
</p><p class="">I think sending stuff to the correct lists (public or private) is
a separate matter. But yes, for the most part, anything that
should be public is sent to the public lists where it is then also
publicly archived. This conversation for example (!)</p><p class="">Part of the reason for asking is that doorgroup has (always?)
been privately archived. Since the mailman makes it easy to enable
archives I figured why not turn it on for wheel too.<br class="">
</p><p class="">- Felix</p>
<div class="moz-cite-prefix">On 15/5/19 6:23 pm, James French wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAPzvwpgEKE3LND6T+BqVgUYkdjXxQdL+wvS8VF3y0T5+Z0w_0Q@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">
<div class="">I've gone back a little further in my own archive and there
is some stuff on this list that is sensitive (domain
passwords, security incidents etc). Although infrequent that
stuff is what the list is notionally for, ergo private.
Reality is this is a very quiet list the majority of the time,
most discussion happens on tech@</div>
<div class=""><br class="">
</div>
<div class="">Arguably the "sensitive" stuff includes conversations about
new wheel members, but in the interests of transparency, I
don't really have an objection to making that public.</div>
<div class=""><br class="">
</div>
<div class="">Having said that, you're right too though Felix, by and
large most of what's come here is stuff back and forth with
ITS, and that isn't particularly sensitive most of the time
(except when it is). Tech would arguably be a better place for
that too (except when it isn't).</div>
<div class=""><br class="">
</div>
<div class="">I don't mind the idea of a /private/ archive, as it might
be helpful to new wheel members. The concern is just passwords
going into it.</div>
<div class=""><br class="">
</div>
<div class="">I actually wouldn't object to putting the various committee
aliases (or just exec if there were concerns) on this list.
Historically there's been a critical mass of committee on this
list anyway that it's never been too big of an issue.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">F.</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 15 May 2019 at 14:56,
Andrew Adamson <<a href="mailto:bob@ucc.gu.uwa.edu.au" target="_blank" moz-do-not-send="true" class="">bob@ucc.gu.uwa.edu.au</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">We
don't archive wheel@ for the same reasons that committee-only
is not <br class="">
archived - anything that should be public already is because
it has been <br class="">
sent to tech@ instead.<br class="">
<br class="">
Andrew Adamson<br class="">
<a href="mailto:bob@ucc.asn.au" target="_blank" moz-do-not-send="true" class="">bob@ucc.asn.au</a><br class="">
<br class="">
|"If you can't beat them, join them, and then beat them."
|<br class="">
| ---Peter's Laws
|<br class="">
<br class="">
On Wed, 15 May 2019, Felix von Perger wrote:<br class="">
<br class="">
> Hi all,<br class="">
> <br class="">
> Something I'd like to consider, and would like some input
from those it<br class="">
> affects - is there any problem enabling archiving of the
wheel mailing list?<br class="">
> <br class="">
> While I've been here, I haven't seen anything which
shouldn't be kept<br class="">
> on-record (even if private/confidential). Given that I've
not been here very<br class="">
> long I'd like to hear if there are any particular reasons
why the archives are<br class="">
> disabled, or barriers to enabling the archive function.<br class="">
> <br class="">
> Cheers,<br class="">
> <br class="">
> Felix<br class="">
> <br class="">
<br class="">
</blockquote>
</div>
</blockquote>
</div>
_______________________________________________<br class="">List Archives: <a href="http://lists.ucc.asn.au/pipermail/committee" class="">http://lists.ucc.asn.au/pipermail/committee</a></div></blockquote></div><br class=""></div></div></body></html>