On Thu, Dec 13, 2012 at 1:06 AM, Dave Fisher <dave2w...@comcast.net> wrote: > > On Dec 12, 2012, at 6:55 PM, Rob Weir wrote: > >> If we're going to have all of these wiki account requests via email, >> would it makes sense to create a special admin list (or webmaster >> list) for these and similar requests, and maybe also for general >> website development topics? > > sysadmin requests to a special ML may make sense, but I don't think that the > website development topics belong in that ML. website topics already overlap > into marketing and L10n. >
I could argue it either way. For example, one reason the discussions are spread out over marketing and L10n is because currently there is no clear "center" to website discussions. A new list could become that center. And a volunteer on the marketing list or L10n list is more likely to subscribe to a dedicated website list than to join the dev list, purely due to traffic. But you could also argue that although the website has its own technical discussions at the admin/sysop level, the design and content is a larger project-wide discussion, often touching on marketing and L10n as well. One way of looking at it might be: Suppose we wanted in 2013 to do a real clean up of the website, updating the stagnant NL pages, making a more modern look, applying any new branding, pruning or updating outdated content, etc. Suppose to do this we had a call for website volunteers and needed to get them up to speed on the CMS and related topics. How would we do this? In practice I think the challenge would be getting new volunteers to survive the dev list traffic. Getting volunteers with project-wide interests to subscribe to "yet another list" is relatively easy. Of course, we don't need to decide the larger question now. It would be enough to have an admin list for admin requests across web, wiki, bugzilla, blog, forums, etc. -Rob > Regards, > Dave > >> >> -Rob >
