All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] project status and future
Date: Sun, 25 Dec 2005 22:33:46 +0000	[thread overview]
Message-ID: <43AF1E4A.90902@sh.cvut.cz> (raw)

Hello all,

In this holiday time most of us is resting and maybe thinking about the future plans
for a new year. Maybe you want to do something for other people, to help, to support,
simply to create something that will help other people. Well as you will read further
here is your chance ;)

Executive summary is bellow the article ;)

I would like to write here few notes and visions about lm-sensors project. Let me begin
with current state. The project is managed by Jean Delvare, who also maintains the kernel
part of the project. He is doing his job very well and I would like to thank him very much for this effort.

He always tries hard to go through every single byte of C source and find out if code will work in all cases as
expected. Well this review work is very hard and takes a lot of time in magintude of hours just to review
single patch. He also manages the stack of patches that he accepted and  pushes them to kernel. Of course
he must keep everything in sync. As the project leader he must resolve all issues that are in question,
architectural and implemntation specific. This also takes some time to think out.

He is doing his work very well but he is quite overloaded, so please dont blame him for not reviewing your work
for some time or dont expect that you will receive polite answer to some obvious question. He is only a human
and after 8 hours in regular job is quite difficult not to be tired. You might thing there is a weekend too.
Well there is but even developers want to have a social life :), and rememeber there should be some time
that is devoted to actual coding and thoughts about the future plans. This all is hard to do when you dont
have time, because you must solve all other issues - but  not for different project but for this project.

This was just a first part, the patches. We have also different work. We call them "support questions". Maybe
this is why you are on the list. You came with question but you left yourself subscribed.

Handling the user questions is mainly my "job" I'm trying to help them as much I can, sometimes I win, sometimes
not. We have also a support system on our pages but it is quite unfonfortable for our needs. The answers are written
by me or Jean, and it takes tenth of minutes to reply single one.

Time is my enemy too. I'm finishing university -> master thesis, have already part time jobs... So I cant spend
so much time for this project as I want. Things will go better like round end of February but I'm having hard time now.
I had to stop my theora optimization work because I simply dont have more free time left.

Well this is the end of "active" team. We have some hidden staff, that helps us run the list and website.
I would like to thank Philip Edelbrock and Axel Thimm (iirc) for their efforts.

We have here also past developers of the project and they do help when
they can, but as we all are busy with other stuff and by defintion of past developers lm-sensors is now not
their main project. I would like to thank them for a help too, most notably to Mark Hoffman and Mark Studebaker.

And then we have you and next like 150 of others on the list. Well I know that some of you is trying to help, when
it comes to some work you preiously did. Yeah it is good, but as you can see it is simply not enough.

We have some visions and plans for a future but we cant turn them into reality because we are burried with "must do"
work then will never ever stop to come.

We need your help with our work so we can go for future!

And the future plans that are PITA for now:

1) new support system, - (it died previously and never has been finished)
2) new userspace library - new config file system and all stuff around.
3) wiki like pages, so other people can contribute to sensors know-how -> it should "concentrate" our wisdom
   and wisdom from mailing list.
Pi) configuration file repository - this can hide in wiki as first step.
4) patches that were not included in mainline simply because Jean did not have time to handle them :(
5) and many others ...(multiplexed bus handling, driver cleanup, decode-dimms update... etc etc)
(hope I did not forget something)


Well thats it. If you have some free time and willing to help with someting mentioned here, please reply to
this mail and we can discuss further. I also would like to hear what you wish to change and how we should
change...

Executive summary:

Please join us and help to maintain/create even better project!

We need help with:
1) with this new projects
2) with the support
3) With the reviews

Thank you all for staying with us on ML.

Regards
Rudolf

PS: sorry for the long email and my english, this was written just with one and half pass and it came directly from
my mind.


             reply	other threads:[~2005-12-25 22:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-25 22:33 Rudolf Marek [this message]
2005-12-27 10:52 ` [lm-sensors] project status and future Michael Renzmann
2005-12-28 10:09 ` Volker Kuhlmann
2005-12-28 19:07 ` Philip Edelbrock
2005-12-28 21:32 ` Henrique de Moraes Holschuh
2005-12-29  7:33 ` Michael Renzmann
2005-12-29 22:33 ` Jean Delvare
2005-12-29 22:49 ` Rudolf Marek
2005-12-29 23:06 ` Philip Edelbrock
2006-01-02 16:41 ` Michael Renzmann
2006-01-02 22:19 ` Rudolf Marek
2006-01-02 22:38 ` Axel Thimm
2006-01-03  7:25 ` Michael Renzmann
2006-01-03 14:05 ` Axel Thimm
2006-01-03 14:45 ` Michael Renzmann
2006-01-06  7:08 ` Jim Cromie
2006-01-06 20:01 ` Rudolf Marek
2006-01-06 21:40 ` Axel Thimm
2006-01-06 21:42 ` Philip Edelbrock
2006-01-06 21:48 ` Axel Thimm
2006-01-07 11:06 ` 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=43AF1E4A.90902@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.