1 |
On 3 April 2010 16:30, Alex Legler <a3li@g.o> wrote: |
2 |
> I propose to use MediaWiki. |
3 |
|
4 |
As I said in my other post, MediaWiki and MoinMoin should, in my |
5 |
opinion, be on our shortlist to consider. |
6 |
|
7 |
> I'd be interested in helping out with the backend part, i.e. setting up |
8 |
> and maintaining the Wiki software and the needed extensions, |
9 |
> user management and support. |
10 |
|
11 |
Thanks, that would certainly be helpful. |
12 |
|
13 |
> Here's another idea: |
14 |
> The German Wikipedia uses a concept called "sighted revisions". If you |
15 |
> visit an article without logging in you will see the latest sighted |
16 |
> revision, as an identified user you can also view the latest revision. |
17 |
|
18 |
That's an interesting idea, which we should consider. |
19 |
|
20 |
|
21 |
>> Is there anything else we should consider before getting started? |
22 |
>> |
23 |
> |
24 |
> Maybe we should discuss what goals we want to reach with a Wiki. |
25 |
> |
26 |
> One thing is offering user-contributed documentation, of course. |
27 |
> But do we also want a developer wiki? Or offer per-project realms in our |
28 |
> wiki? Or $something_else? |
29 |
|
30 |
Good suggestion. I think we would want to accommodate both |
31 |
user-contributed documentation and developer needs. For example, |
32 |
recently the need arose to have a wiki page for GSoC ideas. |
33 |
Projects may want to use it as well. I find myself using the wiki |
34 |
at gitorious.org (where we also host our overlay) for purposes of |
35 |
the Qt herd. It would also be handy for developing new documentation |
36 |
(it would have helped for the LXDE guide, or the Qt4 ebuild |
37 |
development howto) as well as keeping existing documentation up to |
38 |
date. GuideXML documents are often experienced as an unnecessary |
39 |
barrier. |
40 |
|
41 |
What else do we want it for and how would that impact organization? |
42 |
|
43 |
-- |
44 |
Ben de Groot |
45 |
Gentoo Linux Qt project lead developer |