Hi Zeljko,

It is certainly possible to set those up as I described before.  In fact we
have a few of them already, but not project-wide. Perhaps you can bring this
discussion to Don's telecon and get a decision regarding using this more
extensively.

Jeff

> From: Zeljko Ivezic <[EMAIL PROTECTED]>
> Organization: University of Washington
> Reply-To: [EMAIL PROTECTED], LSST Data Management
> <[email protected]>
> Date: Tue, 26 Sep 2006 14:32:42 -0700
> To: LSST Data Management <[email protected]>
> Subject: Re: [LSST-data] Postings to list servers
> 
> Jeffrey P Kantor wrote:
>> Hi Zeljko,
>> 
>> Actually you can set mailman (the tool we use for lsst lists) lists to be
>> "private", that is to require someone to be subscribed to see the list
>> contents and you have enter your email and password.  This is a
>> configuration setting.  Then the administrator simply manages who is allowed
>> to subscribe.  I believe (after some initial confusion on the list manager's
>> part) this is how the lsst-scmgt list is configured.
>> 
>> You can also set the entire list so that it is hidden from the overall list
>> directory page, so you have to know the name of the list to find it.
>> 
>> Of course, for lsst-data, we WANT the list to be readable, so it is not set
>> that way.  But this can be done on an individual list basis, so if you
>> wanted lsst-sc that way for example, it can be set with those parameters.
> 
> Thanks! I think you already explained that once to me.
> 
> My problem is more philosophical: people tend not to send
> postings to email lists because they are so public. The
> volume of email related to lsst that is send to private
> email addresses in everyone's mailbox can easily prove
> this assertion. There may be other reasons too, but it
> is my impression that the public nature of lsst-* lists
> is a significant factor.
> 
> A large fraction of email conversation in the project
> that doesn't get posted to lsst-* lists is very bad for
> at least two important reasons:
> 
> - that conversation is not archived
> - its distribution is limited only to those on a sender's
>  private list
> 
> Both of these are likely to have a significant negative impact
> on the project.
> 
> I believe that project-wide, but invisible to the world, lists
> would help. And repeated insistence by the project management
> that private email exchanges are not good for the project.
> Even when their content is trivial.  We must have lively
> project wide communication that is not accessible to google
> robots. Even after google people join us.
> 
> 
>   Cheers,
> 
>   Zeljko
> 
> 
> 
> _______________________________________________
> LSST-data mailing list
> [email protected]
> http://www.lsstmail.org/mailman/listinfo/lsst-data
> 

_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data

Reply via email to