[GitHub] mesos issue #179: Added a new title to the existing list

[packtpartner]

Github user packtpartner commented on the issue:

https://github.com/apache/mesos/pull/179
  
and merge the request to the documents page


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #179: Added a new title to the existing list

[packtpartner]

Github user packtpartner commented on the issue:

https://github.com/apache/mesos/pull/179
  
can u push the request? @liorze 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #179: Added a new title to the existing list

[liorze]

Github user liorze commented on the issue:

https://github.com/apache/mesos/pull/179
  
Sure, what can I do for you? 
Just letting you know, I'm not a committer in this project.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #179: Added a new title to the existing list

[packtpartner]

Github user packtpartner commented on the issue:

https://github.com/apache/mesos/pull/179
  
Hi @liorze  I have added a new book in the documentation section, can you 
help me with it?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #179: Added a new title to the existing list

[packtpartner]

GitHub user packtpartner opened a pull request:

https://github.com/apache/mesos/pull/179

Added a new title to the existing list 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/packtpartner/mesos patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/179.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #179


commit b7d1d1900c8006c64cec44b6a375ab702388e0ff
Author: Packt 
Date:   2016-11-10T06:19:31Z

Update home.md




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Mesos Documentation Project

[James Peach]

> On Nov 9, 2016, at 4:29 PM, James Neiman  wrote:
> 
> Dear Mesos Users, Operators, Developers, and Contributors:
> 
> My name is James Neiman. I have been working with Benjamin Hindman, Artem
> Harutyunyan, Neil Conway, and Joseph Wu on improving the Mesos
> documentation. We now have a proposal for the community to critique.
> 
> Our goal is to satisfy the needs of Operators, Developers, and Contributors
> by:
> 
>   - Revising, restructuring, and expanding existing topics.
>   - Authoring new topics, such as *Quick Start* and *What is Mesos?*.
>   - Reorganizing the table of contents.
>   - Providing role-specific views of the table of contents.
> 
>   *Please note that versioning of the documentation will be addressed in a
> separate project.*
> 
> This will be an iterative process. Your feedback and contributions are very
> important to making this project a success!
> 
> I will follow up very soon with a request for your comments on proposed
> changes. I look forward to your feedback.

Is the proposal github PR that Joseph linked, or is there more? Is there a 
rendered version of the PR available anywhere?

Are the “intallation-$platform.md” named intentionally, or the result of a 
typo? A lot of the headings on these pages have a trailing ‘]’. Is that markup 
or typo?

Did you consider switching to a more full-featured docs toolchain (I have had 
good experiences with sphinx) that can generate man pages, indices, TOC, 
cross-references, search, etc?

thanks,
James

Re: 答复: Mesos Documentation Project

[tommy xiao]

it's all good way for mesos community.  thanks a lot.

2016-11-10 9:32 GMT+08:00 Joseph Wu :

> Because of the heavy amount of markdown changes, this proposal will live
> in a Github PR [1], which is presumably reachable.  We may also consider,
> as part of this project, migrating design documents for existing features
> off GoogleDocs and into markdown, so that they can live in the
> documentation too.
>
> That being said, you can usually use a VPN to bypass the "network
> limitations" ;)
>
> [1] https://github.com/apache/mesos/pull/178
>
>
> On Wed, Nov 9, 2016 at 5:03 PM, pangbingqiang 
> wrote:
>
>> It is really cool, but now mesos desigin doc on googledoc, china users
>> can not enter in to download because of network limitations.
>>
>> -邮件原件-
>> 发件人: James Neiman [mailto:jneima...@mesosphere.io]
>> 发送时间: 2016年11月10日 8:30
>> 收件人: dev@mesos.apache.org
>> 主题: Mesos Documentation Project
>>
>> Dear Mesos Users, Operators, Developers, and Contributors:
>>
>> My name is James Neiman. I have been working with Benjamin Hindman, Artem
>> Harutyunyan, Neil Conway, and Joseph Wu on improving the Mesos
>> documentation. We now have a proposal for the community to critique.
>>
>> Our goal is to satisfy the needs of Operators, Developers, and
>> Contributors
>> by:
>>
>>- Revising, restructuring, and expanding existing topics.
>>- Authoring new topics, such as *Quick Start* and *What is Mesos?*.
>>- Reorganizing the table of contents.
>>- Providing role-specific views of the table of contents.
>>
>>*Please note that versioning of the documentation will be addressed in
>> a separate project.*
>>
>> This will be an iterative process. Your feedback and contributions are
>> very important to making this project a success!
>>
>> I will follow up very soon with a request for your comments on proposed
>> changes. I look forward to your feedback.
>>
>> Sincerely,
>>
>>
>> James Neiman
>>
>> Technical Writing Consultant, Mesosphere
>>
>> jneima...@mesosphere.io
>>
>
>


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: 答复: Mesos Documentation Project

[Joseph Wu]

Because of the heavy amount of markdown changes, this proposal will live in
a Github PR [1], which is presumably reachable.  We may also consider, as
part of this project, migrating design documents for existing features off
GoogleDocs and into markdown, so that they can live in the documentation
too.

That being said, you can usually use a VPN to bypass the "network
limitations" ;)

[1] https://github.com/apache/mesos/pull/178

On Wed, Nov 9, 2016 at 5:03 PM, pangbingqiang 
wrote:

> It is really cool, but now mesos desigin doc on googledoc, china users can
> not enter in to download because of network limitations.
>
> -邮件原件-
> 发件人: James Neiman [mailto:jneima...@mesosphere.io]
> 发送时间: 2016年11月10日 8:30
> 收件人: dev@mesos.apache.org
> 主题: Mesos Documentation Project
>
> Dear Mesos Users, Operators, Developers, and Contributors:
>
> My name is James Neiman. I have been working with Benjamin Hindman, Artem
> Harutyunyan, Neil Conway, and Joseph Wu on improving the Mesos
> documentation. We now have a proposal for the community to critique.
>
> Our goal is to satisfy the needs of Operators, Developers, and Contributors
> by:
>
>- Revising, restructuring, and expanding existing topics.
>- Authoring new topics, such as *Quick Start* and *What is Mesos?*.
>- Reorganizing the table of contents.
>- Providing role-specific views of the table of contents.
>
>*Please note that versioning of the documentation will be addressed in
> a separate project.*
>
> This will be an iterative process. Your feedback and contributions are
> very important to making this project a success!
>
> I will follow up very soon with a request for your comments on proposed
> changes. I look forward to your feedback.
>
> Sincerely,
>
>
> James Neiman
>
> Technical Writing Consultant, Mesosphere
>
> jneima...@mesosphere.io
>

Re: [2/2] mesos git commit: Added MESOS-6142 to CHANGELOG for 1.1.1.

[Benjamin Mahler]

We wouldn't normally create the 1.1.x branch before 1.1.0 is released. If
1.1.0 doesn't go through this branch needs to be rebased and force pushed?

On Tue, Nov 8, 2016 at 1:56 PM,  wrote:

> Added MESOS-6142 to CHANGELOG for 1.1.1.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/550d13c3
> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/550d13c3
> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/550d13c3
>
> Branch: refs/heads/1.1.x
> Commit: 550d13c3dffe4d3b86c74ca40fb539796cefd848
> Parents: 0023d38
> Author: Alexander Rukletsov 
> Authored: Tue Nov 8 22:57:24 2016 +0100
> Committer: Alexander Rukletsov 
> Committed: Tue Nov 8 22:57:24 2016 +0100
>
> --
>  CHANGELOG | 4 
>  1 file changed, 4 insertions(+)
> --
>
>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/550d13c3/CHANGELOG
> --
> diff --git a/CHANGELOG b/CHANGELOG
> index a305da1..28bc827 100644
> --- a/CHANGELOG
> +++ b/CHANGELOG
> @@ -2,6 +2,10 @@ Release Notes - Mesos - Version 1.1.1 (WIP)
>  ---
>  * This is a bug fix release.
>
> +All Issues:
> +** Bug
> +  * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
> +
>
>  Release Notes - Mesos - Version 1.1.0
>  -
>
>

答复: Mesos Documentation Project

[pangbingqiang]

It is really cool, but now mesos desigin doc on googledoc, china users can not 
enter in to download because of network limitations.

-邮件原件-
发件人: James Neiman [mailto:jneima...@mesosphere.io] 
发送时间: 2016年11月10日 8:30
收件人: dev@mesos.apache.org
主题: Mesos Documentation Project

Dear Mesos Users, Operators, Developers, and Contributors:

My name is James Neiman. I have been working with Benjamin Hindman, Artem 
Harutyunyan, Neil Conway, and Joseph Wu on improving the Mesos documentation. 
We now have a proposal for the community to critique.

Our goal is to satisfy the needs of Operators, Developers, and Contributors
by:

   - Revising, restructuring, and expanding existing topics.
   - Authoring new topics, such as *Quick Start* and *What is Mesos?*.
   - Reorganizing the table of contents.
   - Providing role-specific views of the table of contents.

   *Please note that versioning of the documentation will be addressed in a 
separate project.*

This will be an iterative process. Your feedback and contributions are very 
important to making this project a success!

I will follow up very soon with a request for your comments on proposed 
changes. I look forward to your feedback.

Sincerely,


James Neiman

Technical Writing Consultant, Mesosphere

jneima...@mesosphere.io

[GitHub] mesos pull request #178: WIP: Mesos Documentation Project Reorg Proposal

[jneimanmesos]

GitHub user jneimanmesos opened a pull request:

https://github.com/apache/mesos/pull/178

WIP: Mesos Documentation Project Reorg Proposal

This is an initial proposal for reorganizing the Mesos Documentation. 

Our goal is to satisfy the needs of Operators, Developers, and Contributors 
by:

  - Revising, restructuring, and expanding existing topics.
  - Authoring new topics, such as _Quick Start_ and _What is Mesos?_.
  - Reorganizing the table of contents.
  - Providing role-specific views of the table of contents.





You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jneimanmesos/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/178.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #178


commit cde169aaf4ececdf5d9138ed3807f4824d3d8806
Author: jneimanmesos 
Date:   2016-11-10T00:55:30Z

Mesos Documentation Project Reorg Proposal




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Mesos Documentation Project

[James Neiman]

Dear Mesos Users, Operators, Developers, and Contributors:

My name is James Neiman. I have been working with Benjamin Hindman, Artem
Harutyunyan, Neil Conway, and Joseph Wu on improving the Mesos
documentation. We now have a proposal for the community to critique.

Our goal is to satisfy the needs of Operators, Developers, and Contributors
by:

   - Revising, restructuring, and expanding existing topics.
   - Authoring new topics, such as *Quick Start* and *What is Mesos?*.
   - Reorganizing the table of contents.
   - Providing role-specific views of the table of contents.

   *Please note that versioning of the documentation will be addressed in a
separate project.*

This will be an iterative process. Your feedback and contributions are very
important to making this project a success!

I will follow up very soon with a request for your comments on proposed
changes. I look forward to your feedback.

Sincerely,


James Neiman

Technical Writing Consultant, Mesosphere

jneima...@mesosphere.io

Re: [VOTE] Release Apache Mesos 1.1.0 (rc3)

[Zhitao Li]

+1 (non-binding)

Tested with ROOT and docker on debian jessie.

On Mon, Nov 7, 2016 at 2:19 PM, Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI.
>
> *Revision*: a44b077ea0df54b77f05550979e1e97f39b15873
>
>- refs/tags/1.1.0-rc3
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)/>
> [image: Not run]
> cmake
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> 7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Not run]
> --verbose autotools
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Not run]
> cmake
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)/>
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)/>
> cmake
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> --verbose autotools
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Success]
>  Release/23/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> cmake
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
> [image: Success]
>  Release/23/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/>
>
> On Mon, Nov 7, 2016 at 7:49 AM, Evers Benno  wrote:
>
> > +1 (non-binding)
> >
> > Built and installed on Ubuntu 10.04 + 14.04
> >
> > Configured with --disable-java --enable-python --disable-bundled-pip
> > --disable-python-dependency-install
> >
> > On 04.11.2016 14:15, Till Toenshoff wrote:
> > > Hi all,
> > >
> > > Please vote on releasing the following candidate as Apache Mesos 1.1.0.
> > >
> > >
> > > 1.1.0 includes the following:
> > > 
> > 
> > >   * [MESOS-2449] - **Experimental** support for launching a group of
> > tasks
> > > via a new `LAUNCH_GROUP` Offer operation. Mesos will guarantee that
> > either
> > > all tasks or none of the tasks in the group are delivered to the
> > executor.
> > > Executors receive the task group via a new `LAUNCH_GROUP` event.
> > >
> > >   * [MESOS-2533] - **Experimental** support for HTTP and HTTPS health
> > checks.
> > > Executors may now use the updated `HealthCheck` protobuf to
> implement
> > > HTTP(S) health checks. Both default executors (command and docker)