You are right. Then the question is which "CLI" should it go to? Seems like
src/cli is superseded by https://github.com/mesosphere/mesos-cli too and
should be on the spring cleaning list? I personally don't mind cli to be
inside the core source tree but it seems like
https://github.com/mesosphere/mesos-cli is more feature complete already.

--
Jiang Yan Xu <[email protected]> @xujyan <http://twitter.com/xujyan>

On Mon, Apr 6, 2015 at 2:46 PM, Benjamin Mahler <[email protected]>
wrote:

> +1 on removing deploy_jar, haproxy+apache, torque.
>
> For mesos-submit, it seems that this should instead be a mesos CLI command.
>
> On Mon, Apr 6, 2015 at 2:04 PM, Vinod Kone <[email protected]> wrote:
>
> > +1
> >
> > On Mon, Apr 6, 2015 at 12:28 PM, Adam Bordelon <[email protected]>
> wrote:
> >
> > > +1 to moving these out to https://github.com/mesos/<framework> even if
> > > they
> > > are used, in which case we should open an issue tracker for each
> separate
> > > project and give write permissions to that repo to anyone willing to
> > > maintain it.
> > >
> > > On Mon, Apr 6, 2015 at 12:10 PM, Yan Xu <[email protected]> wrote:
> > >
> > > > There exist a couple of frameworks in the Mesos codebase under
> > > /frameworks:
> > > > deploy_jar     haproxy+apache mesos-submit   torque
> > > > (See https://github.com/apache/mesos/tree/master/frameworks)
> > > >
> > > > Anyone still uses them?
> > > >
> > > > These frameworks are not trivial implementations like the ones under
> > > > src/examples to demonstrate/test Mesos features and they rely on
> > external
> > > > programs to run. Since we don't actively maintain them, they may have
> > > > already stopped working with the current versions of these programs.
> > > >
> > > > We'd like to remove these from the Mesos repository. If there are
> folks
> > > who
> > > > still use them and would like to contribute, the ideal place to host
> > them
> > > > is in their own repos. e.g., https://github.com/mesos/hadoop
> > > >
> > > > Any comments?
> > > >
> > > > --
> > > > Jiang Yan Xu <[email protected]> @xujyan <http://twitter.com/xujyan>
> > > >
> > >
> >
>

Reply via email to