> While there may be things we can do to bring attention to current bugs, > there's no way we can force someone to fix a particular bug. We do have > mechanisms to try to encourage bux fixing: Bug Days workshops, lists of > tickets on trac....
I hate bug days workshop, it's like you have to spend money to fix bugs. I would almost be better to be paid when you fix a bug :-P (which would mechanically encourage people to produce bugs in the first place :-P) > Certainly making every bug a blocker won't work. Do you have another > suggestion to encourage people to work on bugs? Well. For instance keeping broken doctests in Sage would be nice I think. You would see the bug each time you do a "sage -t" somewhere. But that can confuse newcomers too... That's why I thought that an optional flag for bugs would be nice, because developers could always enable it and see the bugs that do exist. But of course if they do not do it, or if only a few of us add the bugs to the sources, nothing changes... :-/ I'm stuck, because the bugs I have in mind are bugs that I cannot fix. I just can't, I either don't know the maths or the code. Otherwise I would have fixed them already. And I am stuck because I hate to see them stay around :-/ Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
