aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Farrell <>
Subject Re: the status of pesos
Date Tue, 21 Apr 2015 02:29:48 GMT
We only sync reviewboard repos from our git-wip or svn servers. I would
recommend that we move them into aurora-<project> name git repos so they
can have their own release cycles


On Mon, Apr 20, 2015 at 5:50 PM, Brian Wickman <> wrote:

>  I started work in r/32373 <> to add
> pesos <> support for the Aurora executor.
> Pesos is a pure python implementation of the Mesos API.  Adding Pesos
> support to Aurora will pave the way towards "pip install" and the standard
> python packaging toolchain as a means to package/install the Aurora
> executor, without relying upon a cumbersome Mesos build process that is
> predicated on the nuances of libmesos and its myriad dependencies e.g.
> glibc, C++11 and libsvn/apr.
> Pesos and its dependent library, compactor
> <>, are both projects on my personal
> github.  I'd like to keep them independent repositories.  My experience
> shows that vendoring these sorts of things reduces discoverability and
> peoples' willingness to contribute, and increases likelihood of forks.
> That being said, I'm not convinced they should be under my personal github
> either because I'm a poor BDFL
> <> candidate.
> Instead they should either be under the moniker of the mesos github
> organization (there is precedent <> for
> this) or we should create an Aurora organization for third party projects
> that tend to be developed under the Aurora umbrella, e.g. pystachio.
> Regardless of where they live, I think we should immediately start using
> reviewboard to do code reviews for patches.  Does anyone know if this is
> feasible using if the code does not live under the
> apache umbrella?  (The code itself is Apache licensed.)
> ~brian

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message