From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: New sensors web site (was Re: 2nd mail archive?)
Date: Thu, 19 May 2005 06:25:26 +0000 [thread overview]
Message-ID: <FDmd72qq.1103018674.0379170.khali@localhost> (raw)
In-Reply-To: <41BDF25A.9030509@edgedesign.us>
> I like the idea of a wiki-style edit for web pages (at least only
> accessible for us).
If only a limited number of person can access it, I'm not sure it has an
interest to make it a wiki. Also, I wonder how you would create the
drivers tables as we have them now... Sounds a bit too complex to be
made with a wiki.
I am not opposed to the wiki concept, but I am not sure that all the web
site can be done that way. That said I can be convinced (let's just try
and see if we hit the limits or not). If there are more contributors to
the site that way (as opposed to hand-written HTML code under CVS) that
might be worth it, granted.
Also, we would need a place to manage board-specific configuration files.
I know someone started to work on this, don't know how far it went...
We need a place where we can store board-related info in a free but
consistent way (think of MBM's mobo list, more complete if possible).
http://mbm.livewiredev.com/mobolist.html
> Other things we will want:
>
> - CVS web browse
Sure, and if possible something a little bit more user-friendly than what
we had. Being able to download any revision of any file and getting
diffs between revisions are missing at the moment.
We might consider moving from CVS to Subversion. As far as I know it is
possible to convert CVS repositories without loss, and SVN allows things
CVS doesn't (such as renaming/moving files). This would suggest that
all contributors (not that many as far as I can tell) would need to
start using Subversion. Does it sound like a potential problem?
> - Support/ticket system
Again, something more user-friendly than what we have ATM would be
welcome. Original posters need to be able to add info to their ticket,
or the system is next to useless. Bugzilla? Or something else?
> - Mailing list (and web search)
Obviously...
> Anything else?
Nothing that I can think of.
> It probably isn't a bad time to try to roll in a new web design into the
> site. I think things are rather too large right now (big fonts, big
> graphics, nav on left is a little funky, etc.).
Whatever we do, it has to rely on CSS. No more old-style
netscape-generated crappy html please. I've tried to clean things up
bit by bit in the last year, but redesigning the site from scratch
can't be bad.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 New sensors web site (was Re: 2nd mail archive?) Philip Edelbrock
2005-05-19 6:25 ` Jean Delvare [this message]
2005-05-19 6:25 ` Philip Edelbrock
2005-05-19 6:25 ` Philip Edelbrock
2005-05-19 6:25 ` Philip Edelbrock
2005-05-19 6:25 ` Axel Thimm
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Axel Thimm
2005-05-19 6:25 ` Philip Edelbrock
2005-05-19 6:25 ` Philip Edelbrock
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=FDmd72qq.1103018674.0379170.khali@localhost \
--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.