[sakai-pmc] [DG: Open Forum] Plan - from Mailman to Google groups

[Matthew Jones]

Yeah, I think it could be possible to get #1 to work, but since people
probably won't be auto-subscribed to the new lists as they move around the
return address would be apereo, I think it would be better to move to
apereo. It should be possible to have a short term auto-responder (few
weeks, month?) for any messages sent to @collab.sakaiproject.org to just
bounce with some informational message to go read some new documentation or
go to some new groups.

For #2 I think we could set this up on S3 without much work to match the
URL's as they previously existed. We just wouldn't want to do it until it's
switched over. But yeah, not a big deal to do it.

On Mon, Feb 2, 2015 at 10:48 AM, Neal Caidin <neal.caidin at apereo.org> wrote:

>
> Hi Seth,
>
> I hadn't thought about those options.
>
> I think the questions are
> Should we do it? Who will do it?
>
> Since I haven't given these options any thought, off the top of my head:
>
> 1) Pros - will catch emails sent to old email addresses. Easier
> transition.  Cons - might still be confusing since some lists will merge.
> Shows lack of awareness of users and may make it less likely they will
> understand what happened to the lists and how to use them effectively.
> Questions - What happens when they get a response? Comes from the new list
> address?   Will sufficient communication about the move and the standards
> (e.g. using [i18n] for subject line on international posts) be sufficient?
> Could masking users from the change cause more confusion than the
> convenience provided?
>
>
> 2) I don't see any downside to this if someone is willing to do it. John
> Lewis offered to help suck the old messages into the Google Groups as
> another alternative, but would need someone to write the scripts.  All
> these ideas seem good and I defer to the "doocracy". If someone wants to do
> it, that would be cool. IMHO it should not hold up the move. And I presume
> if we have the static information, we could always implement one or both of
> these ideas at a later date (but seems like if we don't do it upfront,
> interest will probably be lost).
>
>
>
> Thanks,
> Neal
>
>
>   Seth Theriault <slt at columbia.edu>
>  February 2, 2015 at 10:35 AM
> Hello,
>
> [Dropping everyone except the PMC]
>
> I have two questions for clarification (and perhaps repetition due to
> my ignorance):
>
> 1) Will a collab.sakaiproject.org MX be preserved so that mail to old
> lists will automagically go to the new lists?
>
> 2) Will the static archives be accessbile via the old collab URLs?
>
> Seth
>
>
>   Neal Caidin <neal.caidin at apereo.org>
>  February 2, 2015 at 9:14 AM
> [all 21 Sakai lists that exist currently]
>
> *Proposal*
> Movement of Sakai lists to Apereo Google Groups infrastructure.
>
> *Decision Making*
> All opinions are welcome and encouraged. A material objection raised by a
> Sakai PMC member will block this proposal.  Silence equals consent. Monday,
> February 9, 2015 is the cutoff date for any objections.
>
> *Plan*
>
>    - Communicate to lists to being merged or moved. Provide a date for
>    when move is happening.
>    - Create new Apereo Google groups and populate with members from
>    Mailman (collab lists). When combining multiple lists, populate with
>    members from all of the lists into the one list.
>    - Start using new Google group, turn off corresponding mailman
>    list(s).
>    - Move old list archives to static web space.
>    - Repeat as needed for all lists until done.
>
>
> *Proposed set of Apereo Google Groups*
> sakai-openforum at apereo.org
> sakai-user at apereo.org
> sakai-production at apereo.org
>  sakai-core-team at apereo.org
> sakai-dev at apereo.org
> sakai-docs at apereo.org
> sakai-pmc at apereo.org
> sakai-qa at apereo.org
> sakai-spanish at apereo.org
> portfolio at apereo.org (no longer a sakai-specific list)
>
> *Consolidating Lists*
> * pedagogy and sakai-user merging into sakai-user at apereo.org
> * i18n (internationlization/localization) and a11y (accessibility) merging
> into sakai-dev. Convention for users to add [i18n] and [a11y] in subject
> line for filtering.
> * evaluation and gradebook2-dev and samigo and sakai-mobile merging into
> sakai-dev
> * infrastructure merging into sakai-core-team
>  * sakai-au - not being migrated.
> * sakai-france - not being migrated
> * builds - not being migrated
> * ja-sakai - not being migrated
> * eurosakai - not being migrated. Already have an Apereo Europe google
> group.
> * source - not being migrated. Need to remove post commit hook from SVN.
>
> *Lists not being migrated*
> We will still move the old list archives to a static web presence, even
> for lists not being migrated.
>
> *Timing*
> Will be variable based on lists, and communication with those
> sub-communities. Intent is to get this done in the next couple of months,
> by April/May timeframe for completion. Will start migration of lists during
> February 2015.
>
> Thanks,
> Neal
>
>
>
>
> --
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
>
>
> _______________________________________________
> 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/20150202/88da2fce/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20150202/88da2fce/attachment.jpg