Hi All, Would it make sense to to make a branch that lived in our fork of the bigtop project (github.com/juju-solutions/bigtop)? That way, we charmers all have commit access, and can grant commit access to those working on a charm. We can then open a sort of mega PR against the Apache bigtop repo, and you can review and merge that when you're ready.
The issue that I see is coordinating upstream merges with downstream additions. Are there points where you want us to freeze the branch while you prepare to merge it? Also, are you proposing that the branch contain just the charms themselves -- the files in in bigtop-packages/src/charms -- or do you want us to include puppet fixes and changes in the branch? I think that it might make a lot of sense to keep all the directly charm related stuff in a branch, but would strongly prefer to keep the puppet related fixes in their own, per ticket, branches. That mega branch is going to get rebased frequently, and I'd rather cut down the chances of conflicts and messiness to a minimum. Regards, ~ PeteVG
