Bug trackers make people accountable and make it easy for tasks to be delegated and tracked. BUT, someone has to take on the responsibility of assigning bugs as the come in and/or closing bugs/feature requests that aren't going to be developed on any time soon, thus keeping the number of bugs in the tracker manageable.
On Thu, Dec 9, 2010 at 5:06 PM, David Cole <david.c...@kitware.com> wrote: > Hello CMake users and devs, > > (And now for something completely different...) > > Controversial questions: > > - Should we eliminate the bug tracker entirely and just do all > discussion and patches on the mailing list? (Why have two sources of > information...?) > > - Or, alternatively, should we eliminate the bulk of mailing list > traffic, and insist on issues in the bug tracker being the main > conversational forum for the whole community? > > I'd like to have this discussion here publicly, to try to get a good > sense of varous community members attitudes and feelings. > > > I'll start the ball rolling by saying that, personally, I like the bug > tracker. I find it much easier to keep a list of issues organized and > accessible than I can with email filters and folders. But I still see > a need for both tools. > > What do you say? > > > David Cole > Kitware, Inc. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
