From: Simon van der Veldt <simon.vanderveldt+linux-hwmon@gmail.com>
To: linux-hwmon@vger.kernel.org
Subject: RE: Problems with lm-sensors web site / Wiki
Date: Thu, 19 May 2016 20:53:49 +0000 (UTC) [thread overview]
Message-ID: <loom.20160519T225212-685@post.gmane.org> (raw)
Guenter Roeck <linux <at> roeck-us.net> writes:
>
> On 01/27/2016 01:17 AM, Philip Edelbrock wrote:
> >
> >> On Jan 26, 2016, at 7:33 AM, Guenter Roeck <linux <at> roeck-us.net>
wrote:
> >>
> >> On 01/26/2016 07:02 AM, Paul Crawford wrote:
> >>> I was just checking the wiki (that used to be) on the www.lm-
sensors.org
> >>> site and it looks as if someone has messed up the Apache web server,
as
> >>> it only has a directory 'ht' with a .rpm file in it.
> >>>
> >>> Does anyone know who is looking after the site and/or if this is being
> >>> fixed?
> >>>
> >>
> >> The maintainer is not reachable. I think we'll have to re-create the
site
> >> from scratch.
> >>
> >> Guenter
> >
> >
> > Yes, unfortunately. I see www.lm-sensors.org is pointing to the
httptunnel project, which is
> definitely not us.
> >
> > I just wish we had a copy of the Trac and database with all the pages
and such… ugggg. That’s a bit upsetting.
> >
> Most or at least some of it can be found in web caches, though it will be
a bit of work.
>
> > I could set something up where the web files are on Github and we can
have multiple authors. If nothing else,
> somebody could always take the Github files and run with them without
having to track down a former MIA admin.
> >
> > It probably won’t be too soon, though, I’m a bit swamped with my day job
but I’ll try to get something
> going soon with multiple admins. I’m open to other ideas, too. I own lm-
sensors.org and can get the DNS to
> point anywhere.
> >
>
> Is it possible to set up a wiki ? No idea how the back-end storage would
work, though.
> We'll definitely want it backed up this time.
>
> Guenter
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors <at> lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
>
(posting here as well because the "other"/old lm-sensors mailing list seems
to be no longer used?
Hi all, never posted to the list before, but I'm a happy user of the
functionality lm_sensors provides.
I feel like the lm_sensors site being down isn't the best experience for new
(and old) users ;)
I'd like to suggest to make use of the features GitHub offers to
simplify/reduce the amount of work and cost needed to fix this and making
sure keeping everything running/available doesn't depend on a single person.
I have a fair amount of experience with it and want to help out.
My suggestion would be:
- Create an lm_sensors organization and add the necessary user as
owner/contributor
- Add a repo for the main sources
- Add a repo for board configurations (this is something I was already
working on, could for now just host the configs from the wiki)
- Add a repo to automatically host the site from (github pages)
For each repository there is an included wiki, so I think it's easiest to
add the initial docs there. Optionally the docs could be published to a
proper website using github pages as well.
Let me know if this sounds good to all of you, hope I can help/do something
back :)
Thanks!
Simon
reply other threads:[~2016-05-19 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20160519T225212-685@post.gmane.org \
--to=simon.vanderveldt+linux-hwmon@gmail.com \
--cc=linux-hwmon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox