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
On 24 June 2015 at 10:55, Yan Xu y...@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
(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
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
+1!
On Tue, Jun 23, 2015 at 4:31 PM, Yan Xu y...@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
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 y...@jxu.me wrote:
So I'd like to resurface this topic. The last attempt
https://reviews.apache.org/r/33090/ to remove
Hi All,
This brings up a larger issue of governance around the mesos GitHub org;
how is this managed, and what is its relationship it has to the Apache
project. Concerns from members of the Apache community have previously
been expressed regarding this, and I'm hesitant to see us move portions
of
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
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
+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 y...@jxu.me wrote:
There
+1
On Mon, Apr 6, 2015 at 12:28 PM, Adam Bordelon a...@mesosphere.io 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
+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 vinodk...@apache.org wrote:
+1
On Mon, Apr 6, 2015 at 12:28 PM, Adam Bordelon a...@mesosphere.io wrote:
+1 to moving
12 matches
Mail list logo
