[sakai-pmc] [sakai-forum] Re: What do we think of this so far?

[Neal Caidin]

Also we have not been updating Mailman so we could be significantly behind
in versions, I suspect. So yeah, the maintenance and cost savings.
Maintenance is probably the bigger deal of the two.



On Tue, Jan 6, 2015 at 10:18 AM, Matthew Jones <matthew at longsight.com>
wrote:

> The monthly costs of the server that host mailman and Jenkins together was
> something like $150 a month. We really don't need that Jenkins instance
> anymore because we have a Jenkins running on AWS now with the new nightlies.
>
> We could put mailman on an EC2 (either the current machine or a micro) and
> shut down this existing machine to save the foundation money but someone
> would have to set it up with our custom hacks and configuration which would
> probably take at least a few hours.
>
> But I think we also figured Google groups provided more benefits even over
> the cost savings, such as better archives of the messages, searching and a
> forum style web view.
>
> On Tue, Jan 6, 2015 at 10:10 AM, Noah Botimer <botimer at umich.edu> wrote:
>
>> So, uhh... Is Mailman a problem? I mean: what is the total time + dollar
>> cost annually?
>>
>> I don't mind consolidation and outsourcing but it kind of feels like
>> fiddling unless there are other costs and issues unknown to me.
>>
>> I suppose we're moving other core workflow/infrastructure bits around
>> now, so it's as good a time as any. This isn't an objection -- just
>> wondering why the new mouse trap's better, since it might shape the
>> transition (à la grand unification).
>>
>> Thanks,
>> -Noah
>>
>> On Jan 6, 2015, at 9:00 AM, Neal Caidin wrote:
>>
>> Who do I ask about access to the Collab server? At one time I had access
>> but now I cannot get in.
>>
>> I get the message "Permission denied (publickey,gssapi-with-mic)"
>>
>>
>>
>> On Tue, Jan 6, 2015 at 8:52 AM, John A. Lewis - Unicon <jlewis at unicon.net
>> > wrote:
>>
>>> There is an API for importing individual messages. Maybe someone wants
>>> to look at scripting a migration? On a quick search I didn't find much else
>>> that is ready to use.
>>>
>>>
>>> https://developers.google.com/admin-sdk/groups-migration/v1/guides/manage-email-migrations
>>>
>>> On Tue, Jan 6, 2015 at 8:41 AM, Neal Caidin <neal.caidin at apereo.org>
>>> wrote:
>>>
>>>> Yeah, I think we should. That's one of the things I need to investigate
>>>> (or use help in investigating). Maybe we can move the archives to a simple
>>>> web server?
>>>>
>>>>
>>>> On Tue, Jan 6, 2015 at 8:34 AM, Seth Theriault <slt at columbia.edu>
>>>> wrote:
>>>>
>>>>> On Tue, Jan 6, 2015 at 8:17 AM, Neal Caidin <neal.caidin at apereo.org>
>>>>> wrote:
>>>>> > FYI, I would like to decommission all Mailman mailing lists this
>>>>> year in
>>>>> > favor of other options. I was leaning towards using Apereo Google
>>>>> Groups as
>>>>> > the most viable option.
>>>>>
>>>>> Do we plan to maintain the Mailman list archives in a specific manner?
>>>>>
>>>>> Seth
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>>
>>>
>> _______________________________________________
>> sakai-pmc mailing list
>> sakai-pmc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>
>>
>>
>> _______________________________________________
>> 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/20150106/be4a4fc3/attachment.html