Re: [gentoo-dev] RFC: Disabling some of our Mail Lists
On 04/20/10 22:52, Jeremy Olexa wrote: > Hello, > As suggested in bug 291860, I am heading up an infra cleanup project to > disable/close some mailing lists. Since the list is quite large, I want > to send it out for RFC. Going by archives.gentoo.org stats, the following lists are also inactive, and are all listed as 'Primary Gentoo Mailing Lists' at www.gentoo.org/main/en/lists.xml If there's a reason to keep any of them, perhaps they should be split off to a 'Low-traffic Lists' section, as I can't see them being of much use to most people. gentoo-ppc-dev 2010 - 0 posts 2009 - 4 posts 2008 - 9 posts 2007 - 15 posts gentoo-hppa 2010 - 0 posts 2009 - 0 posts 2008 - 1 post 2007 - 12 posts gentoo-desktop-research 2010 - 0 posts 2009 - 0 posts 2008 - 3 posts 2007 - 12 posts gentoo-admin 2010 - 0 posts 2009 - 8 posts 2008 - 3 posts 2007 - 3 posts gentoo-web-user 2010 - 4 posts 2009 - 0 posts 2008 - 10 posts 2007 - 10 posts gentoo-devrel 2010 - 0 posts 2009 - 1 post 2008 - 2 posts 2007 - 8 posts gentoo-uk 2010 - 0 posts 2009 - 0 posts 2008 - 16 posts 2007 - 6 posts gentoo-au 2010 - 0 posts 2009 - 0 posts 2008 - 28 posts 2007 - 24 posts gentoo-vdr 2010 - 0 posts 2009 - 3 posts 2008 - 8 posts 2007 - 28 posts
[gentoo-dev] RFC: Disabling some of our Mail Lists
Hello, As suggested in bug 291860, I am heading up an infra cleanup project to disable/close some mailing lists. Since the list is quite large, I want to send it out for RFC. A few of the important reasons to disable some of our mail lists are: * Confusing to users because there are so many lists that aren't being used. How should you know which one is active without more research? * More lists means more managing, more spam attempts and infra overhead. I want to emphasize that the lists will be closed for new posts but the archives will remain available. Disabled lists can be re-enabled by filing an infra-bugs request. My suggestions to disable are as follows: gentoo-doc-lt Reason: Only 1 post, late 2008 gentoo-extreme-security Reason: Never was a real project, 1 post. gentoo-doc-id Reason: Only posts have been 2 spam messages. gentoo-forum-translations Reason: 2 posts, 2007. gentoo-translators Reason: 3 posts, all spam. 2008 gentoo-arm Reason: 4 posts total, last 2006. ACKd with team. gentoo-gwn-fr Reason: GWN is not active. gentoo-gwn-pl Reason: GWN is not active. gentoo-dev-lang Reason: 7 posts total, last 2007 gentoo-ia64 Reason: Not active. last 2006 tenshi-announce Reason: Not used, current release is .11, last used for .4 2006 gentoo-scire Reason: Dead, last 2008 tenshi-user Reason: Not used, last 2006 gentoo-media Reason: Besides spam, last used 2006 gentoo-proctors Reason: Not used since 2007. 14 message total. ACKd with team. gentoo-gwn-nl Reason: GWN is not alive. gentoo-doc-hu Reason: Last project commit: 3 years ago, last ML 2007 gentoo-user-kr Reason: Rarely used, last late 2009 with no reply gentoo-doc-nl Reason: last 2007 gentoo-gnustep Reason: Keep but questionable. Probably be closed during next cleanup gentoo-xbox Reason: Dead project gentoo-cygwin Reason: Dead Project, last 2008 gentoo-gwn-de Reason: GWN is not alive. gnap-dev Reason: Dead Project, some life recent but..? www-redesign Reason: Dead Project gentoo-gwn Reason: Dead project gentoo-installer Reason: Dead project gentoo-performance Reason: Not active, recent spam gentoo-osx Reason: Dead project
Re: [gentoo-dev] Gentoo stats server/client @ 2010-04-21
On 04/20/2010 08:44 PM, Sebastian Pipping wrote: Another thing I've been working on is re-shaping the Gentoo code in a way that it's now ready to go upstream, at least from my point of view. I have requested permission to merge it in a few hours ago: Let's see how upstream thinks about it. So that's the news I wanted to share with you. Great, thanks! I've been waiting for your project to become more official for months. :) :)
[gentoo-dev] Gentoo stats server/client @ 2010-04-21
Intro = Some of you may remember that project of mine I worked on for GSOC 2009: collection of information on Gentoo user machine setups. I have been extending Smolt [1] (whose current upstream version collects information on hardware) to fit our interest in the software side of things. News In the past days [2] I have been migrating the server side of Smolt to server-to-server communication. What does that mean? Server-to-server communication -- When a client submits to the Gentoo Smolt Server, the server will extract the part of interest to the common Smolt server (smolts.org) and forward it. As a consequence the needs for space in storage (quite a few SQL tables, use flags per installed package, ..) and increased processing time per submission are no problem to smolts.org anymore. Also we gain more direct access to "our" data from it. Another thing I've been working on is re-shaping the Gentoo code in a way that it's now ready to go upstream, at least from my point of view. I have requested permission to merge it in a few hours ago: Let's see how upstream thinks about it. So that's the news I wanted to share with you. Sebastian [1] https://fedorahosted.org/smolt/ [2] http://git.fedorahosted.org/git/?p=smolt.git;a=shortlog;h=refs/heads/next [3] http://git.goodpoint.de/?p=smolt-gentoo.git;a=shortlog;h=refs/heads/gentoo
