Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Linkernetworks into powered-by-mesos.md #54

Closed
wants to merge 4 commits into from

Conversation

usultrared
Copy link
Contributor

please approve us , appreciated

@usultrared
Copy link
Contributor Author

please approve it .thanks

@haosdent
Copy link
Member

haosdent commented Aug 7, 2015

This document is sorted by dictionary order, could you put it after

@haosdent
Copy link
Member

haosdent commented Aug 7, 2015

And I think @davelester could help you merge this.

please approve it ,thanks.
@usultrared
Copy link
Contributor Author

haosdent,
Done . #54

On Fri, Aug 7, 2015 at 12:30 PM, haosdent notifications@github.com wrote:

This document is sorted by dictionary order, could you put it after


Reply to this email directly or view it on GitHub
#54 (comment).

@usultrared
Copy link
Contributor Author

@davelester https://github.com/davelester
appreciated . #54

On Fri, Aug 7, 2015 at 12:34 PM, haosdent notifications@github.com wrote:

And I think @davelester https://github.com/davelester could help you
merge this.


Reply to this email directly or view it on GitHub
#54 (comment).

@haosdent
Copy link
Member

haosdent commented Aug 7, 2015

👍

@usultrared
Copy link
Contributor Author

Haosdent ,
Looks like its still pending . May I know how to speed this up ?
appreciated .

On Fri, Aug 7, 2015 at 12:57 PM, haosdent notifications@github.com wrote:

[image: 👍]


Reply to this email directly or view it on GitHub
#54 (comment).

@haosdent
Copy link
Member

Maybe @davelester is busy with MesosConf now, let me help you @mpark .

@mpark
Copy link
Member

mpark commented Aug 10, 2015

@usultrared: I was about to commit this but I wanted to confirm that you want Linkernetworks, rather than LinkerNetworks or Linker Networks? From www.linkernetworks.com it seems like the last one would be preferred?

@usultrared
Copy link
Contributor Author

Very appreciated .
Btw, we developed so much code and incubated one project ,
Could you please direct me and let me know how to deeply involve into this
community .
For example , we improved Marathon etc.

On Mon, Aug 10, 2015 at 12:40 PM, haosdent notifications@github.com wrote:

Maybe @davelester https://github.com/davelester is busy with MesosConf
now, let me help you @mpark https://github.com/mpark .


Reply to this email directly or view it on GitHub
#54 (comment).

@usultrared
Copy link
Contributor Author

@park , its Linkernetworks. thanks.

On Mon, Aug 10, 2015 at 2:21 PM, Michael Park notifications@github.com
wrote:

@usultrared https://github.com/usultrared: I was about to commit this
but I wanted to confirm that you want Linkernetworks, rather than
LinkerNetworks or Linker Networks? From www.linkernetworks.com it seems
like the last one would be preferred?


Reply to this email directly or view it on GitHub
#54 (comment).

@mpark
Copy link
Member

mpark commented Aug 10, 2015

@usultrared: I've committed the patch to master. Could you please close this PR?

In terms of involvement with the community, what type of involvement are you looking for?

If you're interested in contributing to the development of Mesos, the Apache Mesos Triage JIRA board would be a good place to look for interesting tickets, as well as Submitting a Patch guide on the Apache Website. There is also an IRC channel at #mesos on irc.freenode.net.

If you're interested in Marathon, I think the best way to contribute is to create pull requests on the Github Repo. You can also find folks on #marathon on irc.freenode.net.

@davelester
Copy link
Member

@mpark thanks for committing this! In the future if you update the documentation or adopters list, please also do a separate update of the website to reflect these changes so they don't get out of sync. I can put it live this time.

@usultrared
Copy link
Contributor Author

Guys,
I still cannot see linkernetworks in that page .
Something wrong here ?

Sent from my iPhone

On Aug 12, 2015, at 2:06 AM, Dave Lester notifications@github.com wrote:

@mpark thanks for committing this! In the future if you update the documentation or adopters list, please also do a separate update of the website to reflect these changes so they don't get out of sync. I can put it live this time.


Reply to this email directly or view it on GitHub.

@usultrared
Copy link
Contributor Author

Guys,
it still not reflect on the website .

@haosdent
Copy link
Member

Hi, @usultrared The document is not real time update. It would show after next website generation. But your company has already in repo now. https://github.com/apache/mesos/blob/master/docs/powered-by-mesos.md

@usultrared
Copy link
Contributor Author

Thanks , man

Sent from my iPhone

On Aug 13, 2015, at 7:23 PM, haosdent notifications@github.com wrote:

Hi, @usultrared The document is not real time update. It would show after next website generation. But your company has already in repo now. https://github.com/apache/mesos/blob/master/docs/powered-by-mesos.md


Reply to this email directly or view it on GitHub.

Change from Linkernetworks to Linker Networks
@davelester
Copy link
Member

@usultrared This is now reflected on the website: http://mesos.apache.org/documentation/latest/powered-by-mesos/

@usultrared
Copy link
Contributor Author

lester,
Just changed from linkernetworks to Linker Networks . Thanks anyway.

Sent from my iPhone

On Aug 14, 2015, at 2:04 PM, Dave Lester notifications@github.com wrote:

@usultrared This is now reflected on the website: http://mesos.apache.org/documentation/latest/powered-by-mesos/


Reply to this email directly or view it on GitHub.

@jfarrell
Copy link
Contributor

Closing per request at https://s.apache.org/V8r3

@jfarrell jfarrell closed this Jul 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants