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

[Noah Botimer]

Oh, certainly. I mean no disrespect to the people and groups mentioned. I only gave some ballpark ideas to start some community self-examination; no unilateral action implied.

The basis of my suggestion was that a large portion of messages to the grouped lists were cross-posts of the same announcements. I have no agenda other than providing facilitation and clarity to accompany the disruption that would come from moving the lists. The only real costs of extra lists are fragmentation and duplication, to be weighed against concision and cohesion.

Thanks,
-Noah

On Jan 7, 2015, at 9:25 AM, Neal Caidin wrote:

> Fortunately, Anthony W. has done much of this ground work and already consolidated and removed many lists as compared with a year or so ago. I'll go back and look at the spreadsheet he created and make a plan based on where we are now and share the plan. 
> 
> It will involve reaching out to the existing lists so we don't have too much of a heavy hand in making the changes. I'll post the plan to the PMC though after that we can just do it (primarily Ian and myself it sounds like). :-)
> 
> Cheers,
> Neal
> 
> 
> On Wed, Jan 7, 2015 at 5:13 AM, Ian Dolphin <ian.dolphin at apereo.org> wrote:
> It would strike me that it is appropriate to raise the potential futures
> of many of the lists being discussed with the lists themselves - or at
> least to provide the opportunity for voices from those lists to be heard
> by directly approaching them. The right people to decide whether a
> portfolio list is still required are members of the portfolio list -
> likewise Ja-Sakai, and at least some of the others I've seen mentioned.
> 
> If it would be helpful for the Foundation (AKA, in this case, Neal and
> myself) to help with consultation and any transition, I'm sure we could
> work something out.
> 
> Best
> 
> Ian D
> > Jean-Francois Leveque <mailto:jean-francois.leveque at upmc.fr>
> > 7 January 2015 09:55
> > That consolidation doesn't sound good to me.
> >
> > Mixing i18n, a11y, docs and QA seems wrong.
> >
> > Is portfolio still needed, when OSP is not maintained and the new
> > portfolio project is independent?
> > _______________________________________________
> > sakai-pmc mailing list
> > sakai-pmc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> > Steve Swinsburg <mailto:steve.swinsburg at gmail.com>
> > 6 January 2015 20:22
> > Yep, that consolidation sounds good too.
> >
> > I still have the question as to why the google group would exist under
> > the apereo.org <http://apereo.org> umbrella and not just a main google
> > group. What do we achieve? Do we lose anything in terms of visibility
> > and discoverability?
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > sakai-pmc mailing list
> > sakai-pmc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> > Noah Botimer <mailto:botimer at umich.edu>
> > 6 January 2015 16:04
> > Sold. Now what about the mapping? It seems clear that activity is
> > somewhat lower and less diverse than in times past. Even though many
> > have been consolidated already, here is a further strawman:
> >
> > gradebook2-dev, evaluation, samigo-team, sakai-mobile -> sakai-dev
> >
> > infrastructure -> sakai-core-team
> >
> > portfolio -> pedagogy
> >
> > i18n, accessibility, sakai-docs -> sakai-qa
> >
> > (and maybe something with eurosakai, ja-sakai, sakai-france, sakai-au)
> >
> > Thanks,
> > -Noah
> >
> >
> >
> > _______________________________________________
> > sakai-pmc mailing list
> > sakai-pmc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> > Matthew Jones <mailto:matthew at longsight.com>
> > 6 January 2015 15:18
> > 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.
> >
> >
> > _______________________________________________
> > sakai-pmc mailing list
> > sakai-pmc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
> > Noah Botimer <mailto:botimer at umich.edu>
> > 6 January 2015 15:10
> > 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
> >
> >
> >
> > _______________________________________________
> > 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/20150107/164836b0/attachment.html