> Multiple development trackers are evil. The only one of the > "standard" four that get created for a new project which *should* be > separate is the support tracker. Bugs/patches/features should be > coalesced into one thing. The current configuration of the trackers > on SF has more to do with their legacy than anything else. So it was a mistake to fork off a feature tracker? What about MvL's assertion that it's more important to pay attention to patches than to bugs, because patches are people who are trying to contribute, and we want to encourage them? (People submitting bug reports are also trying to help, but arguably they are more interested in *getting* something, e.g. a fix, while patch submittors are clearly *giving*, even if they may not always be 100% altruistic -- some patches are clearly "do it my way" requests.) --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4