Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "Michael Renzmann" <mrenzmann@madwifi-project.org>
Cc: linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org,
	ath9k-devel@lists.ath9k.org
Subject: Re: Searching new home for ath[59]k-devel mailing lists
Date: Fri, 13 Jan 2017 12:28:34 +0200	[thread overview]
Message-ID: <87y3yfi78t.fsf@purkki.adurom.net> (raw)
In-Reply-To: <49328.217.24.3.26.1483895726.squirrel@webmail.madwifi-project.org> (Michael Renzmann's message of "Sun, 8 Jan 2017 18:15:26 +0100 (CET)")

"Michael Renzmann" <mrenzmann@madwifi-project.org> writes:

> Out of history, the ath5k-devel and ath9k-devel mailing lists have been
> and still are hosted on the mailing list server of the MadWifi project. I
> intend to shut the server down, and thus I'm searching a new loving home
> for the lists.
>
> Besides a new home the lists also need some attention - both would receive
> a fair amount of spam, and thus they need someone who takes care of some
> kind of moderating posts and/or filtering spam.
>
> To be honest, I've not been following things at all for many months. From
> what I can tell it seems that ath5k-devel is pretty quiet. ath9k-devel,
> however, still sees a fair amount of communication; but I didn't look at
> how much of that traffic actually took place here on linux-wireless, just
> CC'ing ath9k-devel.
> This is to say, if there is a broad agreement that one of the lists or
> both of them are no longer required, I'm fine with just closing them in an
> ordered fashion.

I really don't see any need for ath5k-devel, according to git log there
has been five patches for ath5k during the past year.

ath9k is of course a lot more active, 99 patches over the last year. But
still I get the feeling that we don't really need an ath9k specific
mailing list, discussion via linux-wireless should work. And if there
ever comes up a demand to have a dedicated list for ath9k we can then
try find a new one, for example from infradead.org.

So feel free to close both of the lists and thanks for the heads up. Are
you planning to update the MAINTAINERS file or should I?

-- 
Kalle Valo

  reply	other threads:[~2017-01-13 10:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 17:15 Searching new home for ath[59]k-devel mailing lists Michael Renzmann
2017-01-13 10:28 ` Kalle Valo [this message]
2017-01-14  6:48   ` Michael Renzmann
2017-01-27 12:00     ` Kalle Valo
2017-01-27 12:37       ` Valo, Kalle
2017-01-30 18:40       ` Michael Renzmann
     [not found]   ` <49460.217.24.3.26.1484376491.squirrel@webmail.madwifi-project.org>
2017-01-16 12:15     ` Michael Renzmann
2017-01-16 13:49       ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3yfi78t.fsf@purkki.adurom.net \
    --to=kvalo@codeaurora.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mrenzmann@madwifi-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox