Proposition to simplify VideoLAN mailing-lists

[Christophe Massiot]

Dear friends,

I believe that there are too many mailing-lists in the VideoLAN 
project, and it is confusing for both our users and developers. In 
particular, for our library the distinction between "user" 
mailing-lists and "devel" mailing-lists is confusing, and with the 
exception of CVS commits, traffic is quite often off-topic.

Since the purpose of the libdvdcss and libdvbpsi libraries is to 
serve other programs (such as VLC, VLS, ogle...), users tend to 
report bugs to VLC, VLS or ogle's mailing lists. Moreover, the 
traffic in these lib* mailing-lists is very low, and I don't see the 
point in systematically splitting it in two.

Therefore, I suggest that we do the same as most open source 
libraries (liba52, libmpeg2, mad...), and keep a unique mailing-list 
for each project, that is :
- merge libdvdcss and libdvdcss-devel, and call the resulting ml libdvdcss ;
- merge libdvbpsi and libdvbpsi-devel, and call the resulting ml libdvbpsi ;
- merge libdvdplay and libdvdplay-devel, and call the resulting ml 
libdvdplay (the libdvdplay hasn't been released to the public yet).

Any objection ?

-- 
Christophe Massiot.
-- 
This is the libdvdcss-devel mailing-list, see http://www.videolan.org/libdvdcss/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>