From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Submitting motherboard-specific support? (w/
Date: Tue, 21 Aug 2007 08:45:10 +0000 [thread overview]
Message-ID: <20070821104510.3cf9518e@hyperion.delvare> (raw)
In-Reply-To: <46C997B4.50509@dolbeau.org>
Hi Hans,
On Mon, 20 Aug 2007 22:44:02 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > Also, storing the configuration files in the wiki is probably the worse
> > thing we could come up with in these conditions, but hopefully we'll
> > have something better shortly after lm-sensors 3.0.1 is released.
>
> Do you have something planned? As you know I've had several students work on a
> motherboard config website without much success, I do think Ivo's
> sensors-detect changes for dmi based autoconf are good (we need to get those
> integrated, plan?). But the website delivered by one of his fellow students is
> less good.
Your students' work was obviously what I was thinking about here.
> I do have a friend who is a php guru who is willing to write a php driven site
> for us if we can provide him with proper specs.
>
> I can start writing a spec for the website as time permits, then discuss it
> here, and once approved ask him to write it (under an OSS license of course).
Writing it is one thing, hosting it is another. Axel, maybe I already
asked, can't remember: can we host a PHP app on lm-sensors.org?
> Another option would be to stay with the wiki, add some special markup comments
> for the dmi strings and write a script to generate a tarbal / "database" for
> the dmi based detect code. For me putting the info in the wiki works well, its
> not like we are getting multiple motherboard configs per day, and the wiki
> keeps history which can be benifitial (a sufficiently advanced website could do
> this too).
I'd prefer a dedicated interface where anyone can contribute its
configuration. The target configuration count is in hundreds if not
thousands, that's not something we want to handle manually.
That being said, if someone _else_ is going to take care, it doesn't
matter that much to me ;) The usual open development rule applies:
whoever does the job decides how it should be done. I simply haven't
looked enough into it all yet, for now I'm focusing on getting
libsensors4 ready so that we can release it before the end of the year.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-08-21 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:31 [lm-sensors] Submitting motherboard-specific support? (w/ attached Romain Dolbeau
2007-08-20 16:25 ` [lm-sensors] Submitting motherboard-specific support? (w/ Juerg Haefliger
2007-08-20 17:27 ` Juerg Haefliger
2007-08-20 17:58 ` Jean Delvare
2007-08-20 20:44 ` Hans de Goede
2007-08-20 21:12 ` Ivo Manca
2007-08-21 8:45 ` Jean Delvare [this message]
2007-08-21 10:35 ` Axel Thimm
2007-08-21 11:10 ` Romain Dolbeau
2007-08-21 14:38 ` Axel Thimm
2007-08-21 14:50 ` Jean Delvare
2007-08-21 17:17 ` Jean Delvare
2007-08-21 17:38 ` Axel Thimm
2007-08-22 19:45 ` Sebastian Flothow
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=20070821104510.3cf9518e@hyperion.delvare \
--to=khali@linux-fr.org \
--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.