All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] project status and future
Date: Tue, 03 Jan 2006 14:05:45 +0000	[thread overview]
Message-ID: <20060103140545.GC4076@neu.nirvana> (raw)
In-Reply-To: <43AF1E4A.90902@sh.cvut.cz>

Hi,

On Tue, Jan 03, 2006 at 08:25:25AM +0100, Michael Renzmann wrote:
> 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.

Is it really that helpful? At ivtvdriver.org nobody really misses
that, while there are quite a few users that are mediawiki experts and
have taken the load off the developers' shoulders. After all one of
the ideas of a wiki is to make it easier for users to contribute to
documentation.

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

At least tickets and any items that will be sent in notifier channels
(a commit/notify list) should not contain markup. This makes it very
hard to the ASCII MUA user (i.e. all od us? ;).

> Bottom line: personally I'd strongly vote for the Trac-internal wiki
> rather than Mediawiki in this case.

Well, as I said I personally prefer mediawiki, but I'm not insisting :)
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060103/fb057afb/attachment.bin

  parent reply	other threads:[~2006-01-03 14:05 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
2006-01-03 14:05 ` Axel Thimm [this message]
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=20060103140545.GC4076@neu.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.