[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposal: Debian Science mailing lists



On Wed, 2011-06-15 at 08:33 -0400, Manjusha Joshi wrote:
> On Tue, Jun 14, 2011 at 1:13 PM, Brett Viren <bv@bnl.gov> wrote:
>         Sylvestre Ledru <sylvestre@debian.org> writes:
>         
>         > == Proposal ==
>         >
>         > I would like to propose the following:
>         > * move all packaging related discussions to
>         > debian-science-maintainers@lists.alioth.debian.org
>         > * use debian-science@lists.debian.org only for user oriented
>         discussions
>         > * make sure that all the commit mails are sent on
>         > debian-science-maintainers-commits@lists.alioth.debian.org
>         >
> Benefit is we also get updates about packages and that is really
> useful for us. 
> As Linux user cannot remain only user, need to do system admin level
> work also for scientific packages.
> Second thing is,  after making 2 separate list will there be increase
> in the user level queries? At present there are hardly user related
> queries.
> 


In practice I'm inclined to disagree with the proposal.  That is, in one
sense it arguably makes sense in principle to keep packing discussions
separate from user discussions.  But I agree with Manjusha that

a) it could be useful to have the user's perspective on packaging
questions

b) users could potential find it useful to hear what we're up to and
what decisions we're making on packages. They will be affected by those
decisions.

c) I haven't noticed that many user-level discussions anyway.  What
problem are we trying to solve here?  Have user discussions been impeded
by packaging discussions? Is it the intention of the proposal to
encourage more user discussion by shifting out all packaging discussion?

For myself personally, I tend to find it easier to have just the one
list to have to think about.  Although it's easy enough to set up
another email filter just as I already have for debian-science.


Drew




Reply to: