On Sat, Oct 23, 2010 at 1:24 AM, Arjan van de Ven <[email protected]> wrote: > On 10/22/2010 3:19 PM, Felipe Contreras wrote: >> >> On Fri, Oct 22, 2010 at 9:24 PM, Arjan van de Ven<[email protected]> >> wrote: >>> >>> On 10/22/2010 11:10 AM, Foster, Dawn M wrote: >>>> >>>> I agree that you can't protect users from themselves, but you can put >>>> the decision solely in their hands. If they subscribe to a list and then >>>> forget what it is, this becomes their mistake. If a moderator lets it >>>> through or >>>> if we let people who aren't subscribed post to the list, it takes the >>>> decision >>>> out of the user's hands. I prefer to let each user make their own >>>> decision >>>> and >>>> then be accountable for it. By requiring subscription and email >>>> confirmation, >>>> you can be certain that at some point each user made a conscious >>>> decision >>>> to join the list. >>> >>> btw for the meego-kernel I really want subscriber only. I want people who >>> post patches to get not just the review comments >>> on their code, but also on everyone elses code so that they won't make >>> the >>> same mistakes. I want them to read the announcements >>> that are made there, etc etc. >> >> You can't do that; subscription != membership. >> >> People can subscribe, and disable mail delivery, therefore they would >> not receive other people reviews. >> >> Besides, in order to be baby-sitting newbies, you would be impairing >> people that already know the process and send mail to lkml, CC say >> linux-arm, and meego-kernel. Even if the poster is subscribed, the >> people replying to the mail might not, and a mess would be created. >> Even worst, if the poster is not subscribed, meego-kernel wouldn't >> even receive the original message. >> >> What would happen is that people would not CC meego-kernel. >> >> So meego-kernel would be isolated from the rest of kernel development. > > meego-kernel (heck, MeeGo as project) is NOT for kernel development. > I don't WANT meego-kernel to be CC'd on lkml submissions. Things need to get > hashed out on LKML first. > THEN people who care about meego can ask for a backport. > > MeeGo is a distribution where we integrate things, not where kernel code > gets developed.
Ah, I'm sorry, I thought _collaboration_ was an important part of MeeGo. I will be sure to not CC MeeGo mailing lists when I write mails, even when I know they are related to MeeGo. Because if people from the other mailing lists reply, they would get these annoying messages and the conversation would get messed up because MeeGo can't be bothered to have conversations with non-subscribers nor other mailing lists. -- Felipe Contreras _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
