[Swift-devel] maling lists

[Mihael Hategan]

On Thu, 2008-06-05 at 12:32 -0500, Michael Wilde wrote:
> It sounds good to me.
> 
> Would it be better and feasible though to maintain just one set of list 
> memberships, and have the master lists echo to the other set for 
> archival purposes?

If you want @ci to be primary, then no. It is required for all
committers to be subscribed to the @globus mailing lists.

So we either keep both in these conditions or move entirely to @globus.

> 
> It seems like we have much vested in maintaining svn and bugzilla using 
> the current infrastructure, but the email lists seem a bit easier to 
> change. And if the CI lists can remain the master, is it OK just to 
> forward traffic to the dev.globus lists?
> 
> If the dev.globus lists need to be fully populated with members to meet 
> dev.globus requirements, then can we transition to using those as the 
> sole lists, with minimal impact on current list members?
> 
> - Mike
> 
> 
> 
> On 6/5/08 12:22 PM, Mihael Hategan wrote:
> > It seems like one requirement is to have all committers subscribed to
> > the @globus.org mailing lists.
> > 
> > While @ci will continue to be our primary mailing lists, in order to
> > meet the requirements, I'll do the following:
> > 
> > - move everybody from swift-commit at ci to swift-commit at globus and make
> > swift-commit at ci forward to swift-commit at globus. This is so that we don't
> > get double posts, but still have the infrastructure primarily based @ci.
> > 
> > - subscribe all committers to the other @globus mailing lists. We'll
> > encourage users to use the @ci mailing lists, and discussions initiated
> > on @globus should be manually moved to @ci.
> > 
> > Objections?
> > 
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel