1. 8
  1. 2

    Oh noes, problem loading data. HTTP 403 forbidden.

    But, it’s assuming the metric is of any relevance, and I think it’s not. An SMT solver and a curated lists of lolcat macro generators are going to have issues of completely different nature and complexity. In large scale projects there are many reasons to have open issues for a long time, from need for extensive testing and review, to leaving cosmetic issues for later when there are more pressing ones, to avoiding a fix for a special case when a fix for a whole class of issues is already in the works.

    I’ve seen projects that close issues that no one reacted to in a few weeks. Saying such a project has short issue closing time is, to put it politely, bullshit.

    1. 1

      it’s assuming the metric is of any relevance, and I think it’s not.

      I agree, it should be acceptable for projects to have issues open for any length of time as there are many good reasons why certain issues will grow grey hairs.

      I shared the project primarily because its source code looked “interesting” and it uses a framework called Mavo that I wasn’t familiar with.