What do we still need to be ready for graduation?

[Katherine Marsden <km...@apache.org>]

Hello Edgent Community and especially committers and ppmc members,

The incubator PMC is engaging in a "Podling Graduation Rally"  and has 
identified Edgent as appearing to be ready to graduate[1].  So the 
question is: What do you as a community feel we still need to do to be 
ready?   I would recommend the following steps before graduation.

1) Attract at least  a third independent committer/ppmc member.
2) Do a second release to show the process is repeatable (under way).
3) Complete the Maturity Model [1]. (There are just a couple security 
items that I felt someone with better knowledge of the product should 
address QU20 and QU30)
4) Prepare a graduation resolution.
5) Secure a volunteer to complete the graduation infrastructure steps 
once voted in.


Are there other items we should address?

Any volunteers for the items above?

Any members of the community out there that would like to contribute and 
work toward being a committer on the project? Please let us know your 
interests and I am sure the community would be willing to help you.

Best

Kathey


[1] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201702.mbox/%3CCAOqetn8-Y55KLoqx8dO9wR9go33U8BM_zo9D_VsAvdjbqUpe9g%40mail.gmail.com%3E
[2] 
https://cwiki.apache.org/confluence/display/EDGENT/Apache+Maturity+Model+For+Edgent
[3] - http://incubator.apache.org/guides/graduation.html

Re: What do we still need to be ready for graduation?

[Dan Debrunner <dj...@debrunners.com>]

On 2/14/2017 8:20 AM, Katherine Marsden wrote:
> Hello Edgent Community and especially committers and ppmc members,
>
> The incubator PMC is engaging in a "Podling Graduation Rally"  and has
> identified Edgent as appearing to be ready to graduate[1].  So the
> question is: What do you as a community feel we still need to do to be
> ready?   I would recommend the following steps before graduation.
>
> 1) Attract at least  a third independent committer/ppmc member.

 From an ASF PoV I think the community needs more non-IBM 
committers/ppmc members. If IBM withdrew their activity on Edgent then 
the project might just die.

An additional release would hopefully help use of Edgent and hopefully 
visibility at the IoT summit (?) at ApacheCon.

Dan.
Disclaimer: I'm employed by IBM.

Re: What do we still need to be ready for graduation?

[William Marshall <wc...@gmail.com>]

>What do you as a community feel we still need to do to be ready?

To mirror previous concerns, I agree that we need a larger and more diverse
community. I see healthy projects composed of many individual contributors
from universities, corporate entities, or personal projects. Currently, we
only have one non-IBM committer.

Meetups, conferences, and articles might be a good way to spur growth.

-Will

Re: What do we still need to be ready for graduation?

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> 1) Attract at least  a third independent committer/ppmc member.

Would be best, but I think it may be possible to graduate without that.

> 2) Do a second release to show the process is repeatable (under way).

It would also be good to do a release with a different rerelease manager. (Tests the release process is documented and that someone else can follow it.)

> 3) Complete the Maturity Model [1]. (There are just a couple security items that I felt someone with better knowledge of the product should address QU20 and QU30)

This is not a requirement to graduate but it still a handy document.

> 5) Secure a volunteer to complete the graduation infrastructure steps once voted in.

Mentors/infra normally help out with most of the process here. There’s usually a  press release than needs to be drafted, can’t think of anything else off top of my head.

Thanks,
Justin