opencog-dev team mailing list archive

["David Hart" <hart@xxxxxxxxxxxx>]

Joining launchpad-beta-testers will allow any opencog-dev member to access
the Mailman functions (i.e. to join the opencog-dev Mailman list), but it
also redirects all of a user's sessions to the Launchpad beta test site (for
all beta code); I didn't want to opt-in everyone to be full beta testers (by
requesting that opencog-dev become a member of launchpad-beta-testers) since
we're only a few days away from the release of the beta Mailman/Launchpad
integration code.

Membership of opencog-dev in the mailing-list-beta-testers group is what
allowed the opencog-dev Mailman list to be created, and individual
membership in launchpad-beta-testers is what allows users to join the list.
The user membership in mailing-list-beta-testers inherited from the
opencog-dev group membership is just an inconsequential side-effect. Aren't
these  Zopey/Pythonic OOP effects fun? ;-)

-dave

On Tue, Mar 25, 2008 at 2:34 AM, Cassio Pennachin <cassio@xxxxxxxxxxxxx>
wrote:

> David,
>
> I see I'm an "indirect" member of mailing-list-beta-testers.  Is this
> good enough or do I need to be a direct member?
>
> Cassio
>
> On Mar 24, 2008, at 12:53 AM, David Hart wrote:
> > Hi All,
> >
> > Sorry for the delay setting up the opencog-dev list. I'm told that
> > the list
> > will function for all users later this week when Launchpad 1.2.3 is
> > released. I was unaware of the requirement that opencog-dev team
> > members
> > join launchpad-beta-testers to use the list (I thought that
> > membership in
> > mailing-list-beta-testers inherited from opencog-dev's membership
> > would
> > accomplish this), an interesting (if confusing in this case)
> > demonstration
> > of the integration of Mailman with Launchpad's permission
> > infrastructure.
> >
> > -dave
>
> --
> Cassio Pennachin
> CEO, Vetta Labs
> www.vettalabs.com -- +55(31)3421-6933
>
>
>
>