Wanted: (Media)Wiki Guru and opinions.

[UniqPhoeniX]

I don't think all cvars should have their own page, and it doesn't require vid_restart, range is 0.5 - 3.

[khalsa]

So what are we doing about versions?  More importantly, what about things that change between 1.1 and newer clients/qvms?

All information should be about 1.1, things that are significantly changed and are in svn should be mentioned imo.

Modding and mapping sections are for howtos or already-released mods/maps? (or both)

How to Mod and Map.

".svg" is not a permitted file type. Permitted file types are png, gif, jpg, jpeg.
Can we have SVG's too?
EDIT: [wiki]R_gamma[/wiki]  Is that how it should be?  We should agree on a style before all doing different things.

SVG enabled. Scratch that, server is having some issues with that, use PNG for now untill I have time to look into it.

As far as per-page cvars... you guys figure that out with Paradox.. I dunno the best way to do it.


Khalsa

[Paradox]

Per page cvars is perfect, and NOT impossible.

Mediawiki's homepage has a page for every $wg setting, so i dont see how we are any different. If anyone wants, ill make up a template for the cvars so we can see information about them, such as type, default, etc.

And if you guys see any vandalism, please report it to Khalsa or me.

David, do we really need as compicated a template structure as that of wikipedia? Wouldn't it be better to make our own from scratch?

[David]

Templates are good, as we can change the template and all pages that use it are updated.  It also ensures all pages follow the same style.  (The templates should of course be fully protected)
I'd suggest doing the same for maps etc etc.

[Paradox]

Yes, i encourage templates. But we dont need thousands of complex templates (such as !, !!, !!!!!!) etc.

Keep it simple till we need it.

I haven't edited any of your templates, but i have left comments on their talk pages. You might want to read them.

[David]

Yeah, the ! stuff is there because the thing to do alternating colored rows needs it, and is a major mess so I didn't want to edit it.
I'm sure it can be done a nicer way, I just don't know how and importing a handful of templates is easier than reinventing the wheel.

[Paradox]

Ah well, i guess we can just copy them. But cleaning them up later=headache.

[Roanoke]

Hope it's not too late, but maybe a section for mod concepts?

Edit: I like how it fits with the forum's theme. I also like the binding section.
Edit2: May I ask how you imported the trem users into the wiki? Will the wiki's users update as the forum's do?

[David]

2 things:
Tables don't work.  They work but no borders or anything else.
Should we put cvars and commands and whatever into there own namespaces?  As it is there will be pages call "name" and "sex" and "set" and whatnot, it could get a big confusing and potentially ambiguous.  If they are all Cvar:name and Command:print then it will be clearer, and also easier on the URLs.

[khalsa]

Hope it's not too late, but maybe a section for mod concepts?

Edit: I like how it fits with the forum's theme. I also like the binding section.
Edit2: May I ask how you imported the trem users into the wiki? Will the wiki's users update as the forum's do?

Mod concepts go in the Mod idea Palace
Thanks
No importing, it's simply calls SMF's SSI for authentication. So yes.

2 things:
Tables don't work.  They work but no borders or anything else.

I will look into this as soon as I get time.

[Roanoke]

Mod concepts go in the Mod idea Palace

Well, yes, but some mod concepts would be better in a wiki format. Especially new ones, since they require a lot of tweaking.

[Paradox]

2 things:
Tables don't work.  They work but no borders or anything else.

2 reasons:
No table style defined in the theme. Try setting tables to class wikitable.

If you see any other missing classes/styles that should be standard, tell me (talk page plx) and ill add them.

[khalsa]

Well, yes, but some mod concepts would be better in a wiki format. Especially new ones, since they require a lot of tweaking.

Every post comes with it's very own edit or modify button, it's quite amazing really.

If the mod is that complete or large, they should have their own website anyways :-)

Khalsa

[Roanoke]

Every post comes with it's very own edit or modify button, it's quite amazing really.

If the mod is that complete or large, they should have their own website anyways :-)

Khalsa

Yes, but not everyone can edit my post. And what's the point of setting up a website for a concept?

[khalsa]

Suggest changes go in replies for discussion. If it's *your* concept then you keep up with the first post

Not like a concept needs to be super duper fleshed out, once code starts hitting the SCM's then you basically do need a 'website' of some sort.

Khalsa

[Paradox]

Google sites if you want a plainass simple wiki for your mod that wont ever get off the ground

[Paradox]

If anyone is looking for something to do for the wiki, look here
http://tremulous.net/wiki/Category:Unsorted_Cvars

[palmax]

I'm sorry, but I don't know where to put this info.

Can you write a public documentation for train new developers of tremulous? I want to understand howto collaborate to tremulous.

Thanks

[bacon665]

could there be an article on porting maps and maybe add the user maps to the list?
Oh and i did this. http://tremulous.net/wiki/Compiling
Not sure where you wanted it on the main page so i left it alone.
It needs mac and POSIX build instructions. and im sure theres several issues that need to be addressed for the windows guide.
the regulations of wikis are so strict ts hard to put a link to anything.
for instance you cant provide a download link for mingw or the MS sdk.

[David]

I vote add pages for other maps, but not on the main page, as deciding who gets to be there is a major PITA.  Add a link to Category:Maps though.
Don't need a compiling guild for posix, it's just "make" and done.
And why can't you link?

[bacon665]

http://en.wikipedia.org/wiki/WP:EL

There are individual pages for maps currently.
I think the best way to handle user maps would be if we retag the existing one with (defualt) and (username) to distinguish the ones shipped with trem and the rest. also it gives credit to the creator.
and to relieve job duty i think it best that the creators make pages for their maps and add them unless by some request.
wikipedia can be a pain to create pages for.

and i disagree about POSIX.
BSD has ports and portsnap and is it in asparagus?
and area for simple svn needs to be added that just says
"check out here using client of your choice
refer to doc for help
cd to directory
execute "make install clean"

and OSX is technically UNIX.
id say installation needs to be added to the main hierchy so we can also add using layman and emerge in gentoo and the binary package systems equo yum dpkg rpm apt and the one distro systems like pisi used in pardus.

[David]

Screw wikipedia's policies and crap.  Link whatever you need to.
Leave the maps as-is I vote.  There's little need to mark official and unofficial maps, most people know.  And if two maps have the same name, then first come first server, idiots shouldn't steal names.
It's a wiki, anyone can make a page for a map.

Encouraging people to use the repos is a bad idea, they just cause problems and if we suggest it it makes it harder to tell people to not use them when they come asking for help.

[bacon665]

okey dokey then ill do some more work on it in a couple hours.

Updated.

Fixed busted heading format
Fixed contents menu
Added link to MS SDK
Added POSIX instructions
Changed code notes accordingly so that someone doesnt redo work


Things to do to/for the compiling page.

Add MAC instructions or point me to a howto
Link MSys
Link MinGW
Add a "why should i compile" or point me to a good summary
Add a Section for BSD ports, equo and emerge. Or simply tell me the directory of the Ports tree and the location for the overlays and i will add them.
Spellchauk =P

If you see something else let me know.

[bacon665]

OH that page needs to be added to the main navigate page under documentation.
If someone could please do so. that way we dont have multiple pages.

[tojimaru]

I've been sorting all those unsorted cvars and I'm not sure where to put the ones that are both client and server side. Should they stay in the unsorted list?

[David]

Put them in all  category's that apply.
Just put the tags one after another like in [wiki]Sv_master1[/wiki].
But 99% don't go in more than one.

[mooseberry]

I have a question about the wiki, and I figured this would be the best place to ask. I was wondering about something that I'd like a dev/mod's opinion on.

Many of the articles have stub templates, and many of them _do_ need more work, but many of them I don't see how they will ever be not "stubs."

For example; [wiki]G_alienStage3Threshold[/wiki]. I don't think there is really anything more that should be added to this article, simply because there isn't really anything that can be added to this article. It tells what the cvar is and what it does. Now, if this were the only article like this I would remove the stub template, but there are dozens of similar articles (mostly cvars) that are tagged as stubs because they are only a few lines. I think that while short, there isn't much that could be done to them (but if anyone has suggestions please feel free to voice them). The bad thing about having all these articles tagged as stubs when there isn't much that can be done to change them is the fact that 1. it's cluttered, and 2. when people look at the list of stubs in order to help improve the wiki they see mostly these cvars and such that can't really be helped. I think a stub means more "a page that needs more added to be finished" instead of "a short page."

If there is some good way that anyone can think of to improve/lengthen these many short articles in general please say and people (myself included) will hopefully get that done. If there is no way that anyone sees to change this, I suggest removing the stub category on all of the articles which can not be lengthened (many of the cvars).

What say you people? (Mostly ones who have a real say, but anyone can speak.)

[David]

I vote remove the stub for such articles.  It was auto-added for pages with the auto-created infoboxes.  If a page is "complete" then it's not a stub.

Should probably have used a "auto-created" template instead.


Soon we'll have "not updated for 1.2" boxes on every page

[khalsa]

Basically what david said The stub thing was added automatically to all the.. automatically created pages. Once the page is functionally complete (such as your example) feel free to remove it

[sheridanm962]

I want crow bars in tremulous they would make good melee weapons