From: Fredrik J. <jer...@sq...> - 2007-02-01 11:45:15
|
>>> Me too. If there's already a private svn at squirrelmail.org, that's >>> fine, but I can also set one up if needed. >> >> Why non-public? What is there to hide? > > I was thinking more like "what's there to show?". :-) However, I do not > have a strong opinion on this matter. The site itself isn't Open Source is it? If we make the code public, what license shall we choose for it? Do we need improve security to make sure that the data in the database is safe? It will become a project of its own. If that's what we want, then we can use a public repository. > On a related matter, does anyone _not_ like the wiki? Its navigation is > lacking, and it looks ugly. If anyone else dislikes it as much as I do , > then perhaps we could consider replacing it with something else. The looks can be changed with some CSS. Much of the information in it should be moved to the static documentation. When that's done, there's not going to be much left in the wiki. Progress on moving the documentation has been slow, since I want to verify that the information is correct and have to rewrite some parts to be clearer and better English, but if I lower the quality of the move I can do it much quicker. > I've had good experience with dokuwiki, having installed and used it at > http://sieve.info) and mediawiki, although that one is bloated and > beyond our needs. I don't mind replacing the existing wiki with something else, but I'm not really sure we need a wiki at all but dumping short lived documents. We don't want to use it as a support forum, we want the documentation to be verified and in the repository, so what use is it that we want to satisfy with a wiki? Sincerely, Fredrik |