I'm not sure I've seen anyone asking for apologies
I haven't seen anyone asking for an apology either. This post was in response to the people who did apologize, not in response to anyone who might have asked for one.
I have seen a lot of requests for increased clarity and comprehensiveness
Skud's post is a wealth of useful constructive criticism and we'll get around to implementing as much of it as we can as soon as we can within the limitations and constraints that we work under. We set up the in-house volunteer system to help train people who don't know how to code. People who already know what they're doing can fork the code and submit pull requests. Which skud has already done. It's one of the main reasons we moved to github.
Is the AO3 code documented anywhere?
The AO3 code is documented in the code. It's not documented very well. If you don't want to wait for us to fix it and would like to fork it and improve its documentation yourself, please, feel free.
no subject
I haven't seen anyone asking for an apology either. This post was in response to the people who did apologize, not in response to anyone who might have asked for one.
I have seen a lot of requests for increased clarity and comprehensiveness
Skud's post is a wealth of useful constructive criticism and we'll get around to implementing as much of it as we can as soon as we can within the limitations and constraints that we work under. We set up the in-house volunteer system to help train people who don't know how to code. People who already know what they're doing can fork the code and submit pull requests. Which skud has already done. It's one of the main reasons we moved to github.
Is the AO3 code documented anywhere?
The AO3 code is documented in the code. It's not documented very well. If you don't want to wait for us to fix it and would like to fork it and improve its documentation yourself, please, feel free.