mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yan Xu <...@jxu.me>
Subject Re: Regarding old frameworks in Mesos repository
Date Tue, 07 Jul 2015 18:31:17 GMT
The cleanup has been committed:
https://issues.apache.org/jira/browse/MESOS-2640.

Jake,
Is it still against ASF policy if these frameworks are moved under
github.com/mesos but we make it very clear we are not taking contributions
to these repos and they are read-only? People can still fork them just like
they can fork github.com/apache/mesos but I don't think it's our intention
to block that right?

--
Jiang Yan Xu <yan@jxu.me> @xujyan <http://twitter.com/xujyan>

On Wed, Jun 24, 2015 at 3:48 PM, Marco Massenzio <marco@mesosphere.io>
wrote:

> +1
> for deleting obsolete / unmaintained code
> (this is also a great courtesy to newbies who feel like they wasted time
> learning/reading code that they're then told is out-of-date)
>
> One of the great things about using git is that we can resurrect them (or
> parts thereof) at any time, should we wish to do so: where to "graveyard"
> them I would argue is sort of already implied here, and it's in this repo.
>
> Thanks for offering to do this!
>
> *Marco Massenzio*
> *Distributed Systems Engineer*
>
> On Wed, Jun 24, 2015 at 11:05 AM, Niklas Nielsen <niklas@mesosphere.io>
> wrote:
>
> > On 24 June 2015 at 10:55, Yan Xu <yan@jxu.me> wrote:
> >
> > > If we anticipated further development we wouldn't have proposed moving
> > them
> > > out. :)
> > > So I think it's safe to say that we are just looking for a graveyard
> for
> > > them. Do the policies still apply?
> > > That said, if they cannot be moved out, we should still just delete
> them
> > > and point to the commit in which they are deleted.
> > >
> >
> > +1
> >
> >
> > >
> > > Most of the discussions around this are on this thread. Relevant notes
> > from
> > > the community sync are in this google doc
> > > <
> > >
> >
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit
> > > >
> > > (June
> > > 4). It's not about ec2 maintenance as the scripts in this repo are not
> > > up-to-date and and people have created ec2 tools not based on these
> > > scripts. (See this
> > > <
> > >
> >
> http://mail-archives.apache.org/mod_mbox/mesos-dev/201505.mbox/%3CCAK8jAgMtmdeTskCKQmwatYAB3DMAUTSXo5p+6p2F2S2k-zTArw@mail.gmail.com%3E
> > > >
> > > .)
> > >
> > > Yan
> > >
> > > --
> > > Jiang Yan Xu <yan@jxu.me> @xujyan <http://twitter.com/xujyan>
> > >
> > > On Tue, Jun 23, 2015 at 7:18 PM, Jake Farrell <jfarrell@apache.org>
> > wrote:
> > >
> > > > (infra hat on) This can not be just shifted to a random github org
> and
> > > > still be maintained under the Apache Mesos project. All commits must
> > > occur
> > > > to Apache hardware before going to any mirrors such as github, which
> > > > currently does not support anything not under the Apache github org.
> > > >
> > > > (Mesos hat back on) Sorry I missed the last sync up, I did not see
> any
> > > > notes from this brought back to the dev list. If there is a need for
> > > > maintainers for the ec2 section of the code base I would be happy to
> > step
> > > > in and help either rework to cloudformation or answer any outstanding
> > > > questions
> > > >
> > > > -Jake
> > > >
> > > >
> > > >
> > > > On Tue, Jun 23, 2015 at 9:26 PM, Erik Weathers <
> eweathers@groupon.com>
> > > > wrote:
> > > >
> > > > > Please maintain the git history for the files when you move them.
> > They
> > > > > should not all appear to have been born into the new repos...
> > > > >
> > > > > - Erik
> > > > >
> > > > > On Tuesday, June 23, 2015, Yan Xu <yan@jxu.me> wrote:
> > > > >
> > > > > > So I'd like to resurface this topic. The last attempt
> > > > > > <https://reviews.apache.org/r/33090/> to remove things
under
> > > > frameworks/
> > > > > > was put off because scripts under ec2/ still reference these
> > > > frameworks.
> > > > > >
> > > > > > However we seem to have reached the consensus that these
> > unmaintained
> > > > > code
> > > > > > need to be moved out to avoid confusion (People asking questions
> /
> > > > > > reporting errors for things we don't maintain anymore). This
> point
> > > was
> > > > > > reiterated during our last community sync and we decided to
> remove
> > > ec2/
> > > > > > folder as well.
> > > > > >
> > > > > > Therefore, if there's no objection, I will delete these files
and
> > > > > recreate
> > > > > > them as individual projects under github.com/mesos. Our website
> > will
> > > > be
> > > > > > updated with the links to them either deleted or replaced by
> > similar
> > > > > > external projects.
> > > > > >
> > > > > > --
> > > > > > Jiang Yan Xu <yan@jxu.me <javascript:;>> @xujyan
<
> > > > > > http://twitter.com/xujyan>
> > > > > >
> > > > > > On Fri, Apr 10, 2015 at 2:39 AM, Alexander Rojas <
> > > > > alexander@mesosphere.io
> > > > > > <javascript:;>>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 If they are not maintain they should be somewhere else.
> > > > > > >
> > > > > > > > On 06 Apr 2015, at 21:10, Yan Xu <yan@jxu.me <javascript:;>>
> > > > 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 <yan@jxu.me <javascript:;>>
@xujyan <
> > > > > > http://twitter.com/xujyan>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

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