[split] OAPtFatSotC > narfnin Document Maintainer

[narfnin]

I was trying to make an ares mod, but had a problem with LB. But enough of that.


I would be willing to work (preferable co-work) on the Manual/Readme when I have time. If nobody's volunteered yet, count me in. If someone has, see if they'll want me to help. I would love to help make Ares more user-friendly and easy to understand.


HOWEVER!! I would not be able to work daily. What I would like, if it would work for you guys, is to just e-mail me when there's things that need documentation.


IE: You guys finished coding a new feature. Let me know how it works, and I'll edit the manual with it and, once tested, post what exactly happens that wasn't planned and/or in more detail. However, I would probably need someone else to test unless my mysterious problem was solved.

So, TL;DR, I would be willing to be the/a Documentation Maintainer, provided I am notified when something needs documenting.

[Graion Dilach]

Narfnin, what's your problem with Launch Base?

I use LB daily, even used it to give out private beta mods... so I think I can help with that.

EDIT: Dammit, I misremembered you.

[Renegade]

Nighthawk, as the Project Manager, is managing the ACSC, though I will say that remembering to continuously e-mail you whenever we need a change would probably be just as much work as updating the manual ourselves.

[Nighthawk]

narfnin, I'm afraid I'm going to have to turn down your request. Primarily, I'm saying no because (as Renegade says) your method of getting updates through to the documentation is just as much work as if it was just done by the developers manually, and that would merely amplify the documentation problem, as opposed to solve it.