It does sound like a good idea. There'd have to be some sort of regulation (only forum members with more than 10 posts, or something similar), so that random weirdos don't just go all over it and fill it with junk.
MoP - ip's are traced and banned and pages can easily be roll-back'd even when completely defaced. Also, a login system can be required if you don't want random guest wierdos editing the place. Pages can also be protected from any editing by those who have the power to protect them (usually admins)
Ah, I didn't know about the roll-back thing. Yeah, I guess having it open to everyone would work fine, then. There's always assholes who want to screw around with stuff like that though ... is it possible to have something like a "Wiki moderator" who could make sure nothing was being abused?
It sounds like a good idea to me, but don't forget that links to tutorials and the like need to be checked regularly. We don't want link rot. The W3C link checker would be cool for that.
[ QUOTE ]
There'd have to be some sort of regulation (only forum members with more than 10 posts, or something similar), so that random weirdos don't just go all over it and fill it with junk.
[/ QUOTE ] Whoa, even I would actually qualify for that. It's not too difficult to make 10 posts, when you are a random weirdo seeking for action. However, I do like the idea of a wiki moderator.
ok, we havent been ignoring this, but rather watching to test interest.
we're going to set something up. something simple to start off with and see where it goes. Gauss is going to be the lead on this, so tell him his concepts are wonderful.
remember that the wiki is not a messageboard. gauss will have full rights to administer silliness out of it as well as users who can't tell the difference. thats my usual warning to play nice.
current status is that i've got a brief outline of polycount's earlier days is up on a 'history' page, because i think it's important to not lose that kind of stuff... polycount is 7 years old already, which is pretty anazingly old by internet standards especially. that's essentially blocked out, now i'm getting to delineating the basic structure for the major meat of the wiki... the place for the tutorials, etc. etc. i'll keep this thread updated for when we're looking to make it public
The ttorial transfers would be a good thing, because at some point, around the release of UT2003, there haven't been many "separate" tutorials, or game specific tutorials on this site.
in refrence to scott's comment, i'd like to see the same. and as it will be a wiki, everyone will be able to help.
i'd personally like to see the wiki replace the existing resources and links sections on the site completely. no more busted links as we'd have everything locally. it would be a good thing.
you can poke around the info there for an idea of the features we'll have availible. if you see something you have questions on, ask in here and we'll look to answer them, asap.
So do have to learn this scripting language before we can start adding our little information tidbits or is the some sort of nicer front end available?
there isnt a work processor built into this thing. there is some markup language thats required to polish enties completely, but if you are looking to just lay down some text, its straightforward. you can always ask for a polish pass from gauss or another if you cant figure out the markup stuff. its pretty simple tho, about as simple as it gets which was choosen on purpose to make it as simple as possible for artists.
Anything that lets multiple people work on the same document is a blessing. Not only do you get constant feedback and corrections, but you continually links keywords to explanations. It's a stunning system.
That it is..We've been using a wiki at work for a couple of weeks. The most significant use we've gotten out of it so far is collaboration on a game design document..invaluable.
There are two things holding back the rest of our team from using it.. first of all, most people resist the idea of creating entire documents in a wiki editor; they'd much rather use microsoft word. I end up transferring and formatting the documents for them. Another thing is I haven't quite figured out how to totally customize the look and feel of the pages.. kind of superficial, but people still chuckle at the generic white template with the flower (we went with MediaWiki) and ALWAYS suggest we use the company colors and logo.
Still, wiki's are useful tech. Anyone else running one at the workplace?
I'm itching to create a "3D software tips & tricks" section, with sub-sets for Maya, Max, Lightwave, Silo, whatever. Then have a list of the most useful default shortcuts, features, techniques and tricks for that software.
If anything, I'd just do that so that people no longer have to ask me how they accidentally managed to turn on Degradation Override...
Replies
/me imagines tuts and explanations and stuff all linking to eachother in a community contributive form
It does sound like a good idea. There'd have to be some sort of regulation (only forum members with more than 10 posts, or something similar), so that random weirdos don't just go all over it and fill it with junk.
http://c2.com/cgi/wiki?WikiEngines
^ There are some Wiki engines available..
MoP - ip's are traced and banned and pages can easily be roll-back'd even when completely defaced. Also, a login system can be required if you don't want random guest wierdos editing the place. Pages can also be protected from any editing by those who have the power to protect them (usually admins)
/jzero
Ive helped get one of these get set up in Rebellion - it was very useful.
Honestly, there is not much besides scripted spammers that can damage a wiki.
[ QUOTE ]
There'd have to be some sort of regulation (only forum members with more than 10 posts, or something similar), so that random weirdos don't just go all over it and fill it with junk.
[/ QUOTE ] Whoa, even I would actually qualify for that. It's not too difficult to make 10 posts, when you are a random weirdo seeking for action. However, I do like the idea of a wiki moderator.
we're going to set something up. something simple to start off with and see where it goes. Gauss is going to be the lead on this, so tell him his concepts are wonderful.
remember that the wiki is not a messageboard. gauss will have full rights to administer silliness out of it as well as users who can't tell the difference. thats my usual warning to play nice.
more info as it happens.
ok, so i guess not so secretly, since you know it exists... but whatever
Scott
i'd personally like to see the wiki replace the existing resources and links sections on the site completely. no more busted links as we'd have everything locally. it would be a good thing.
http://moinmoin.wikiwikiweb.de/
you can poke around the info there for an idea of the features we'll have availible. if you see something you have questions on, ask in here and we'll look to answer them, asap.
There are two things holding back the rest of our team from using it.. first of all, most people resist the idea of creating entire documents in a wiki editor; they'd much rather use microsoft word. I end up transferring and formatting the documents for them. Another thing is I haven't quite figured out how to totally customize the look and feel of the pages.. kind of superficial, but people still chuckle at the generic white template with the flower (we went with MediaWiki) and ALWAYS suggest we use the company colors and logo.
Still, wiki's are useful tech. Anyone else running one at the workplace?
Gauss is going to be the lead on this, so tell him his concepts are wonderful.
[/ QUOTE ]
Gauss, your concepts are wonderful.
That said, I really love the idea!
If anything, I'd just do that so that people no longer have to ask me how they accidentally managed to turn on Degradation Override...