<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 2014-02-05 10:37, Joachim Strömbergson wrote:<br>
<blockquote type="cite">Aloha!<br>
<br>
I've had a few discussions with LinusN regarding the different
mailing<br>
lists (and we have also had a few discussions on the mailing lists
too).<br>
<br>
The lists and short charter are described here:<br>
<a class="moz-txt-link-freetext" href="https://cryptech.is/wiki/MailingLists">https://cryptech.is/wiki/MailingLists</a><br>
<br>
Right now we have four lists:<br>
<br>
* announce<br>
* tech<br>
* core<br>
* org<br>
<br>
@announce is pretty easy to understand. Releases, Vulnerabilties
etc.<br>
<br>
@tech is the where the technical discussions about the stuff we
are<br>
developing. Also pretty easy.<br>
<br>
@org is about financing and administration. Does that include
system<br>
administration issues such as (for example) git repo problems?<br>
<br>
</blockquote>
<br>
I don't think it should<br>
<br>
<blockquote type="cite">And then we have @core. From experience in
FreeBSD I can understand<br>
having a core team list with a smaller (and controlled) number of<br>
participants where strategic discussions can be handled among the<br>
project principals. But I (and Linus) are a bit afraid that we
risk<br>
creating a "we vs them"-situation with this separation. We want to
be<br>
open and inclusionary. Both as a way of getting interest and
support,<br>
but also to build trust.<br>
<br>
I (we) therefore have a bit of a problem understanding the
separation of<br>
discussions in @core with discussions in @tech and to some extent<br>
discussions in @org.<br>
<br>
Do we really need @core? What purpose does it solve and can those<br>
problems be handled in other ways?<br>
<br>
And regarding sysadmin issues - are they part of the "admin"
charter for<br>
@org? To me they may be so. It os not as if the list is swamped
with<br>
mails. OTOH having an open maillist for sysadmin things might be
good.<br>
<br>
My suggestion is to merge @core and @org (into @org). And possibly<br>
update charter for @org to clarify what admin means.<br>
<br>
<br>
(I have issues regarding the git repo that may be well worth
discussion<br>
among more persons than me and Linus and Rob. But I am sort of
stuck on<br>
where to send them.)<br>
<br>
</blockquote>
<span style="white-space: pre;">>
_______________________________________________<br>
> Core mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Core@cryptech.is">Core@cryptech.is</a><br>
> <a class="moz-txt-link-freetext" href="https://cryptech.is/mailman/listinfo/core">https://cryptech.is/mailman/listinfo/core</a></span><br>
<br>
<br>
</body>
</html>