From: "H. Langos" <henrik-dvb@prak.org>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Linuxtv wiki needs email notification/more email-ready users
Date: Fri, 18 Sep 2009 10:09:41 +0200 [thread overview]
Message-ID: <20090918080941.GA15590@www.viadmin.org> (raw)
Hi there,
after a while I decided to come back to the linuxtv wiki to finish
organizing the bazillion dvb-t usb devices in a way that helps
a) normal users to find out if a certain device is supported and
b) developers to update information on the drivers they manage.
Some preview of this can be seen on my playground page:
http://www.linuxtv.org/wiki/index.php/HLPlayground2
As this is a more complicated way of storing the information than just plain
tables, I'd like to keep an eye on changes. Not because of fear of
vandalisim but because changes to the templates/date potentially have
effects on a lot of pages.
There are some people who day by day put a lot of effort and work into the
wiki and I'd like to thank them all for their continuing effort. I myself
have only occasionaly time to update information there and I miss a lot
of changes, even to the pages I watch, because the "watchlist" and "recent
cahnges" reaches only seven days back. Manually going through the pages on
my watchlist (currently 57) is not what I'd call good use of resources.
It would be great if it was possible to get (immediate/daily/weekly?) change
notifications by email in order not to lose track of what is happening to
the pages that I care about. (I bet this is standard functionality of
mediawiki or at least one of the more common extentions.)
Also I'd like to encourage new and existing users to add their email address
to their profile AND to check the "Enable e-mail from other users" box.
Maybe we could change the default to enable that box?
That way it is possible to ask for missing details if somebody adds a new
device, or to send hints if somebody writes in an article that a certain
device doesn't work. Or to simply write a short note when removing some
information like "Hey dude, I just removed some information that you added
to article X because it is already contained in article Y. Instead I've
added a link to Y. Thank you for your help and keep up the good work!..."
Also developers could ask people who are interested in a device's driver to
check out a new version as soon as it is ready.
All in all it would improve the user experience and the quality of information
on the wiki as feedback would not have to go through the "discussion" pages.
I went that way when talking to some other wiki admins about my efforts to
unify the usb dvb-t data and the experience shows that wiki's are not a
good medium for serious discussions.
cheers
-henrik
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2009-09-18 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 8:09 H. Langos [this message]
2009-09-19 5:47 ` [linux-dvb] Linuxtv wiki needs email notification/more email-ready users CityK
2009-10-13 4:52 ` CityK
2009-10-14 8:53 ` H. Langos
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=20090918080941.GA15590@www.viadmin.org \
--to=henrik-dvb@prak.org \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@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