Re: Apache Myriad Project Status

espi...@gmail.com> wrote: >>> >>>> Hi Ken, >>>> >>>> Good news, slowly we will be able to evolve this interesting project. The >>>> integration with DC/OS is a guarantee of framework success. >>>> >>>>

Re: Apache Myriad Project Status

Javi, Well done and Nice work! I am one of the original Apache committers on Myriad… however I have been MIA for a long time. I am willing and interested in helping. At this time I am not able to offer up a lot of time but will help where I can. As a part of Mesosphere, I spent some

Re: [Vote] Retire Myriad

I’ve been busy keeping up with a number of things and disengaged for some time.. I would like to come back to active status as a committer and I’m willing to commit to: 1. Review and merge of code. 2. Vet releases Ken > On Jun 20, 2017, at 10:26 AM, yuliya Feldman

Re: Myraid Slack

Darin try one more time… I think we had a miss configuration > On Jun 29, 2016, at 11:15 AM, Darin Johnson <dbjohnson1...@gmail.com> wrote: > > Still no luck off wifi or cell. > On Jun 29, 2016 12:11 PM, "Ken Sipe" <k...@mesosphere.io> wrote: > >> https

Re: Myraid Slack

https://plus.google.com/hangouts/_/mesosphere.io/myriad <https://plus.google.com/hangouts/_/mesosphere.io/myriad> > On Jun 29, 2016, at 11:08 AM, yuliya Feldman <yufeld...@yahoo.com.INVALID> > wrote: > > no luck joining so far > > From: Ken Sipe

Re: Will not attend today's dev sync

I'm out today as well Sent from my iPhone > On Mar 9, 2016, at 8:53 AM, Santosh Marella wrote: > > -- > Sent from mobile

Re: Introduction

awesome! welcome aboard Zach! Some of the build issue JIRAs should be easy knock outs and we need them for the 0.2.0 release. ken > On Feb 24, 2016, at 3:27 PM, Zachary Jaffee wrote: > > Hi Everyone, > > Maybe you have seen a few of my recent JIRA comments or PRs, but I

[jira] [Commented] (MYRIAD-165) Cleanup old branches in git

[ https://issues.apache.org/jira/browse/MYRIAD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163509#comment-15163509 ] Ken Sipe commented on MYRIAD-165: - thanks for script... here is the command for removing the branches from

[jira] [Commented] (MYRIAD-165) Cleanup old branches in git

[ https://issues.apache.org/jira/browse/MYRIAD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15163510#comment-15163510 ] Ken Sipe commented on MYRIAD-165: - for reference: ``` git remote -v apache https://kens...@git-wip

[jira] [Closed] (MYRIAD-181) Build failure due to dependency on zookeeper test jar

[ https://issues.apache.org/jira/browse/MYRIAD-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Sipe closed MYRIAD-181. --- Resolution: Fixed Assignee: Ken Sipe > Build failure due to dependency on zookeeper test

[jira] [Updated] (MYRIAD-165) Cleanup old branches in git

[ https://issues.apache.org/jira/browse/MYRIAD-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Sipe updated MYRIAD-165: Assignee: Ken Sipe > Cleanup old branches in git > --- > >

dev sync

https://plus.google.com/hangouts/_/mesosphere.io/myriad we are getting ready to begin

Re: New Committer: Swapnil Daingade

congrats Swapnil! > On Nov 5, 2015, at 6:38 AM, Adam Bordelon wrote: > > The Podling Project Management Committee (PPMC) for Apache Myriad has asked > Swapnil Daingade to become a committer and PPMC member and we are pleased > to announce that he has accepted. > > Please

Re: New committer: Darin J

congrats Darin! > On Nov 5, 2015, at 6:36 AM, Adam Bordelon wrote: > > The Podling Project Management Committee (PPMC) for Apache Myriad has asked > Darin to become a committer and PPMC member and we are pleased to announce > that he has accepted. > > Please join me in

Re: apache rat plugin

late to the conversation… gradle does NOT use maven plugins but for anything popular there is a gradle plugin. Gradle can use ANT plugins tho… In this case: https://plugins.gradle.org/plugin/org.nosphere.apache.rat ken > On Oct

Re: myriad.js

nything in /public is generated by gulp. > > I searched for santosh and ashankar in my repo and couldn't find anything. > what branch? > > > On Fri, Oct 16, 2015 at 11:35 AM, Ken Sipe <k...@mesosphere.io> wrote: > >> team, >> >> I was forced to revie

Re: Google Hangout Link

I sent an invite… and BTW… the sync notes have the hangout link at the top: https://docs.google.com/document/d/1JGmJrgeg98bHw_0_sSRmyX6WiAe13OdErcFlaz6Aa04/edit#heading=h.rnolkdpzfc8u https://docs.google.com/document/d/1JGmJrgeg98bHw_0_sSRmyX6WiAe13OdErcFlaz6Aa04/edit#heading=h.rnolkdpzfc8u

Re: Documentation Comments

john, the details of where to send it on in the pdf that must be filled out and signed. the fastest way is to send the ICLA to secret...@apache.org mailto:secret...@apache.org ken On Aug 19, 2015, at 1:56 PM, John Omernik j...@omernik.com wrote: Happy to sign the ICLA. Who do I send it

Re: Question about build

Hey Patrick, I was the one that refactored myriad in to a multi-project structure. I took what was originally there and tried to maintain the semantics into the new structure (meaning it was my intention to not change anything other than the structure). At first glance this appears to be a

Re: Docker Hub Docker submission

I just checked… docker hub security doesn’t have fine grain controls.the next level of access for the group you are in would be admin. It appears that writing a desc requires admin rights (based on what your feedback). Are you indicating you are not able to edit this:

Re: May board report

Justin, Thanks for the detailed feedback. As someone involved with the project here is my understanding: 1. we do have a hangout to discuss the project every 2 weeks. Is this not appropriate?It really helps to sync up with where we are in the process. Would it help if we had

Re: Recommending or requiring mesos dns?

John, 1. +1 to mesos-dns aware 2. all tasks deployed by mesos are already in mesos-dns. so all the nm are there (we should make sure they have good names. 3. the RM is not usually started with mesos… if it was it would also be listed in mesos-dns, however a process started outside mesos is not

docker hub repo

I’ve created a docker repo for myriad under the mesos namespace: https://registry.hub.docker.com/u/mesos/myriad/ https://registry.hub.docker.com/u/mesos/myriad/ provide me with users that need push rights thanks, ken

Re: docker hub repo

on the docker images. Am I missing something? Santosh On Wed, Apr 8, 2015 at 12:38 PM, Ken Sipe k...@mesosphere.io wrote: On Apr 8, 2015, at 2:33 PM, Luciano Resende luckbr1...@gmail.com wrote: How is this repo going to be used ? It will be the pull location for myriad… at least