Roan Kattouw wrote:
So mostly, I think our immediate problems are:
* no agreed-upon strategy to tackle the problem (what do y'all think
about mine?)
* not enough man-hours spent on keeping up with new commits
** ...presumably because employed people aren't given the time to work
on it and/or made to work on it
I think your analysis and implementation strategy are both fine. The issue
seems to be, plainly, that nobody is forced to do code review in order to
reduce the backlog. When they are (think of the period directly before the
1.17 deployment), it gets done. This is largely what I was talking about
yesterday with deadlines and being forced to meet obligations.
This topic has come up several times and each time, it seems like the people
with any kind of power are conspicuously absent. Where is Danese? Is she
subscribed to this list? Is she reading it? I'm not sure how it's really
possible for this issue to keep coming up and for the situation to not ever
be improved. We're not talking about a new Apollo program; this is mostly
PHP code development. What's the issue here and how can it be resolved once
and for all so that we can stop having these repetitive threads?
** ...and because some of our reviewers are college
students working
part-time (fortunately I'll graduate soon and have more time :D)
Not to be cynical, but there's no doubt in my mind that when you have more
free time, you'll be tasked to work on further "high priority" (but very
low
impact) tasks like ArticleFeedback (or whatever the new pet project is in a
few months).
MZMcBride