Showing content from http://mail.python.org/pipermail/python-dev/attachments/20171026/461f02fd/attachment-0001.html below:
<br><br>On Thursday, October 26, 2017, Mark Sapiro <<a href="mailto:mark@msapiro.net">mark@msapiro.net</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/26/2017 07:28 AM, Wes Turner wrote:<br>
><br>
><br>
> On Thursday, October 26, 2017, Paul Moore <<a href="javascript:;" onclick="_e(event, 'cvml', 'p.f.moore@gmail.com')">p.f.moore@gmail.com</a>> wrote:<br>
><br>
>Â Â Â On 26 October 2017 at 10:24, Victor Stinner<br>
>Â Â Â <<a href="javascript:;" onclick="_e(event, 'cvml', 'victor.stinner@gmail.com')">victor.stinner@gmail.com</a>> wrote:<br>
>Â Â Â > We are using Mailman 3 for the new buildbot-status mailing list and it<br>
>Â Â Â > works well:<br>
>Â Â Â ><br>
>Â Â Â ><br>
>Â Â Â <a href="https://mail.python.org/mm3/archives/list/buildbot-status@python.org/" target="_blank">https://mail.python.org/mm3/<wbr>archives/list/buildbot-status@<wbr>python.org/</a><br>
>Â Â Â ><br>
...<br>
><br>
>Â Â Â My only use of the pipermail archives is to find permanent URLs for<br>
>Â Â Â mails I want to refer people to. My usage goes as follows:<br>
><br>
>Â Â Â 1. Google search for a post.<br>
>Â Â Â 2. Paste in the URL to an email.<br>
><br>
>Â Â Â Or, if I have the post already (usually in my email client).<br>
><br>
>Â Â Â 1. Check the date and subject of the post.<br>
>Â Â Â 2. Go to the pipermail article by month, and scan the list for the<br>
>Â Â Â subject and author.<br>
>Â Â Â 3. Click on the link, check it's the right email, copy the URL.<br>
>Â Â Â 4. Paste it into my email.<br>
><br>
>Â Â Â I don't use the archives for reading. If the above two usages are<br>
>Â Â Â still available, I don't care. But in particular, the fact that<br>
>Â Â Â individual posts are searchable from Google is important to me.<br>
<br>
<br>
A Google search narrowed with "site:<a href="http://mail.python.org" target="_blank">mail.python.org</a>" and perhaps<br>
"<a href="javascript:;" onclick="_e(event, 'cvml', 'inurl:listname@python.org')">inurl:listname@python.org</a>" works for HyperKitty archives as well. Also,<br>
the archive itself has a "search this list" box.</blockquote><div><br></div><div>Gmail also supports "list:<a href="http://python.org">python.org</a>" now.</div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
...> The complexity of this process is also very wastefully frustrating to<br>
> me. (Maybe it's in the next month's message tree? No fulltext search? No<br>
> way to even do an inurl: search because of the URIs?!)<br>
<br>
<br>
I don't see these issues. There is a full text search box on the archive<br>
page and I don't see the problem with Google inurl:</blockquote><div><br></div><div>This URL style would work with inurl:<br></div><div><br></div><div>inurl:x.TLD/THREADID/msgid </div><div><br></div><div>These can't span across the year-month or otherwise catch other threads in the result set:</div><div><br></div><div>inurl:<a href="http://mail.python.org/pipermail/astropy/2017-September/0001.html">mail.python.org/pipermail/astropy/2017-September/0001.html</a></div><div>inurl:<a href="http://mail.python.org/pipermail/astropy/2018-January/0002.html">mail.python.org/pipermail/astropy/2018-January/0002.html</a><br></div><div> </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
> Isn't there a way to append a permalink to the relayed message footers?<br>
> Google Groups and Github do this and it saves a lot of time.<br>
<br>
<br>
As you note below, there is an Archived-At: header. I have just<br>
submitted an RFE at <<a href="https://gitlab.com/mailman/mailman/issues/432" target="_blank">https://gitlab.com/mailman/<wbr>mailman/issues/432</a>> to<br>
enable placing this in the message header/footer.<br>
<br>
<br>
> [Re-searches for things]<br>
><br>
> Mailman3 adds an RFC 5064 "Archived-At" header with a link that some<br>
> clients provide the ability to open in a normal human browser:<br>
><br>
> <a href="http://dustymabe.com/2016/01/10/archived-at-email-header-from-mailman-3-lists/" target="_blank">http://dustymabe.com/2016/01/<wbr>10/archived-at-email-header-<wbr>from-mailman-3-lists/</a><br>
><br>
> I often click the "view it on Github" link in GitHub issue emails. (It's<br>
> after the '--' email signature delimiter, so it doesn't take up so much<br>
> room).<br>
> Â <br>
> "[feature] Add permalink to mail message to the footer when delivering<br>
> email"<br>
> <a href="https://gitlab.com/mailman/hyperkitty/issues/27" target="_blank">https://gitlab.com/mailman/<wbr>hyperkitty/issues/27</a><br>
<br>
<br>
This needs to be in Mailman Core, not HyperKitty. As I note above, I<br>
filed an RFE with core and also referenced it in the HyperKitty issue</blockquote><div><br></div><div>Thanks!</div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
>Â Â Â Finally, how would a transition be handled? I assume the old archives<br>
>Â Â Â would be retained, so would there be a cut-off date and people would<br>
>Â Â Â have to know to use the old or new archives based on the date of the<br>
>Â Â Â message?<br>
><br>
><br>
> Could an HTTP redirect help with directing users to the new or old archives?<br>
<br>
<br>
What we did when migrating security-sig is we migrated the archive but<br>
kept the old one and added this message and link to the old archive page.<br>
<br>
"This list has been migrated to Mailman 3. This archive is not being<br>
updated. Here is the new archive including these old posts."<br>
<br>
We also redirected<br>
<<a href="https://mail.python.org/mailman/listinfo/security-sig" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/security-sig</a>> to<br>
<<a href="https://mail.python.org/mm3/mailman3/lists/security-sig.python.org/" target="_blank">https://mail.python.org/mm3/<wbr>mailman3/lists/security-sig.<wbr>python.org/</a>>.<br>
<br>
We purposely didn't redirect the old archive so that saved URLs would<br>
still work.<br>
<br>
We did the same things for security-announce and clearly can do the same<br>
for future migrations.</blockquote><div><br></div><div>Great.</div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Finally note that Mailman 3 supports archivers other than HyperKitty.<br>
For example, one can configure a list to archive at<br>
<a href="http://www.mail-archive.com" target="_blank">www.mail-archive.com</a>, in such a way that the Archived-At: permalink<br>
points to the message at <a href="http://www.mail-archive.com" target="_blank">www.mail-archive.com</a>.</blockquote><div><br></div><div>Someday someone will have the time to implement this in e.g. posterious or hyperkitty or from a complete mbox:</div><div><a href="https://github.com/westurner/wiki/wiki/ideas#open-source-mailing-list-extractor">https://github.com/westurner/wiki/wiki/ideas#open-source-mailing-list-extractor</a><br></div><div><br></div><div>Thanks again!</div><div>Â </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Mark Sapiro <<a href="javascript:;" onclick="_e(event, 'cvml', 'mark@msapiro.net')">mark@msapiro.net</a>>Â Â Â Â The highway is for gamblers,<br>
San Francisco Bay Area, California  better use your sense - B. Dylan<br>
</blockquote>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4