In any case, I think the main idea is that the community-maintained wiki should be somewhat separate from the main, official, website. In the past they kind of got conflated and in the end the official website was a bit of a mess. So no matter which engine we use, I'd like a clear separation between official content and community-maintained pages
The main reason why I disabled public user creation were the many registrations of accounts never used in the old wiki. The quality of user contributions was never an issue as anyone who made significant contributions was well known in the community and had admin access anyway. Surely, the old wiki was a big mess, but that was because no one really cared about maintaining it for years. So when I started cleaning things up I had to e.g. remove an FAQ entry referring to a bug closed over 6 years ago. This is also why the website ran on an outdated and insecure mediawiki version for so many years.
In any case, I think the main idea is that the community-maintained wiki should be somewhat separate from the main, official, website. In the past they kind of got conflated and in the end the official website was a bit of a mess. So no matter which engine we use, I'd like a clear separation between official content and community-maintained pages
I can't really see what content a community wiki would have. The only two kinds of content I can imagine are those that should be collected in the official wiki and those that should be on private pages. Therefore, I'm suggesting an altered version of the current de-facto policy: Everyone well known to the community who wants to contribute to the wiki simply asks and eventually gets an account with admin rights.
As my main focus has shifted to different projects, it would also to be important to have a maintainer for the wiki as currently I'm the one having all the passwords for the server and admin access to the wiki skin repository, which is kind of weird as don't even have write access to the main code repository.
Did i can made the French version, of the new WebSite.
i help on the old website, to made some pages in French
I really appreciate the work you did translating, but tbh it's not worth investing time for the edge case where french main wiki pages are useful. That is why the current setup doesn't support internationalization.
I'm working with samuncle on some updates to the tutorials here, and he said he liked the idea of using GitHub. Perhaps something could be set up so that the pages could be managed on GitHub and automatically be pushed to the wiki. We were actually discussing it in issue #5 and I came across this, which sounded interesting.
Using github works great if you're used to github. But the problem is it excludes non-programmers. The Open Knwoledge Foundation Germany runs a central site (
http://codefor.de) that has to be edited by many people using github and jekyll and the only thing I hear is people complaining that editing is cumbersome to awful. Though, the sources of all wiki pages should be mirrored to github as an easy access and backup solution. I did this partially in the repository of the skin, but this should be automatized.
It would also be reasonable to move the wiki skin repository into the supertuxkart team on github. Due to github policies, either I need admin access in the supertuxkart team (which is unlike to happen), or I can move the skin to an admin and then he/she can move it into the team. Any admin here willing to do that?
.
. The new tracks look great though. But yeah I see that you have adopted to the 1 min 30 game video trailers crap all games do, that are just commercials (and put even a commercial in it).