<div dir="ltr">Google Groups seems to be a popular forum / list discussion solution. <div><br></div><div>An open source mapping platform called Cesium uses it with much success:<div><a href="https://groups.google.com/forum/#!forum/cesium-dev">https://groups.google.com/forum/#!forum/cesium-dev</a><br></div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 28, 2015 at 5:25 AM, Michael Wilde <span dir="ltr"><<a href="mailto:wilde@anl.gov" target="_blank">wilde@anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Dear All,<br>
<br>
We need to handle this in the next 2 days to avoid outages on the
Swift lists.<br>
<br>
Has anyone already taken some actions for this, or has there already
been a discussion or decision on how to handle this?<br>
<br>
Whats the most accessible and open-source-friendly way to maintain
list discussions? We might need an interim solution, or we can use
this as an opportunity to improve our communication channels and
unify Swift K & T communications.<br>
<br>
Craig's latest reminder on the CI mailing list close-out is at the
end of this message.<br>
<br>
Thanks,<br>
<br>
- Mike<span class=""><br>
<br>
<br>
<div>On 6/30/15 1:53 AM, Mihael Hategan
wrote:<br>
</div>
</span><blockquote type="cite"><span class="">
<pre>On Mon, 2015-06-29 at 23:16 -0500, Michael Wilde wrote:
</pre>
</span><blockquote type="cite">
<pre><span class="">This may be a good time to make the lists appear to be hosted at
</span><a href="http://swift-lang.org" target="_blank">swift-lang.org</a>.
</pre>
</blockquote><span class="">
<pre>An even better idea.
</pre>
<blockquote type="cite">
<pre>It would also be good to move the list archives to that domain. We
should see if that is possible, an dhow forwarding would work.
</pre>
</blockquote>
<pre>Yeah, I don't get how this works, but from Ian's quote of what Craig
says, the implementation and the interface seem to be different things.
So we should probably talk to Craig.
Mihael
</pre>
</span></blockquote>
-------- Forwarded Message --------
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Subject: </th>
<td>REMINDER:Swift-devel mailing list to be retired July 31,
2015</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Date: </th>
<td>Mon, 27 Jul 2015 09:09:39 -0500</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">From: </th>
<td>Craig Stacey <a href="mailto:stace@mcs.anl.gov" target="_blank"><stace@mcs.anl.gov></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Reply-To:
</th>
<td><a href="mailto:support@ci.uchicago.edu" target="_blank">support@ci.uchicago.edu</a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">To: </th>
<td><a href="mailto:Swift-devel-owner@ci.uchicago.edu" target="_blank">Swift-devel-owner@ci.uchicago.edu</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre><span class="">As previously announced, the CI mailing list server will soon be retired.
You're receiving this message as a list owner of a list housed at
</span><a href="http://lists.ci.uchicago.edu" target="_blank">lists.ci.uchicago.edu</a>. Specifically, the following list:
<a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a>, Last post at Sat Jul 25 09:12:44 2015.
<a href="https://lists.ci.uchicago.edu/mailman/listinfo/Swift-devel" target="_blank">https://lists.ci.uchicago.edu/mailman/listinfo/Swift-devel</a><span class="">
(Note the above link also contains a link to any archives of the list as well.)
If you do nothing, the list will stop working at end of July. Any archives that
exist will disappear when the server is retired at that point. Mail sent to
</span><a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a> and <a href="mailto:Swift-devel@lists.ci.uchicago.edu" target="_blank">Swift-devel@lists.ci.uchicago.edu</a> will bounce,
and the sender will receive a notice that the address is no longer valid.
If you want to retain and move the list, your best option is to create a new
list on the service of your choice (for example, ITS provides mailing lists at
<a href="https://itservices.uchicago.edu/services/mailing-lists" target="_blank">https://itservices.uchicago.edu/services/mailing-lists</a>). We don't have a way
to automate this process of moving from one service to another, unfortunately.
However, if you'd like a raw text dump of your existing configuration and
membership, we can provide that, simply let us know. Otherwise, the web UI to
see your existing configuration and membership can be found at
<a href="https://lists.ci.uchicago.edu/mailman/admin/Swift-devel" target="_blank">https://lists.ci.uchicago.edu/mailman/admin/Swift-devel</a>. If you've forgotten the
password for your list, please let us know and we'll reset it.
Once you've got your new list configured and ready, if you'd like we can point
the existing listname <a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a> to that new address. Or you
can simply switch to using the new address, whatever that may be.
If you want the archives of your old CI list, let us know. We can provide the
raw archives (including static HTML files) for you to use as you wish. We do
not have a method of transferring the archives to whatever list provider you
choose to use for your new list, however.
Thanks, and sorry for the inconvenience.
</pre>
<br><span class="">
<pre cols="72">--
Michael Wilde
Mathematics and Computer Science Computation Institute
Argonne National Laboratory The University of Chicago
</pre>
</span></div>
<br>_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" rel="noreferrer" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
<br></blockquote></div><br></div>