Chris Lott wrote:

Hi!

> 1) I communicated with Pascal and he indicated that
> scid-chess.org sounded like the best fit to him. So I plan
> to purchase and set that up.

Set the wiki up first to get people on board, name is second
order. (IMHO)

> 2) Where the wiki can shine, I think, is in providing a
> place where a) enthusiasts can contribute and b) things
> that don't exactly fit into the "official
> documentation"--whether because they are digressions,
> tutorials, tips and tricks, etc-- can be shared in a
> central location.

Keep in mind not to hook off the current community. There
should be a way where I can see what's going on without the
necessity to point my webbrowser to the page. At least if
you want comments from my end to a question. Probably you
don't ;)

> 3) The official scid docs remain where they are.

Given proper setup of the wiki one could easily add a simple
url call to the end of each chapter in Scid that points to
the Wiki section. I think, just for this the wiki pages
should map somehow to the online docs.

> 4) The mailing list remains the central place for
> discussion. I agree with Alexander that trying to hold
> discussions on the wiki doesn't make a lot of sense. It
> doesn't fit the form. I do think there should be "comment"
> or "talk" or some kind of pages where people can share
> meta-conversation without altering the page itself, but
> the wikipedia model of discussion isn't applicable here.

MySQL docs are IMHO a good model.

> 5) Take this for what it's worth, but I work with social
> software for a living and comparisons of most wikis to
> wikipedia are epic FAILs because wikipedia is unlike
> almost any other wiki due to its sheer size and
> popularity.

You are right, I did not want to compare it to Wikipedia,
just point out some ideas.

> 6) re: wiki shortcomings. Pascal mentioned that wikis
> weren't good with complex data structures and didn't have
> finely granulated security...

Do we really need that???

> so the main issue is preventing spam

Yes.

>Really, I think simple is best.

Agree, and the most important thing IMHO is that the editor
is usable and simple. === is really not simpler than <h2>.
None of the users should have to  fiddle with this kind of
"simplicity". (Having a sandbox for a Wiki is synonymous to
say "we failed" before even getting started...)

-- 

Kind regards,                /                 War is Peace.
                             |            Freedom is Slavery.
Alexander Wagner            |         Ignorance is Strength.
                             |
                             | Theory     : G. Orwell, "1984"
                            /  In practice:   USA, since 2001

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to