Difference between revisions of "Dev Tools Discussion"
(→Bugzilla) |
(→Issue Trackers) |
||
| Line 21: | Line 21: | ||
Devs have been conditioned to open bugs (in the Bugzilla model) before making a pull request. With the move to GHI, this is unnecessary and generates clutter. | Devs have been conditioned to open bugs (in the Bugzilla model) before making a pull request. With the move to GHI, this is unnecessary and generates clutter. | ||
| + | |||
| + | A suitable workflow for managing security issues is unclear. | ||
==Github== | ==Github== | ||
Revision as of 20:13, 25 June 2014
Discussion at OSBridge 2014 led to the creation of this page, to make points of friction with our current tool set easier to track.
Contents
Communications
Communities
IRC
Issue Trackers
Bugzilla
Basic searches of bug lists are very limited; advanced searches are non-intuitive to set up.
"Upload a patch" option is displayed by default on individual bug pages (is it possible to turn off?): we don't use this, but its presence can be worrying/offputting to new devs who don't yet know to ignore it. However, this functionality can be useful for attaching e.g. specifications, or screenshots of bugs that are difficult to describe in words.
Having to create and immediately close a bug for one-line fixes that have already been written adds complexity for the sake of completeness.
Github Issues
Search of GHI is non-obvious but extant (on issues page, the otherwise site-wide search box searches the issues).
Issue tagging & assignment is only available to accounts with commit access to the repo.
Devs have been conditioned to open bugs (in the Bugzilla model) before making a pull request. With the move to GHI, this is unnecessary and generates clutter.
A suitable workflow for managing security issues is unclear.
