On Tue, Jul 18, 2017 at 8:10 AM, Chris Puttick <firstname.lastname@example.org> wrote:
So if you want to define us as "upstream" we'd be proud to be making a
contribution (but in the end we're just scratching our collective itch
and have found nothing that does it better in the context we work in
(small-medium size deployments on multiple sites)).
If it solves things for you it might be a solution for more people.
We might remove the unused dependent test packages thou depending how the feedback looks like.
We'll review the open bugs on Launchpad and any we are up to
addressing, as sys admins rather than devs ;) , we'll open an issue
report on our fork (and report back to Launchpad once fixed?). Sound
like a way forward?
Sounds great - lets give you a bit of time, lets say 3.5 weeks and sync again on 14th of August.
That hopefully "enough" time for you to go over the issues and get an idea if/how they could be solved.
Also it is still before feature freeze to upload a hopefully much better version there.
If you need assistance on the Launchpad bug processing let me (and probably Serge) know.
Likely initially it is all about commenting on the bugs that you pick (or reject) and linking the github issues that you open.