This project has a lot of email lists [*] -- but I feel we're either missing 1 or 2 lists or we have too many. Given all our lists, it's not clear which one we should use to talk about cross project dev issues and cross project community/policy issues. general@ has perhaps become a catch all list with user, dev, and community issues inter-mixed. Is that what we want? Should we create more lists to break out these topics? Live with the current inter-mingling? Or consolidate some lists?
Nige [*] I may have missed some: general@ security@ private@ common-user@ common-dev@ common-commits@ common-issues@ hdfs-user@ hdfs-dev@ hdfs-commits@ hdfs-issues@ mapreduce-user@ mapreduce-dev@ mapreduce-commits@ mapreduce-issues@
