incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: Apache Cordova: inquiry about graduation status and timeline
Date Tue, 05 Jun 2012 00:31:36 GMT
Apache RAT audit complete. Hurray!

I've gone through incubation graduation checklist (my comments inline)
below. I think we are good! Final step is to create a test release
snapshot and make sure it adheres to the release checklist you provided,
Jukka. I will be working on this today and tomorrow. Will follow up in
this thread once I have something more to show on that have something you
can glance over, Jukka.

* Legal
  * All code ASL'ed
  * The code base must contain only ASL or ASL-compatible dependencies
  * License grant complete
  * CLAs on file.
  * Check of project name for trademark issues

Yep, I think we're good on legal now that the RAT audit is done.

* Meritocracy / Community
  * Demonstrate an active and diverse development community

Contributors come from companies such as IBM, Adobe, RIM, Microsoft and
Nokia, plus a bunch of independent contributors, so diversity: yes!

  * The project is not highly dependent on any single contributor (there
are at least 3 legally independent committers and there is no single
company or entity that is vital to the success of the project)

Any single contributor (or even company, for that matter) were to abandon
the project, it would very likely still be able to go on and survive and
continue growing.

  * The above implies that new committers are admitted according to ASF
  * ASF style voting has been adopted and is standard practice

I think we are now comfortable with the voting process (discuss + vote on
the private mailing list, forward results if successful to (I)PMC).

  * Demonstrate ability to tolerate and resolve conflict within the

I think so. Example would be the recent "browser invocation" discussion
that was had [1] recently.

  * Release plans are developed and excuted in public by the community.

The roadmap on the wiki [2] is the go-to place for this for our project.

  * Engagement by the incubated community with the other ASF communities,
particularly infrastructure@ (this reflects my personal bias that projects
should pay an nfrastructure "tax").

Oooo.. yeah. Probably not as good as it should be. I am on the infra and
infra-dev lists, but other than engaging in discussion here and there
(particularly related to opinions about git) I am not further involved. As
a project community we definitely should put more effort into this (we
take a lot, we should give back too).

  * Incubator PMC has voted for graduation
  * Destination PMC, or ASF Board for a TLP, has voted for final acceptance

I dunno heh.

* Alignment / Synergy
  * Use of other ASF subprojects
  * Develop synergistic relationship with other ASF sub projects

CouchDB + Cordova is a good combo :D

Although I wonder if our preference for git implicitly docks us marks in
the eyes of the SVN folk ;)

* Infrastructure
  * SVN module has been created
  * Mailing list(s) have been created
  * Mailing lists are being archived
  * Issue tracker has been created
  * Project website has been created and complies with the Apache Project
Branding Requirements
  * Project ready to comply with ASF mirroring guidelines

Yep, yes, yeah, ya, yelpers, yup, mhmm.

  * Project is integrated with GUMP if appropriate

I.. Dunno.

  * Releases are PGP signed by a member of the community

I believe our coho release tool does this but I will verify shortly!

  * Developers tied into ASF PGP web of trust



On 6/1/12 4:36 PM, "Filip Maj" <> wrote:

>I'll focus on this next week Jukka. I'll reply back to this thread once I
>believe all of the points are covered.
>On 6/1/12 4:09 PM, "Jukka Zitting" <> wrote:
>>On Fri, Jun 1, 2012 at 10:52 PM, Filip Maj <> wrote:
>>> I believe the last thing standing in our way is making sure our
>>> repositories have the right license headers in place, and that we are
>>> shipping .jars, that kinda stuff.
>>That's the most pressing issue, right. There are also other concerns
>>(full list at [1]), though as discussed earlier I think Cordova is
>>doing pretty good.
>>As for getting the Apache release done, would someone mind reviewing
>>the latest sources in terms of the requirements documented in the
>>Apache release FAQ [2]. I'll in any case do another review once the
>>next release candidate is available, but ideally at that point all the
>>potential remaining issues would already have been resolved. :-)
>>Jukka Zitting

View raw message