<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> In case it wasn't clear, I am officially volunteering to assist with clearing out the backports queue. I have been working with the Server Team specifically with NGINX since 2014, but I am well versed in Ubuntu policies and how package processes work, and would like to volunteer to be part of the backporters team to help clear out the pending backports queues. This way, Backports can be seen as a potentially viable method of getting newer software features into older releases where SRUs are not a viable solutions. Thomas <div class="moz-cite-prefix">On 11/29/18 12:07 PM, Thomas Ward wrote: </div> <blockquote type="cite" cite="mid:f4274ecf-e566-5948-6bb6-a69399808747@ubuntu.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> I took a look at the backports projects today, and the queues there. The backports queues seem to be pretty siaable, and nobody's really taking the time to take a look at them (73 in Xenial backports, 11 in Bionic, 100+ in Trusty, etc.). I haven't taken a look in-depth on the backport requests yet, but the key thing I am seeing is that all the backporters are otherwise occupied in working on other tasks. If the problem is nobody is stepping up to volunteer to take a peek, the question then becomes is it just a lack of volunteers with the proper knowledge, or is it a lack of people wanting to take a look, or is it a lack of volunteers with the proper permissions to do the backports? (I'd be willing to volunteer some of my time out of each week (probably weekends in my case) to poke at the backports queues if I were considered an acceptable member for the team) It'd also be nice to see what requirements are needed to consider someone to be a backporter, the documentation on this seems nonexistent as does process documentation. Thomas </blockquote> </body> </html>