All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Submitting motherboard-specific support? (w/
Date: Tue, 21 Aug 2007 10:35:48 +0000	[thread overview]
Message-ID: <20070821103548.GA6770@puariko.nirvana> (raw)
In-Reply-To: <46C997B4.50509@dolbeau.org>


[-- Attachment #1.1: Type: text/plain, Size: 2335 bytes --]

On Tue, Aug 21, 2007 at 10:45:10AM +0200, Jean Delvare wrote:
> > 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?

Sure, as long as someone manages the app and any involved security
issues. PHP is rather tricky and needs good care security-wise.

> > 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.

I would also tend to recommend a wiki. The stumbing block is the spam
issue, and I think if we write a simple mailman like registration
module (for example in PHP :) we could have people register once and
then use wiki/trac/tickets/svn etc. as you like (not as flat as it
sounds, but with some lm-sensors heads elevating permissions as
needed, e.g. self-registration allows wiki/ticket editing, and svn
write access needs a bit flip by an lm-sensors leader etc)

Hans, maybe your PHP friend expert (is that Romain copied in the Cc?)
would be interested in this general purpose registration module
stealing some methods from mailman?
-- 
Axel.Thimm at ATrpms.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-08-21 10:35 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
2007-08-21 10:35 ` Axel Thimm [this message]
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=20070821103548.GA6770@puariko.nirvana \
    --to=axel.thimm@atrpms.net \
    --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.