Re: Milagro Rescue Roadmap

[Nick Kew]

On Thu, 12 Apr 2018 16:35:25 +0100
Nick Kew  wrote:

> Posting to both dev@milagro and general@incubator.

> Would folks be happy for me to set up a page for this purpose
> under wiki/incubator?  I would propose a skeleton (mainly a
> set of headings) and look to the community to flesh it out.
> 

OK, I've created a skeleton
https://wiki.apache.org/incubator/MilagroRescueRoadmap

With a list of headings based on my understanding of
the situation.  I hope others will review and improve
my list, clarify the issues listed, and fill in the
big blanks.  If this can grow to a credible roadmap by
the end of April, I think we have the basis of a rescue!

Direct edits to the wiki are great.  If unsure about an
idea, either add it there as tentative, or discuss on-list.
Or of course both!

-- 
Nick Kew

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Milagro Rescue Roadmap

[John D. Ament]

On Thu, Apr 12, 2018 at 11:35 AM Nick Kew  wrote:

> Posting to both dev@milagro and general@incubator.
> As champion for Milagro, I feel responsible for this.
>
> In retrospect, Milagro probably entered the incubator
> prematurely.  It has got hung up on issues of process
> and infrastructure, and project activity hasn't
> migrated to apache.
>
> John has, for very good reasons, proposed retirement.
> However, a poll on the subject attracted a crop of -1 votes:
> people don't want it to retire.
>
> I added a mentor note to April's (late) report:
>
>   "Retirement vote got a crop of NOs, though some of those may
>have misunderstood its purpose.  I'm proposing those who
>support continuation make concrete progress in time to report
>(on time) in May.  Failing that, I will support retirement."
>
> I think what we need right now is a roadmap to bring work
> to Apache.  That'll need the Milagro community to identify
> what's holding it back, and us all to determine whether it
> makes sense to resolve at apache or retire it to its
> prior home at github.
>

Agreed.  There are two big red flags that I see right now that are blocking
Milagro.

- Commits being proposed to their master repos that explicitly reference
repositories hosted by Miracl.
- A seemingly lack of project direction.  Some NTT folks seem willing to
work with the project, but are waiting on Miracl to do something.

The first item is a clear problem.  To be an Apache project, you need to be
vendor independent.  You can't mix the company you work for an Apache, just
don't mix.  It's not clear to me yet that the participants on the project
want that.  Though that could easily be explained by joining Apache too
early.  I suspect there are some other podlings in similar boats, but are
masked by just enough on list discussions.


>
> Would folks be happy for me to set up a page for this purpose
> under wiki/incubator?  I would propose a skeleton (mainly a
> set of headings) and look to the community to flesh it out.
>

If Milagro already has a cwiki instance, I think it can live there.


>
> --
> Nick Kew
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Milagro Rescue Roadmap

[Ted Dunning]

I think a key task here is to help people understand that retirement does
not me and that the community dies. What means in many respects is the
community's freed of the Apache process.

On Thu, Apr 12, 2018, 09:16 Bertrand Delacretaz 
wrote:

> Hi Nick,
>
> On Thu, Apr 12, 2018 at 5:35 PM, Nick Kew  wrote:
> > ...I think what we need right now is a roadmap to bring work
> > to Apache.  That'll need the Milagro community to identify
> > what's holding it back, and us all to determine whether it
> > makes sense to resolve at apache or retire it to its
> > prior home at github
>
> Definitely a job for the Milagro community - if people want to stay in
> the Incubator, they have to roll up their sleeves accordingly - with
> the support of their mentors, of course.
>
> > ...Would folks be happy for me to set up a page for this purpose
> > under wiki/incubator?...
>
> Sounds good to me, that might be useful for other similar situations.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Milagro Rescue Roadmap

[Bertrand Delacretaz]

Hi Nick,

On Thu, Apr 12, 2018 at 5:35 PM, Nick Kew  wrote:
> ...I think what we need right now is a roadmap to bring work
> to Apache.  That'll need the Milagro community to identify
> what's holding it back, and us all to determine whether it
> makes sense to resolve at apache or retire it to its
> prior home at github

Definitely a job for the Milagro community - if people want to stay in
the Incubator, they have to roll up their sleeves accordingly - with
the support of their mentors, of course.

> ...Would folks be happy for me to set up a page for this purpose
> under wiki/incubator?...

Sounds good to me, that might be useful for other similar situations.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Milagro Rescue Roadmap

[Nick Kew]

Posting to both dev@milagro and general@incubator.
As champion for Milagro, I feel responsible for this.

In retrospect, Milagro probably entered the incubator
prematurely.  It has got hung up on issues of process
and infrastructure, and project activity hasn't
migrated to apache.

John has, for very good reasons, proposed retirement.
However, a poll on the subject attracted a crop of -1 votes:
people don't want it to retire.

I added a mentor note to April's (late) report:

  "Retirement vote got a crop of NOs, though some of those may
   have misunderstood its purpose.  I'm proposing those who
   support continuation make concrete progress in time to report
   (on time) in May.  Failing that, I will support retirement."

I think what we need right now is a roadmap to bring work
to Apache.  That'll need the Milagro community to identify
what's holding it back, and us all to determine whether it
makes sense to resolve at apache or retire it to its
prior home at github.

Would folks be happy for me to set up a page for this purpose
under wiki/incubator?  I would propose a skeleton (mainly a
set of headings) and look to the community to flesh it out.

-- 
Nick Kew

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org