Solve bugs on a timeframe depending on the priority


I was checking bugs reported. There are critical bugs that were not solved for versions as old as 2.0 (LTS). They wasn't even a reason about why they were not solved or what was needed for them to be solved.

It is critical not to leave the user alone. In the worst of all it cases, we should ask for a monetary or some other sort of contribution in exchange for the solution of the problem that is reported (unless they ask to include non-free software).

In order to have this done and have the responsible people in charge we to assign value to the work of all people that promote, fix or develop Trisquel. The value assigned must not be in money but in time. Depending on the time invested in favour of Trisquel, each of us will have a "time balance" on our "time account". That balance can be payed if it is negative or withdrawn if it is positive. We can pay by doing work for Trisquel and withdraw by asking for work to be done.

Do you think this is a viable means to solve issues here reported?

Dom, 06/03/2012 - 00:35

I see a few issues related to this problem.

1) Many issues reported on the bug tracker would be better reported elsewhere. Take for example (and I'm not trying to single anyone out since this is happening a lot) of this issue. A little research would show that this bug has already been reported upstream in 2 places (Ubuntu and the program's own bug tracker). Secondly, this is just a minor package in Trisquel not a core component. Yet I had to take the time to track down those upstream reports and link them to that issue report. This issue should have never been made in the first place. The same goes for this issue here. Ubuntu and Debian already have bug reports on it. Eventually the issue will be fixed upstream and make it's way into Trisquel and we don't have to do anything. But now that it is there we have to track and monitor it. Which brings me to my second point.

2) We don't have enough dev/volunteer help. According to the other issue (about not having 100 members) quidam says he is making about 400 euros or 500 dollars a month from membership dues. That isn't a ton. I know rent varies everywhere but that wouldn't even cover my rent. We can barely afford one dev. In fact I would say we are under-paying him because he deserves way more. Because of this we can't look into every single bug in every single program (issue I mentioned above). Thus we should have some rules about posting issues to the issue tracker.

I have written a rough-draft of some rules to increase the efficiency of how we manage issues on the issue tracker. Please give your comments on it.

So I see the solution going a couple ways:

  • We need more money for more paid devs to handle the bugs
  • We need more support from volunteers to contribute
  • We need more regulation on what can be considered an issue. This could include support issues being re-directed to the forum and non-core issues being re-directed upstream.
  • Some combination of the above.
Lun, 05/04/2015 - 17:38