Here's my own, personal minority report: I think that a separate repo
will complicate your build and release process and will fracture your
nascent community. That said...
On Mon, Jan 16, 2017 at 3:58 PM, Jacob Barrett <jbarr...@pivotal.io> wrote:
> Mark,
>
> Looks like we have lots of votes for your separate repo idea. What do we
> need to do to get that going?
This is a self-managing thing. Here's the tool:
https://reporeq.apache.org/
> On that note too, do you know who we need to ping to get a build going?
Did I mention complications to build and release process? ;-)
At any rate -- there's nobody to ping -- it'll be you Jacob (or whoever
else is signing up to hack on the Native client). Mark can give you
Jenkins karma tho:
https://wiki.apache.org/general/Jenkins#How_do_I_get_an_account
> I would suggest we target Linux first since it is the easiest. The tools
> necessary can be found in the src/BUILDING.md file.
That's very much up to whoever is doing the actual work, but it sounds
reasonable.
Thanks,
Roman.
