Hi,
Another obvious solution is:
Think before adding new issues.
We should use more often the dev list (not private emails). A lot of discussions should be done in dev list rather than in issues. For instance, I think that the recent issue #588 opened by Houtan has nothing to do in Github's issues and should rather be discussed on the mailing list.
I am not convinced by the efficiency of synchronous discussions (IRC meetings).
Best, Stéphane.
On 27/01/2014 17:19, Sébastien Villemot wrote:
Hi,
I am getting concerned about the number of outstanding GitHub issues against Dynare. As of now, there are 133 outstanding issues, and this number is following an upward trend.
I think that having the number of issues growing too big has a negative impact, because it makes it more difficult to figure out what are the really relevant issues and act on them. It also diminishes the perceived usefulness of filing an issue, since there is a significant probability that there will be no follow up.
I am therefore wondering what would be the possible solutions to bring down the number of opened issues. I can see at least:
- Have developers deal more diligently with issues that are assigned to
them (or otherwise mark them as unassigned)
Have developers pick up more unassigned issues
Hold meetings (as we did last year on IRC) to discuss issues for
which a collective decision is needed
- Acknowledge that we do not have enough resources to deal with some
issues, and close them (this probably also needs collective decisions)
- Organize bug squashing parties
Obviously items 1 and 2 are not something that we can decide as a group, but I included them for completeness and as a reminder for everyone.
What is your opinion on items 3, 4 and 5? Do you have other ideas?
Best,
Dev mailing list Dev@dynare.org https://www.dynare.org/cgi-bin/mailman/listinfo/dev