> Just so I have this right, the as-yet-unspoken implication in this > suggestion is that nearly 4,000 people subscribe to a new list, update > any email rules they may have set up, etc. In addition, we fragment > the development mailing list archive into a "2005-2008" archive and a > "2008-present" archive. As such, we also chop any threads that may be > in progress during the move, hoping they'll continue without incident > on the new list. And that's not considering the hassle of trying to > actually follow those threads later, given that it'd span two separate > archives. > > Interesting. So now we're considering asking over 10,000 people to > subscribe to up to two new mailing lists, just to continue discussions > they have happily today. And again, we have the whole multiple-archive > problem and hacked-up threads. More to the point, neither of those > would solve the problem, since the issue here isn't that > "django-users" isn't descriptive enough; it's that "django-developers" > is also descriptive enough. If you're registering new names, why not > register a new name for the mailing list actually experiencing the > problem? > > Now, I'm admit: I do realize that Django 1.0 involves some necessary > backwards-incompatibilities. But should mailing list subscriptions > really be added to that list? Troubling nearly 15,000 people to change > 3-year-old habits because a few people are annoyed by off-topic emails > every other day (or so) just doesn't seem worth it to me.
I just thought I'd drop a note here - Google Groups allow existing groups to be renamed, further more groups emails can stay as they were or changed as well to a new one. All this retaining the history, and subscribers. So it would merely make it an issue to people who are sending emails initially. To me thats not a big one at all. So the fact that you say we have to force nearly 15000 people to change is a rather void argument. I'm pretty sure the people who use django-users mainly do it through the web interface - so to them it would only mean the changing of a web address. Everybodies subscriptions would stay in tact, they would just have to send to a slightly different web address. There are going to be some initial confusions, yes, but considering it all I think it'll do more good, than bad. > As always, one man's opinion. Wise words, which also apply to me. Mike. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
