From: mrenzmann@otaku42.de (Michael Renzmann)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] project status and future
Date: Tue, 03 Jan 2006 07:25:25 +0000 [thread overview]
Message-ID: <1136273126.4455.15.camel@gimli> (raw)
In-Reply-To: <43AF1E4A.90902@sh.cvut.cz>
Hi.
On Mon, 2006-01-02 at 23:38 +0100, Axel Thimm wrote:
> didn't we want to use mediawiki instead of trac's embedded wiki?
>
> http://lm-sensors.org/wiki/
>
> vs
>
> http://lm-sensors.org/trac/wiki/
I'd say no. While mediawiki might be more powerful regarding the markup
it uses, we will loose one of the features of Trac: the possibility to
easily link between tickets, wiki, changeset comments, and other Trac
objects.
Trac uses the Wiki markup nearly everywhere where someone can enter text
(the tickets for example), and if we decided to use Mediawiki for the
main wiki, users would be forced to cope with two different wiki markup
dialects.
Bottom line: personally I'd strongly vote for the Trac-internal wiki
rather than Mediawiki in this case.
> As wikispamming is just around the corner, we need to restrain freely
> editing
madwifi.org runs Trac for about three months now. We had no incident of
Wiki spam so far, and only one or two incidents of minor vandalism
(someone thought it would be funny to remove parts of a newbie
documentation).
We allow changes to anonymous users, with the exception of only a few
pages. One of them is a page where I publish my public GPG key.
Everything else can be edited freely.
I have a bot running in our IRC channel that announces
added/deleted/changed wiki pages and tickets, as well as new Subversion
commits. That way it's easy to have a quick look on the changes, which
can then be reverted if necessary.
> and have some wiki operators (e.g. people that acknowledge
> other people's wiki accounts).
Accounts for Trac (which includes the Wiki) will have to be created in
two (three) steps:
1. adding the account credentials to a htpasswd file
2. adding the corresponding permissions to the user via trac-admin
(permission add ...)
3. (optional) The user has to log in and fill in the fields on the
"Settings" page to create a valid session. Without this session his name
won't occur in the drop-down list of the "(re)assign to" field of
tickets.
> > Also someone with trac admin please update the logo ;)
See:
http://lm-sensors.org/trac/wiki/TracInterfaceCustomization#ProjectLogoandIcon
Needs to be done by someone with shell access to the server, write
access to the trac.ini and, depending on the way Trac is installed (as
CGI or using mod_python), the rigths to restart Apache.
Bye, Mike
next prev parent reply other threads:[~2006-01-03 7:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 22:33 [lm-sensors] project status and future Rudolf Marek
2005-12-27 10:52 ` Michael Renzmann
2005-12-28 10:09 ` Volker Kuhlmann
2005-12-28 19:07 ` Philip Edelbrock
2005-12-28 21:32 ` Henrique de Moraes Holschuh
2005-12-29 7:33 ` Michael Renzmann
2005-12-29 22:33 ` Jean Delvare
2005-12-29 22:49 ` Rudolf Marek
2005-12-29 23:06 ` Philip Edelbrock
2006-01-02 16:41 ` Michael Renzmann
2006-01-02 22:19 ` Rudolf Marek
2006-01-02 22:38 ` Axel Thimm
2006-01-03 7:25 ` Michael Renzmann [this message]
2006-01-03 14:05 ` Axel Thimm
2006-01-03 14:45 ` Michael Renzmann
2006-01-06 7:08 ` Jim Cromie
2006-01-06 20:01 ` Rudolf Marek
2006-01-06 21:40 ` Axel Thimm
2006-01-06 21:42 ` Philip Edelbrock
2006-01-06 21:48 ` Axel Thimm
2006-01-07 11:06 ` Jean Delvare
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=1136273126.4455.15.camel@gimli \
--to=mrenzmann@otaku42.de \
--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.