Re: Is Apache Myriad dead?

[Will Ochandarena]

Darin - yes we've done more planning internally, and we do plan on having some 
engineers spend some time on this project, doing some (minor) maintenance for 
our customers.


That said, given the overall project community has waned over the last year, we 
aren't opposed to letting the project sunset, doing our maintenance outside of 
Apache (but still in open source).


To that end, we (MapR) happily volunteer to take ownership of the code, keeping 
it in our git repo.  If it happens to pick up steam 
with a diverse community, we'll look at submitting it back to the incubator.


Since i'm not a committer I'm not sure how involved I can be with the 
sunsetting process, but i'm happy to help however I can.  Perhaps Ted and the 
other mentors can comment on what the next steps would be.


Will



From: Darin Johnson 
Sent: Saturday, June 3, 2017 1:07:48 PM
To: Dev
Cc: lrese...@apache.org; tdunn...@apache.org; dan...@apache.org; 
b...@apache.org; Will Ochandarena
Subject: Re: Is Apache Myriad dead?

Will, any update we've got an Apache review and I'm planning to recommend 
retirement.

On May 3, 2017 10:50 AM, "Will Ochandarena" 
> wrote:
All - sorry for the delay in commenting.  We (MapR) are in the midst of roadmap 
planning for Myriad and other projects.


Please give us a couple of weeks to plan our resourcing.  I'll come back soon 
with a proposal for how we take the project forward.


Will Ochandarena

MapR Product Management


From: Adam Bordelon >
Sent: Friday, April 28, 2017 8:40:30 PM
To: dev@myriad.incubator.apache.org
Cc: dan...@apache.org; 
tdunn...@apache.org; 
lrese...@apache.org; 
b...@apache.org
Subject: Re: Is Apache Myriad dead?

Maybe not dead, but it's in a coma, and I'm not sure if/when it'll wake up
again.
I'm not opposed to retiring, except that moving off of Apache infra sounds
like work.

On Fri, Apr 28, 2017 at 5:46 AM, Klaus Ma 
> wrote:

> +1 on retire
>
> > On 28 Apr 2017, at 20:33, Darin Johnson 
> > > wrote:
> >
> > I think that's an accurate assessment, as much as I'd like to say
> otherwise.
> >
> > I'd suggest we start a vote to retire.
> >
> > Darin
> >
> > On Apr 28, 2017 5:52 AM, "Niels Basjes" 
> > > wrote:
> >
> > Hi,
> >
> > A few weeks ago at the Dataworks/Hadoop Summit in Munich I discussed the
> > upcoming docker support in Yarn (Hadoop 3.0) and I mentioned Apache
> Myriad
> > as a seemingly related project.
> > Someone then stated that Myriad is a dead project and I should avoid it.
> >
> > Out of curiosity to check the validity of that statement I had a look at
> > the project today and I found that
> > - In 2017 only 2 jira tickets were touched (actually 3, but 1 is a
> > duplicate)
> > - The last commit to any branch I could find was about 7 months ago. The
> > last JIRA ticket was 'Fixed' around the same time.
> > - The dev mailing (when ignoring these jira issues and ASF generic
> > messages) is also almost silent.
> >
> > To me this looks like just about everyone involved lost interest in the
> > project about 6 months ago.
> >
> > So can I conclude this project is actually dead?
> >
> > --
> > Best regards
> >
> > Niels Basjes
> > nielsbas...@apache.org
>
>

Re: Is Apache Myriad dead?

[Swapnil Daingade]

In that case I suggest we not retire

>> "Darin - yes we've done more planning internally, and we do plan on
having some engineers spend some time on this project, doing some (minor)
maintenance for our customers."

Regards
Swapnil


On Mon, Jun 5, 2017 at 7:34 AM, Will Ochandarena 
wrote:

> Darin - yes we've done more planning internally, and we do plan on having
> some engineers spend some time on this project, doing some (minor)
> maintenance for our customers.
>
>
> That said, given the overall project community has waned over the last
> year, we aren't opposed to letting the project sunset, doing our
> maintenance outside of Apache (but still in open source).
>
>
> To that end, we (MapR) happily volunteer to take ownership of the code,
> keeping it in our git repo.  If it happens to
> pick up steam with a diverse community, we'll look at submitting it back to
> the incubator.
>
>
> Since i'm not a committer I'm not sure how involved I can be with the
> sunsetting process, but i'm happy to help however I can.  Perhaps Ted and
> the other mentors can comment on what the next steps would be.
>
>
> Will
>
>
> 
> From: Darin Johnson 
> Sent: Saturday, June 3, 2017 1:07:48 PM
> To: Dev
> Cc: lrese...@apache.org; tdunn...@apache.org; dan...@apache.org;
> b...@apache.org; Will Ochandarena
> Subject: Re: Is Apache Myriad dead?
>
> Will, any update we've got an Apache review and I'm planning to recommend
> retirement.
>
> On May 3, 2017 10:50 AM, "Will Ochandarena" > wrote:
> All - sorry for the delay in commenting.  We (MapR) are in the midst of
> roadmap planning for Myriad and other projects.
>
>
> Please give us a couple of weeks to plan our resourcing.  I'll come back
> soon with a proposal for how we take the project forward.
>
>
> Will Ochandarena
>
> MapR Product Management
>
> 
> From: Adam Bordelon >
> Sent: Friday, April 28, 2017 8:40:30 PM
> To: dev@myriad.incubator.apache.org >
> Cc: dan...@apache.org; tdunn...@apache.org
> ; lrese...@apache.org se...@apache.org>; b...@apache.org
> Subject: Re: Is Apache Myriad dead?
>
> Maybe not dead, but it's in a coma, and I'm not sure if/when it'll wake up
> again.
> I'm not opposed to retiring, except that moving off of Apache infra sounds
> like work.
>
> On Fri, Apr 28, 2017 at 5:46 AM, Klaus Ma  @icloud.com>> wrote:
>
> > +1 on retire
> >
> > > On 28 Apr 2017, at 20:33, Darin Johnson  mailto:dbjohnson1...@gmail.com>> wrote:
> > >
> > > I think that's an accurate assessment, as much as I'd like to say
> > otherwise.
> > >
> > > I'd suggest we start a vote to retire.
> > >
> > > Darin
> > >
> > > On Apr 28, 2017 5:52 AM, "Niels Basjes"  basjes.nl>> wrote:
> > >
> > > Hi,
> > >
> > > A few weeks ago at the Dataworks/Hadoop Summit in Munich I discussed
> the
> > > upcoming docker support in Yarn (Hadoop 3.0) and I mentioned Apache
> > Myriad
> > > as a seemingly related project.
> > > Someone then stated that Myriad is a dead project and I should avoid
> it.
> > >
> > > Out of curiosity to check the validity of that statement I had a look
> at
> > > the project today and I found that
> > > - In 2017 only 2 jira tickets were touched (actually 3, but 1 is a
> > > duplicate)
> > > - The last commit to any branch I could find was about 7 months ago.
> The
> > > last JIRA ticket was 'Fixed' around the same time.
> > > - The dev mailing (when ignoring these jira issues and ASF generic
> > > messages) is also almost silent.
> > >
> > > To me this looks like just about everyone involved lost interest in the
> > > project about 6 months ago.
> > >
> > > So can I conclude this project is actually dead?
> > >
> > > --
> > > Best regards
> > >
> > > Niels Basjes
> > > nielsbas...@apache.org
> >
> >
>
>

Re: Is Apache Myriad dead?

[Ted Dunning]

On Mon, Jun 5, 2017 at 10:15 PM, Swapnil Daingade <
swapnil.daing...@gmail.com> wrote:

> In that case I suggest we not retire
>
> >> "Darin - yes we've done more planning internally, and we do plan on
> having some engineers spend some time on this project, doing some (minor)
> maintenance for our customers."
>

The problem is that there is essentially no real community that is
happening.

None of the engineers previously working on this will be working on this
now. And that sort of situation isn't going to change.

That means that it will always be a distraction to get committers qualified
as PMC so that they can approve releases and it will never really be
possible to exit from incubation.

Outside of the Apache limits, we can have a much more flexible structure of
who can commit. We don't plan to limit who can commit. In fact, we will
probably make it more open than an Apache project normally is.

Re: Is Apache Myriad dead?

[Darin Johnson]

Swapnil, the reasons Ted mentioned are precisely the reasons I've stopped
committing to Myriad (we're running a fork).  Apache is more overhead than
this project needs and actually hinders the project from developing to a
maturity level where a community can form.

Darin


On Jun 5, 2017 5:53 PM, "Ted Dunning"  wrote:


On Mon, Jun 5, 2017 at 10:15 PM, Swapnil Daingade <
swapnil.daing...@gmail.com> wrote:

> In that case I suggest we not retire
>
> >> "Darin - yes we've done more planning internally, and we do plan on
> having some engineers spend some time on this project, doing some (minor)
> maintenance for our customers."
>

The problem is that there is essentially no real community that is
happening.

None of the engineers previously working on this will be working on this
now. And that sort of situation isn't going to change.

That means that it will always be a distraction to get committers qualified
as PMC so that they can approve releases and it will never really be
possible to exit from incubation.

Outside of the Apache limits, we can have a much more flexible structure of
who can commit. We don't plan to limit who can commit. In fact, we will
probably make it more open than an Apache project normally is.

Re: Is Apache Myriad dead?

[Swapnil Daingade]

>> The problem is that there is essentially no real community that is
happening.

retiring doesn't help that

>> None of the engineers previously working on this will be working on this
now. And that sort of situation isn't going to change.

Events at MapR contributed to this situation. MapR scaled back its
involvement in Myriad and all its committers left.
MapR is of course free to take its own decisions. But it sounds like there
is interest in working on Myriad, just not under the ASF umbrella.
I feel without ASF, one company will have too much control on Myriad.

Ted, you yourself warned us against this
http://www.zdnet.com/article/hadoop-veteran-ted-dunning-when-open-source-is-anything-but-open/

>>That means that it will always be a distraction to get committers
qualified as PMC so that they can approve releases and it will never really
be possible to exit from incubation.

I suggest we start with the contributions first.

Regards
Swapnil


On Mon, Jun 5, 2017 at 2:53 PM, Ted Dunning  wrote:

>
> On Mon, Jun 5, 2017 at 10:15 PM, Swapnil Daingade <
> swapnil.daing...@gmail.com> wrote:
>
>> In that case I suggest we not retire
>>
>> >> "Darin - yes we've done more planning internally, and we do plan on
>> having some engineers spend some time on this project, doing some (minor)
>> maintenance for our customers."
>>
>
> The problem is that there is essentially no real community that is
> happening.
>
> None of the engineers previously working on this will be working on this
> now. And that sort of situation isn't going to change.
>
> That means that it will always be a distraction to get committers
> qualified as PMC so that they can approve releases and it will never really
> be possible to exit from incubation.
>
> Outside of the Apache limits, we can have a much more flexible structure
> of who can commit. We don't plan to limit who can commit. In fact, we will
> probably make it more open than an Apache project normally is.
>
>