[sakai-pmc] Strategies to deal with email list archives

[Matthew Jones]

I'm not volunteering to write anything, and usually when I want to search
the archives I'll go to nabble or gmane to do the search. The only reason I
ever used the archives really was to be able to link others to emails that
had duplicate answers in them. So just something static out there that we
could rely on for permanence (in-case one of those mirrors was unavailable)
is all I'd personally be interested in. Unless someone did want to write
something anyway.

The container name sounds okay, but maybe just make it mailman? And then
you'd get a CNAME for the domain like
archive.collab.sakaiproject.org/mailman/<archives>. Or if we wanted them on
https it would have to be under the nightly domain (
collab.nightly.sakaiproject.org/archives)

On Thu, Jan 15, 2015 at 8:16 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

> Hi Sakai PMC,
>
> We have a couple of options for dealing with keeping the old Mailman (aka
> Collab server) archives as we move our lists to Apereo Google Groups.
>
> 1) AWS S3 storage. I already did a small proof of concept of this with
> January archives of Teaching and Learning.
>
>
> https://s3-us-west-2.amazonaws.com/apereo.sakai.collab.archives/2015-January/index.html
>
> 2) We could also look at importing all the old messages into Google
> Groups itself. There is an API for it. We would just need to get someone to
> script this and run it. John Lewis has agreed to help facilitate some
> testing if someone was interested in pursuing it.
> https://developers.google.com/admin-sdk/groups-migration/
>
> AFAIK, money wise both options are cheap/free (S3 cheap/ Google groups I
> presume is free). Using option 1 is the easier of the two to set up. Option
> 2 seems like it might be simpler for people interested in searching our
> archives with one place to go.
>
> Are there any volunteers for doing scripting? What do you think of the two
> options? Any other suggestions?
>
> Thanks!
> Neal
>
> P.S. If we go with option 1, and if it matters, we do have control over
> the "container" name and I could use sakai.collab.archives instead of
> apereo.sakai.collab.archives, etc. There are some naming restrictions with
> S3 (lower case, no spaces, etc.).
>
>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20150115/901b9d23/attachment.html