This is currently done by hand, and as such, it's easy for me to lose track of which emeritus requests I've already acknowledged, filed into the received directory, edited various metadata files, and then moving that file again N days later. As such, I've resorted to batching up emeritus requests to file all at once every so often, though this is not ideal as it is easy to lose track of the states of various people, and it is one of the only secretarial duties I have been unable to keep a reasonable SLA for. Note that using Whimsy versus doing this manually require different levels of computer setup; I can easily access the web interface at work, but I don't want to carry around all of Apache on multiple computers just for this one task.
I have recently started receiving several emeritus requests from inactive members after the recent discussions around how long it took to reach quorum. Combined with the handful of existing emeritus requests in various states, this is spinning out of control for me to reasonably handle, especially as I'll be filing several new membership requests soon (which we already have tooling for). I come asking for this feature because I do not have the expertise to implement that feature. The tech stack and domain I work in is so different than Whimsy's that it would sap up all my Apache volunteer time from other PMCs just to familiarize myself with Ruby, Whimsy, and the JavaScript UI. While I would love to be able to contribute, my backlog of Apache-related coding I'm doing stretches well beyond any reasonable response time frame for the numerous requests I've gotten or will get over time. -- Matt Sicker <boa...@gmail.com>
