tl;dr: it is only a matter of time before the infrastructure team notice
that mlreq is hosted on a vm that is set to be decommissioned, and sebb
notices that mlreq is currently using an old version of the whimsy/asf gem.
Let's fix the above before it is a problem.
Originally, whimsy was a playground, and when things got to the point
where people depended on them I worked with the infrastructure staff and
those tools would 'graduate' and become owned by the infrastructure team.
Since then, whimsy has become a PMC, the infrastructure contractors that
were involved in this exercise are no longer active, and the current
contractors are now focused on SLAs, and do what is expected of people
who are tracked by SLAs do: move the issues states like 'planned
enhancements', and buck questions about ownership to management.
Despite asking this question a number of times, I've never gotten a
response. It is time for the PMC as a whole to ask this question.
At the moment, this email is focused on a single tool. My opinion is
that there is a larger problem of single developer code bases. The
whimsy PMC is making slow but steady progress here; but there are plenty
of other codebases that aren't -- some of which aren't even under
revision control or under automated deployment.
Thoughts?
See also:
https://issues.apache.org/jira/browse/INFRA-11502
- Sam Ruby
