Re: contributing pain points (was: Re: New REST API - motivation)
Damien <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.bugzilla.devel |
|---|---|
| Message-ID | <CAAe5jyMXUxLjsdP-Ht_Lv66gTa-Wt_Uky+gjus951-0wp=Varg@mail.gmail.com> |
On Fri, Dec 5, 2014 at 5:01 PM, Mark Côté <[email protected]> wrote: > On 2014-12-05 3:36 PM, Damien wrote: > > however the current "contribution" workflow is a pain for folks that > > actually want to contribute. > > I would love to hear more on this. One of my goals as Assistant Project > Lead is to increase the number of contributors, which in turn requires > that contributing be relatively painless. > > I have had much better user experience with bitbucket and github service. One thing github got right is how continuous integration systems (travis-ci, jenkins and others) can test pull requests and tell you if your changes would pass or break the tests. obsoleting patches is easy as well (updating the pull-request branch). You can also look at gerrit which many communities use. https://www.mediawiki.org/wiki/Gerrit/Tutorial I personally don't like the user interface, but the tooling is nice. _______________________________________________ dev-apps-bugzilla mailing list [email protected] https://lists.mozilla.org/listinfo/dev-apps-bugzilla - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>