Re: Please do not retire Myriad

[John D . Ament]

Javi,

It looks like your repo is at 
https://git-wip-us.apache.org/repos/asf?p=incubator-myriad.git;a=summary
the push URL would be 
https://git-wip-us.apache.org/repos/asf/incubator-myriad.git

However, only committers on the project have write access.

John

On 2018/02/28 08:26:10, Javi Roman  wrote: 
> Totally agree Justin, I really don't like a parallel infrastructure
> ... I would be happy erasing all this parallel stuff and continuing
> with the ASF incubator infra. We only need some help in order to avoid
> the death of this project.
> 
> (I know www.myriad-framework.org breaks the trading and trademarks of
> ASF, this is something to change whether the only option is to
> continue the project out of ASF).
> 
> I have to say I don't know how to push up the project inside ASF, I
> can create PRs at GitHub ... but I afraid never will be attended, the
> same with JIRA and so on.
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> 
> 
> On Wed, Feb 28, 2018 at 9:05 AM, Justin Mclean  
> wrote:
> > Hi,
> >
> >> Unfortunately I don't have permissions for updating the report.
> >
> > It possible to email the report in and/or ask for someone to submit it for 
> > you.
> >
> > It’s unclear to me why you seem to be duplicating the site and mailing 
> > list if you want to keep the project at Apache. Decisions and communication 
> > needs to be happening on this list and you need to use Apache 
> > infrastructure for the site. I'm not sure trademarks would look too fondly 
> > on the site being hosted at http://www.myriad-framework.org.  Either you 
> > want the project to stay at Apache or you are forking it. If you are 
> > forking it then your project is not an Apache incubating project and that 
> > site (including probably the domain name) http://www.myriad-framework.org 
> > would need some work to comply with ASF policy on branding and trademarks. 
> > [1]
> >
> >> The other option is to change the incubator ownership to interested
> >> people like some of us.
> >
> > Are your project mentors still active? They may be able to help here. 
> > Ownership cannot just be handed over but they (and any other active PMC 
> > member) could vote new PMC members in.
> >
> > Thanks,
> > Justin
> >
> > 1. https://www.apache.org/foundation/marks/domains.html
> 

Re: Please do not retire Myriad

[Javi Roman]

Totally agree Justin, I really don't like a parallel infrastructure
... I would be happy erasing all this parallel stuff and continuing
with the ASF incubator infra. We only need some help in order to avoid
the death of this project.

(I know www.myriad-framework.org breaks the trading and trademarks of
ASF, this is something to change whether the only option is to
continue the project out of ASF).

I have to say I don't know how to push up the project inside ASF, I
can create PRs at GitHub ... but I afraid never will be attended, the
same with JIRA and so on.
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Wed, Feb 28, 2018 at 9:05 AM, Justin Mclean  wrote:
> Hi,
>
>> Unfortunately I don't have permissions for updating the report.
>
> It possible to email the report in and/or ask for someone to submit it for 
> you.
>
> It’s unclear to me why you seem to be duplicating the site and mailing list 
> if you want to keep the project at Apache. Decisions and communication needs 
> to be happening on this list and you need to use Apache infrastructure for 
> the site. I'm not sure trademarks would look too fondly on the site being 
> hosted at http://www.myriad-framework.org.  Either you want the project to 
> stay at Apache or you are forking it. If you are forking it then your project 
> is not an Apache incubating project and that site (including probably the 
> domain name) http://www.myriad-framework.org would need some work to comply 
> with ASF policy on branding and trademarks. [1]
>
>> The other option is to change the incubator ownership to interested
>> people like some of us.
>
> Are your project mentors still active? They may be able to help here. 
> Ownership cannot just be handed over but they (and any other active PMC 
> member) could vote new PMC members in.
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/foundation/marks/domains.html

Re: Please do not retire Myriad

[Justin Mclean]

Hi,

> Unfortunately I don't have permissions for updating the report.

It possible to email the report in and/or ask for someone to submit it for you.

It’s unclear to me why you seem to be duplicating the site and mailing list if 
you want to keep the project at Apache. Decisions and communication needs to be 
happening on this list and you need to use Apache infrastructure for the site. 
I'm not sure trademarks would look too fondly on the site being hosted at 
http://www.myriad-framework.org.  Either you want the project to stay at Apache 
or you are forking it. If you are forking it then your project is not an Apache 
incubating project and that site (including probably the domain name) 
http://www.myriad-framework.org would need some work to comply with ASF policy 
on branding and trademarks. [1]

> The other option is to change the incubator ownership to interested
> people like some of us.

Are your project mentors still active? They may be able to help here. Ownership 
cannot just be handed over but they (and any other active PMC member) could 
vote new PMC members in.

Thanks,
Justin

1. https://www.apache.org/foundation/marks/domains.html

Re: Please do not retire Myriad

[Javi Roman]

John,

Unfortunately I don't have permissions for updating the report. And
the only comments I can do regarding the status of the project is the
total abandoned state, the PMCs are not interested, the Jira
maintainer doesn't answer and so on.

The only thing I can do for helping the project is to create an
parallel infrastructure, so I've done:

GitHub: https://github.com/myriad-framework
Slack: https://myriad-mesos.slack.com
Site: http://www.myriad-framework.org/
Mailing list: 
http://myriad-framework.org/mailman/listinfo/dev_myriad-framework.org
Trello Kanban: https://trello.com/myriadframework

The other option is to change the incubator ownership to interested
people like some of us.

Many thanks for your answer.


--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Mon, Feb 26, 2018 at 2:57 AM, John D. Ament  wrote:
> Javi,
>
> Anyone from the community can work on the report.
>
> John
>
> On 2018/02/13 06:35:29, Javi Roman  wrote:
>> Hi John, this report is something that anyone can fill, or it's
>> restricted to PMCs only?
>> --
>> Javi Roman
>>
>> Twitter: @javiromanrh
>> GitHub: github.com/javiroman
>> Linkedin: es.linkedin.com/in/javiroman
>> Big Data Blog: dataintensive.info
>>
>>
>> On Sun, Feb 11, 2018 at 2:28 PM, John D. Ament  wrote:
>> > All,
>> >
>> > If you don't want the podling to retire, the biggest impacting thing you 
>> > can do is make sure a report is filed for the next reporting period.
>> >
>> > I believe without that, I can only assume that there's no interest in 
>> > remaining as an Apache project.
>> >
>> > John
>> >
>> > On 2018/02/02 19:45:22, Brandon Gulla  wrote:
>> >> While I am not a committer at the moment, having contributed to Myriad in
>> >> the early days, I am able to help review potential PRs and changes down 
>> >> the
>> >> road.
>> >>
>> >> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
>> >> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > > 1. Try to convince to Apache managers (I don't now the correct term)
>> >> > > for an exception to allow you accept commits from external
>> >> > > contributors (like me).
>> >> >
>> >> > All and any contributions are welcome, that is not he issue here. The
>> >> > board requires oversight of at least 3 (P)PMC members. For incubating
>> >> > project generally the committers are the PPMC.
>> >> >
>> >> > > 2. Follow your first proposal, create a new github organization, for
>> >> > > example (github.com/myriad) and working there.
>> >> >
>> >> > As the software is under the Apache license anyone can do this, you 
>> >> > don't
>> >> > need to ask for permission.
>> >> >
>> >> > > Maybe in the future we can try go to Apache incubation again.
>> >> >
>> >> > And I’m sure the Apache incubator would welcome that.
>> >> >
>> >> > > I guess we are three people with interest into continue the project,
>> >> > > you, Juan P. and myself. From my side I am working in a local fork for
>> >> > > enhancing some stuff.
>> >> >
>> >> > Alternatively if the people above have contributed and promoted the
>> >> > project (I’m sorry but I don’t know the full history here) and the 
>> >> > currenrt
>> >> > PPMC recognise that and votes you in as PPMC members then that may be
>> >> > enough to continue the project at Apache.
>> >> >
>> >> > Thanks.
>> >> > Justin
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Brandon
>> >>
>>

Re: Please do not retire Myriad

[John D . Ament]

Javi,

Anyone from the community can work on the report.  

John

On 2018/02/13 06:35:29, Javi Roman  wrote: 
> Hi John, this report is something that anyone can fill, or it's
> restricted to PMCs only?
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> 
> 
> On Sun, Feb 11, 2018 at 2:28 PM, John D. Ament  wrote:
> > All,
> >
> > If you don't want the podling to retire, the biggest impacting thing you 
> > can do is make sure a report is filed for the next reporting period.
> >
> > I believe without that, I can only assume that there's no interest in 
> > remaining as an Apache project.
> >
> > John
> >
> > On 2018/02/02 19:45:22, Brandon Gulla  wrote:
> >> While I am not a committer at the moment, having contributed to Myriad in
> >> the early days, I am able to help review potential PRs and changes down the
> >> road.
> >>
> >> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > > 1. Try to convince to Apache managers (I don't now the correct term)
> >> > > for an exception to allow you accept commits from external
> >> > > contributors (like me).
> >> >
> >> > All and any contributions are welcome, that is not he issue here. The
> >> > board requires oversight of at least 3 (P)PMC members. For incubating
> >> > project generally the committers are the PPMC.
> >> >
> >> > > 2. Follow your first proposal, create a new github organization, for
> >> > > example (github.com/myriad) and working there.
> >> >
> >> > As the software is under the Apache license anyone can do this, you don't
> >> > need to ask for permission.
> >> >
> >> > > Maybe in the future we can try go to Apache incubation again.
> >> >
> >> > And I’m sure the Apache incubator would welcome that.
> >> >
> >> > > I guess we are three people with interest into continue the project,
> >> > > you, Juan P. and myself. From my side I am working in a local fork for
> >> > > enhancing some stuff.
> >> >
> >> > Alternatively if the people above have contributed and promoted the
> >> > project (I’m sorry but I don’t know the full history here) and the 
> >> > currenrt
> >> > PPMC recognise that and votes you in as PPMC members then that may be
> >> > enough to continue the project at Apache.
> >> >
> >> > Thanks.
> >> > Justin
> >>
> >>
> >>
> >>
> >> --
> >> Brandon
> >>
> 

Re: Please do not retire Myriad

[Javi Roman]

Hi John, this report is something that anyone can fill, or it's
restricted to PMCs only?
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Sun, Feb 11, 2018 at 2:28 PM, John D. Ament  wrote:
> All,
>
> If you don't want the podling to retire, the biggest impacting thing you can 
> do is make sure a report is filed for the next reporting period.
>
> I believe without that, I can only assume that there's no interest in 
> remaining as an Apache project.
>
> John
>
> On 2018/02/02 19:45:22, Brandon Gulla  wrote:
>> While I am not a committer at the moment, having contributed to Myriad in
>> the early days, I am able to help review potential PRs and changes down the
>> road.
>>
>> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
>> wrote:
>>
>> > Hi,
>> >
>> > > 1. Try to convince to Apache managers (I don't now the correct term)
>> > > for an exception to allow you accept commits from external
>> > > contributors (like me).
>> >
>> > All and any contributions are welcome, that is not he issue here. The
>> > board requires oversight of at least 3 (P)PMC members. For incubating
>> > project generally the committers are the PPMC.
>> >
>> > > 2. Follow your first proposal, create a new github organization, for
>> > > example (github.com/myriad) and working there.
>> >
>> > As the software is under the Apache license anyone can do this, you don't
>> > need to ask for permission.
>> >
>> > > Maybe in the future we can try go to Apache incubation again.
>> >
>> > And I’m sure the Apache incubator would welcome that.
>> >
>> > > I guess we are three people with interest into continue the project,
>> > > you, Juan P. and myself. From my side I am working in a local fork for
>> > > enhancing some stuff.
>> >
>> > Alternatively if the people above have contributed and promoted the
>> > project (I’m sorry but I don’t know the full history here) and the currenrt
>> > PPMC recognise that and votes you in as PPMC members then that may be
>> > enough to continue the project at Apache.
>> >
>> > Thanks.
>> > Justin
>>
>>
>>
>>
>> --
>> Brandon
>>

Re: Please do not retire Myriad

[John D . Ament]

All,

If you don't want the podling to retire, the biggest impacting thing you can do 
is make sure a report is filed for the next reporting period.

I believe without that, I can only assume that there's no interest in remaining 
as an Apache project.

John

On 2018/02/02 19:45:22, Brandon Gulla  wrote: 
> While I am not a committer at the moment, having contributed to Myriad in
> the early days, I am able to help review potential PRs and changes down the
> road.
> 
> On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
> wrote:
> 
> > Hi,
> >
> > > 1. Try to convince to Apache managers (I don't now the correct term)
> > > for an exception to allow you accept commits from external
> > > contributors (like me).
> >
> > All and any contributions are welcome, that is not he issue here. The
> > board requires oversight of at least 3 (P)PMC members. For incubating
> > project generally the committers are the PPMC.
> >
> > > 2. Follow your first proposal, create a new github organization, for
> > > example (github.com/myriad) and working there.
> >
> > As the software is under the Apache license anyone can do this, you don't
> > need to ask for permission.
> >
> > > Maybe in the future we can try go to Apache incubation again.
> >
> > And I’m sure the Apache incubator would welcome that.
> >
> > > I guess we are three people with interest into continue the project,
> > > you, Juan P. and myself. From my side I am working in a local fork for
> > > enhancing some stuff.
> >
> > Alternatively if the people above have contributed and promoted the
> > project (I’m sorry but I don’t know the full history here) and the 
> > currenrt
> > PPMC recognise that and votes you in as PPMC members then that may be
> > enough to continue the project at Apache.
> >
> > Thanks.
> > Justin
> 
> 
> 
> 
> -- 
> Brandon
> 

Re: Please do not retire Myriad

[Brandon Gulla]

While I am not a committer at the moment, having contributed to Myriad in
the early days, I am able to help review potential PRs and changes down the
road.

On Fri, Feb 2, 2018 at 7:50 AM, Justin Mclean 
wrote:

> Hi,
>
> > 1. Try to convince to Apache managers (I don't now the correct term)
> > for an exception to allow you accept commits from external
> > contributors (like me).
>
> All and any contributions are welcome, that is not he issue here. The
> board requires oversight of at least 3 (P)PMC members. For incubating
> project generally the committers are the PPMC.
>
> > 2. Follow your first proposal, create a new github organization, for
> > example (github.com/myriad) and working there.
>
> As the software is under the Apache license anyone can do this, you don't
> need to ask for permission.
>
> > Maybe in the future we can try go to Apache incubation again.
>
> And I’m sure the Apache incubator would welcome that.
>
> > I guess we are three people with interest into continue the project,
> > you, Juan P. and myself. From my side I am working in a local fork for
> > enhancing some stuff.
>
> Alternatively if the people above have contributed and promoted the
> project (I’m sorry but I don’t know the full history here) and the currenrt
> PPMC recognise that and votes you in as PPMC members then that may be
> enough to continue the project at Apache.
>
> Thanks.
> Justin




-- 
Brandon

Re: Please do not retire Myriad

[Justin Mclean]

Hi,

> 1. Try to convince to Apache managers (I don't now the correct term)
> for an exception to allow you accept commits from external
> contributors (like me).

All and any contributions are welcome, that is not he issue here. The board 
requires oversight of at least 3 (P)PMC members. For incubating project 
generally the committers are the PPMC.

> 2. Follow your first proposal, create a new github organization, for
> example (github.com/myriad) and working there.

As the software is under the Apache license anyone can do this, you don't need 
to ask for permission.

> Maybe in the future we can try go to Apache incubation again.

And I’m sure the Apache incubator would welcome that.

> I guess we are three people with interest into continue the project,
> you, Juan P. and myself. From my side I am working in a local fork for
> enhancing some stuff.

Alternatively if the people above have contributed and promoted the project 
(I’m sorry but I don’t know the full history here) and the currenrt PPMC 
recognise that and votes you in as PPMC members then that may be enough to 
continue the project at Apache.

Thanks.
Justin

Re: Please do not retire Myriad

[Javi Roman]

I understand, you are the only Myriad committer right now (the only
committer with active interest in the project), and you are not able
of approving new committers, or even external contributions because
you are alone, and Apache need three official committers for that.

So we are locked!

What options do we have?

1. Try to convince to Apache managers (I don't now the correct term)
for an exception to allow you accept commits from external
contributors (like me). I mean continue the incubation process with
non-standard rules.

2. Follow your first proposal, create a new github organization, for
example (github.com/myriad) and working there. Maybe in the future we
can try go to Apache incubation again.

I guess we are three people with interest into continue the project,
you, Juan P. and myself. From my side I am working in a local fork for
enhancing some stuff.

What do you think about?
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Thu, Feb 1, 2018 at 11:18 PM, Darin Johnson  wrote:
> Javi, the block is a bit bigger than that.  To do things the Apache Way, at
> least 3 committers need to sign off on all releases and approve new
> committers.  This makes it really difficult to strengthen a weak
> community.  There may be a way around this if we got incubator to add some
> new committers outside the standard process.  I don't know how that would
> work or what evidence they'd want.  In addition we'd again need at least 3
> people actively contributing to the project.  Likely this would be almost
> identical to creating a new incubator project.

Re: Please do not retire Myriad

[Javi Roman]

You are right Darin.

However, from my point of view, the only justification for forking the
project is a block from the side of principal maintainers (pull
request untended, questions unanswered and so on).

Personally I'm going to try give an opportunity to the project as is
(under ASF infrastructure), participating in this list, checking the
JIRA tickets and creating PRs for a global enhanced.
Javi Roman

Twitter: @javiromanrh
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Wed, Jan 31, 2018 at 9:34 PM, Darin Johnson  wrote:
> If people are interested in working on it, it's possible to fork the
> project and continue.  If anyone wants to fork and continue I'd be happy to
> work with them (I'll even create the fork).  However, the community is so
> small and distracted it's not ideal to continue developing within Apache. I
> think Myriad might have gone into Apache Incubator to quickly in the first
> place.
>
> On Wed, Jan 31, 2018 at 11:57 AM, Javi Roman 
> wrote:
>
>> Hi Juan P.
>>
>> If the project doesn't have technical reasons for rejecting it, I
>> would like contribute for giving a boost.
>> Javi Roman
>>
>> Twitter: @javiromanrh
>> Linkedin: es.linkedin.com/in/javiroman
>> Big Data Blog: dataintensive.info
>>
>>
>> On Wed, Jan 31, 2018 at 2:41 PM, Juan P  wrote:
>> > Hello, in relation to this mail:
>> > https://www.mail-archive.com/dev@myriad.incubator.apache.org
>> /msg02319.html
>> >
>> > I totally agree, that it is a pity that the project is closed and I
>> wanted
>> > to express my intention to actively collaborate with it. I would need to
>> > update the Mesos version to be compatible with the latest versions.
>> >
>> > Thank you
>> >
>> > Juan Pedro Gilaberte
>> > http://github.com/jpgilaberte
>>

Re: Please do not retire Myriad

[Darin Johnson]

If people are interested in working on it, it's possible to fork the
project and continue.  If anyone wants to fork and continue I'd be happy to
work with them (I'll even create the fork).  However, the community is so
small and distracted it's not ideal to continue developing within Apache. I
think Myriad might have gone into Apache Incubator to quickly in the first
place.

On Wed, Jan 31, 2018 at 11:57 AM, Javi Roman 
wrote:

> Hi Juan P.
>
> If the project doesn't have technical reasons for rejecting it, I
> would like contribute for giving a boost.
> Javi Roman
>
> Twitter: @javiromanrh
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Wed, Jan 31, 2018 at 2:41 PM, Juan P  wrote:
> > Hello, in relation to this mail:
> > https://www.mail-archive.com/dev@myriad.incubator.apache.org
> /msg02319.html
> >
> > I totally agree, that it is a pity that the project is closed and I
> wanted
> > to express my intention to actively collaborate with it. I would need to
> > update the Mesos version to be compatible with the latest versions.
> >
> > Thank you
> >
> > Juan Pedro Gilaberte
> > http://github.com/jpgilaberte
>

Re: Please do not retire Myriad

[Javi Roman]

Hi Juan P.

If the project doesn't have technical reasons for rejecting it, I
would like contribute for giving a boost.
Javi Roman

Twitter: @javiromanrh
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Wed, Jan 31, 2018 at 2:41 PM, Juan P  wrote:
> Hello, in relation to this mail:
> https://www.mail-archive.com/dev@myriad.incubator.apache.org/msg02319.html
>
> I totally agree, that it is a pity that the project is closed and I wanted
> to express my intention to actively collaborate with it. I would need to
> update the Mesos version to be compatible with the latest versions.
>
> Thank you
>
> Juan Pedro Gilaberte
> http://github.com/jpgilaberte