public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jean Delvare <khali@linux-fr.org>
Cc: LM Sensors <lm-sensors@lm-sensors.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Mark M. Hoffman" <mhoffman@lightlink.com>
Subject: Re: [lm-sensors] Hardware monitoring subsystem maintainer position is	open
Date: Tue, 10 Apr 2007 17:40:54 +0200	[thread overview]
Message-ID: <461BB006.9020308@hhs.nl> (raw)
In-Reply-To: <20070410150227.1bac05b5@hyperion.delvare>

Jean Delvare wrote:
> Hi all,
> 
> I am resigning from my role as hardware monitoring subsystem
> (drivers/hwmon) maintainer. This is too much work for me, I do not have
> the necessary bandwidth to review all the incoming patches, in
> particular new drivers, in a timely manner. Patch authors have been
> complaining about this repeatedly. This is no fun for them, and even
> less for me, so I'd rather let someone else with more spare time take
> care of it. If there are volunteers, this is the right time to speak up.
> 

I'm sorry to hear this and I can't help but think that my, erm, rant* yesterday 
is somehow involved in you making this decision. This was in no way my 
intention. My intention was to try and make you change how you handle these 
things, my intention was to make you less of a perfectionist and to distribute 
the work more, you cannot do everything yourself. I think that if you could 
change that you would be able to cope with the load better.

I think you're experience / knowledge when it comes to hwmon stuff is very 
valuable and if you leave / quit doing hwmon stuff this would be a big loose. I 
also believe that with a looser management style, you could seriously reduce 
your workload coming from being the hwmon maintainer and at the same time get a 
better / faster flow of patches.

But alas, I'm afraid I cannot change your mind, so that brings us to the 
question who will pickup the task. I've considered volunteering myself, but I'm 
to inexperienced when it comes to kernel stuff and lm-sensors for me is kinda a 
side project. I sink most of my spare time into Fedora where I maintain circa 
120 packages, which really means I have little time left for lm-sensors (to be 
clear the average package maintainer maintains between 30 - 50 packages).

However I do hereby promise to help the new "Jean" in anyway I can, and 
although not many know me very well here I think I can safely say I can help in 
many ways. I'm a (very) experienced c-programmer specialised in lowlevel code, 
embedded (linux) systems, etc. and I have a bachelor in electronics. So 
who-ever becomes the new "Jean" don't hesitate to ask for help, the worst thing 
that can happen is that I say no :)

Jean, thanks for all your hard work the past years!

Regards,

Hans

* for those not on the lmsensors list I am one of the complaining patch authors


  parent reply	other threads:[~2007-04-10 15:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070410150227.1bac05b5@hyperion.delvare>
2007-04-10 13:56 ` [lm-sensors] Hardware monitoring subsystem maintainer position is open David Hubbard
2007-04-10 15:40 ` Hans de Goede [this message]
2007-04-10 15:46   ` David Hubbard
2007-04-10 22:22     ` Rudolf Marek
2007-04-10 23:02       ` David Hubbard
2007-04-11  9:24       ` Hans de Goede
2007-04-11 15:08         ` Juerg Haefliger
     [not found]         ` <461dca480d7ec@wp.pl>
2007-04-12  7:27           ` [lm-sensors] Hardware monitoring subsystem maintainer positionis open Hans de Goede
2007-04-15  2:07             ` Dmitry Torokhov
2007-04-11  9:49   ` Hardware monitoring subsystem maintainer position is open Jean Delvare
2007-04-11 10:06     ` [lm-sensors] " David Hubbard
2007-04-11 14:49     ` Gene Heskett
2007-04-15 15:03 ` [lm-sensors] " Mark M. Hoffman
2007-04-15 17:54   ` Juerg Haefliger
2007-04-15 18:16   ` Rudolf Marek
2007-04-17  8:45   ` Jean Delvare

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=461BB006.9020308@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=mhoffman@lightlink.com \
    /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