Identifying Causes of Backlog of old issues

[acrymble]

We've had a gradual buildup of old issues getting stuck for a wide range of reasons. This is a new problem that is worse than we've experienced so far. In order to make sure it doesn't become endemic, I'm opening this ticket and asking our Project Manager at Large @mariajoafana to help identify causes and also to help people responsible for the tickets to action them and complete the tasks or otherwise ask for the help they need in order to do so.

Some of these are active. Others are not.

• Full-text search #1018 Full-text search @ZoeLeBlanc
• Plan S implementation #1370 Plan S Implementation @mdlincoln
• Progress reporting for Lesson Sequences #1525 Progress reporting for Lesson Sequences @amsichani
• Proposal for translation tool #1571 Proposal for translation tool @spapastamkou @rivaquiroga
• Error in Exploring and Analyzing Network Data with Python  #1587 Error in Exploring and Analyzing Network Data with Python @svmelton
• Anna-Maria's Software Sustainability Institute fellowship - collaboration with PH #1633 Anna-Maria's Software Sustainability Institute fellowship - collaboration with PH
• Spanish Copyediting Setup #1635 Spanish Copyediting Setup @acrymble @rivaquiroga
• French Copyediting Setup #1636 French Copyediting Setup @acrymble @spapastamkou
• PH-FR 3M Planning 2020/1 #1642 PH-FR 3M Planning 2020/1 @spapastamkou
• make a cheat-sheet for editors on escaping quotes / special characters #1646 Make a cheat-sheet for editors on escaping quotes / special characters @mdlincoln
• Communicating the Institutional Partner Programme #1658 Communicating the Institutional Partner Programme @jenniferisasi
• FNSO 2019 Call for Funding  #1659 FNSO 2019 Call for Funding @spapastamkou

Please don't regard this as a scolding of any kind, but I would value understanding the reasons some tickets linger and others do not. If it's a matter of not understanding who is responsible for tasks, or forgetting, or not being interested in the task, we really need to know so we can make sure we run efficiently. Thanks everyone.

[jenniferisasi]

On #1658 I am collecting the list of emails and should be able to do it on Monday. I was planning on earlier, as other tech tickets I have, but ... work, and emails on Friday don't have the same reception.

[walshbr]

#1587 was fixed by a PR - but we forgot to close the issue. I closed it.

[acrymble]

I've renamed this ticket to be about 'identifying causes' rather than 'clearing' these tickets. This lets us better understand the sticking points and possible solutions, whether that's forgetting to close a ticket, or having too much one one's plate.

[mariajoafana]

All tickets seem to be moving along, I'll recheck today after our meeting

[acrymble]

It seems like we've been able to learn a few things @mariajoafana that helps us better understand some of the challenges people face closing tickets.

In addition to your support and suggestions to reduce roles to 2, and possibly to bring in help for diagnosing or assessing bugs, is there anything else we want to know or explore? Or should we close this ticket?

[acrymble]

Closing this conversation so we can move ahead with supporting solutions