Comments (12)
Documentation will be hosted on Github. I will start writing it, any help is of course welcome towards this community effort. It's about time this project gets a decent documentation.
from ktx.
There's a wiki on this GitHub page that anyone can update, so it would be nice if we could all come together and try to get some basic documentation up.
from ktx.
I totally agree. Question is though if we should document it here or on quakeworld.nu wiki (that will undergo an upgrade in the near future). Since these projects are rather inactive I think having everything on one place might be more suitable, what do you think? (In general I think that docs should be as close to the src as possible and external parties to link to it, but this is a bit different due to status)
from ktx.
I think the documentation should be here on GitHub.
If we try to keep the pages to a minimum, it can easily be duplicated to QW.nu wiki.
from ktx.
No please no duplication, that's the worst thing to do. As soon as something changes at one place there are two (or more) sources of information that might contradict eachother + it's extra maintenance. The reasonable options IMO are to either host it on github and link from qwnu wiki or host on qwnu wiki and link to it from github.
from ktx.
Then link it here, imo.
from ktx.
Why do you think so? :) My arguments for having docs on wiki:
- I imagine it's easier for people to find
- The projects have a tight connection and usually work together so having the documentation in one place would simplify compared to per github project page, since that would mean atleast 4 different places for each module.
- Repo is rather unmaintained/inactive, it's all up to deurks control and might dissappear anytime (like qw-dev)
from ktx.
The inactivity bit is a good argument, so sure. I agree.
from ktx.
+1 for version controlled documentation. Please don't do it in forums or anywhere else. GitHub pages is great tool and people can fork and continue working if one project decides to quit.
from ktx.
@tsoikkel That's the best in the generic case yes but not necessarily in this case. The qw scene is rather focused around quakeworld.nu and ktx/mvdsv aren't used without eachother in 99% of the cases for instance. The quakeworld wiki is "version" controlled in the sense that it's a mediawiki. Requires some thought this :P
from ktx.
Sorry I haven't been following the community for 10 years. Now just popped in and tried to setup a server.
Ended up into:
KTX: http://www.quakeworld.nu/forum/topic/2504/ktx-kombat-teams-extreme-files
MVDSV: http://www.quakeworld.nu/forum/topic/2505/mvdsv-multiview-demo-server-files
This is exactly the case when personally hosted services are huge risk to actually losing data.
from ktx.
Putting that here to not forget to add it to documentation:
https://gist.github.com/meag/09b7b6c736b8f2fde1df991cf1151abb
https://gist.github.com/meag/b5f3e37777d4e3233cba5df2046d1323
from ktx.
Related Issues (20)
- [BUG] Hoonymode should disable powerups, but does not HOT 5
- [BUG] Fix for build on FreeBSD HOT 1
- [BUG] Correction of use strlcpy - potencial security issue HOT 1
- [REQ] BOTS: humanize bot vertical tracking
- [REQ] New rpickup teamnames and colors HOT 6
- licensing of example sounds and models HOT 1
- [REQ] Dropsuit command / Biosuit improvements
- [BUG] Spectators can execute /botcmd removebot
- Request to restore crhook from PR #277 as a 4th option or roll back HOT 2
- [BUG] Hoonymode rounds should be "best of" HOT 1
- [BUG] /laststats data if player drops
- [BUG] /laststats now working for demos
- [PATCH] Add possibility to change race countdown
- [PATCH] Turn off spikes in race mode
- [PATCH] Add route for e1m2
- RFC | KTX Bot (frogbot) editor & map support updates HOT 1
- [BUG] func_bob implementation breaks the deathmatch maps from Dimension of the Machine HOT 7
- [PUP] Certain commands can make server restart without a vote HOT 1
- [BUG] Limit elected admin privilages HOT 3
- [REQ] Change default Health/armor in CARENA mode HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ktx.