[fab] Re: "community maintainers working on core" dilemma

[Christopher Blizzard <blizzard redhat com>]

Thorsten Leemhuis wrote:
> Agreed.
>
> [...]
> > The next question, then: what processes can we put in place that will
> > allow trusted community developers to submit patches in a "fast track"  
> > way, such that the official RH maintainer can simply take a quick look,
> > rebuild, and release?
>
> My preferred variant:
>
> 1. community developer commits his changes to a version control system
> somewhere
> 2. he sends some kind of pull request to the red hat maintainer
> 3. red hat maintainer looks at the changes
> 3a) he doesn't like them -- he mails the community maintainer some
> reasons why he doesn't like them
> 3b) he likes them -- he pulls them and queues build

I think that we could actually remove some steps here.  We need to make 
it so incredibly easy to link developers, fixers, testers and 
maintainers that the bar to fixing something is always about waiting on 
people and never about fighting with technology or wading through bugzilla.

> > It could be as simple as adding a keyword to bugzilla.
>
> "bugzilla != simple" for a lot of people.

Bugzilla is a godawful disaster.

--Chris