Kk so step 1 done! Do we have this written up somewhere though? Would be good to be able to direct people interested in doing documentation to one place as a guide for process and standards.psi29a wrote:So people wishing to write "documentation" regardless of type, can do so by forking openmw on github and writing it, then submitting it for inclusion which triggers our peer review from the developers and those interested in documentation. Once merged, RTD renders the latest from master.
All documentation is in the ReST format, and thanks to sphinx/RTD we can have the output rendered as anything we want: html, LaTex, pdf...
Both would be good, but it's really whoever will put in the work. DavidD was new as far as I know, and started right with documentaiton. If my personal life will settle down I plan to do some too. If people already familiar with a code get a head start on it, we'll be that much farther ahead though.Atahualpa wrote:@raevol: Who do you want to recruit for the documentation task? I don't think external people want to start their affiliation with OpenMW writing documentation. Maybe some inactive developers or long-time lurkers are willing to help?
(Make a request in our forums?)
Oh great! I was actually about to offer to help with documentation until I realized you probably meant source documentation, which I don't think I'd be much help in. But if this includes user manuals and tutorials then I'd love to chip in what I can. If this is a legit thing you're going to advertise needing help in, I recommend putting that up on the wiki under How To Contribute.psi29a wrote:No, we mean both. Documentation is a broad term that covers everything from user manuals, to tutorials to source documentation.
This would be very helpful. I read through the documentation thread with DavidD, but if there's any additional outline or direction that you all have, that would probably expedite the process. This sphinx thing seems pretty cool, and I'm relieved I won't have to deal with the ungainly-ness of Latex or html. Would it perhaps be more prudent to use the wiki for user oriented documents though? Personally, if I'm trying to fix something or learn something, that's my first place to go. I'm thinking of about a million more questions, but I'll move them to the Documentation thread to keep from mucking this one up.raevol wrote:Do we have this written up somewhere though? Would be good to be able to direct people interested in doing documentation to one place as a guide for process and standards.
I understand your thoughts, but frankly, this could delay the release of 1.0 with years. The dice roll combat is a core mechanic in Morrowind, and scrapping that system requires implementation of another system. This also means redefining the functions of all the weapon skills.sonicboom12345 wrote: IMO if you're going to include any *one* feature in a 1.0 release that wasn't in vanilla Morrowind, let it be an optional toggle-off for dice roll combat.
Well the beauty of an open source project is that we can have BOTH if someone implements it.MiroslavXO wrote:No, no, I like dice rolls, Morrowind and KOTOR best combat.
