Backwards development

[Gervase Markham]

Hi Denis,

On 20/11/15 16:15, Denis Roy wrote:
> We've been through this at Eclipse, where many projects had dwindling
> communities and near-zero external contributions, but we've been able to
> help turn that around using modern contribution models (GitHub, Git,
> Gerrit), modern methodologies and careful coaching of projects.

It would be wonderful if someone had the cycles to do this for Bugzilla.
I'd like to, but I just don't have the hours.

We already use Git, and mirror to Github.

> Perhaps if Bugzilla is serious about being an independent software
> project, it should consider moving to an independent software
> foundation. 

I don't see how being part of Mozilla is actively holding Bugzilla back.
Moving to an independent foundation is not going to cause the BMO team
to suddenly have lots of time to port things upstream. Am I missing
something?

> As it stands, Mozilla is not living up to its manifesto wrt.
> Bugzilla, specifically:
> 
> 08 Transparent community-based processes promote participation,
> accountability and trust.
> 
> https://www.mozilla.org/en-US/about/manifesto/

I don't agree that this is true. The Bugzilla project has a transparent,
community-based contribution process. I don't think the Mozilla
manifesto requires Mozilla to upstream every patch it writes to an open
source codebase, although I agree it's more unusual if that codebase is
itself a Mozilla project.

Gerv