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
-Jake On Mon, Apr 20, 2015 at 5:50 PM, Brian Wickman <[email protected]> wrote: > I started work in r/32373 <https://reviews.apache.org/r/32373/> to add > pesos <https://github.com/wickman/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 > <https://github.com/wickman/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 > <http://en.wikipedia.org/wiki/Benevolent_dictator_for_life> candidate. > Instead they should either be under the moniker of the mesos github > organization (there is precedent <https://github.com/mesos/mesos-go> 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 reviews.apache.org if the code does not live under the > apache umbrella? (The code itself is Apache licensed.) > > ~brian >
