incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: [ATTN MENTOR] Re: DISCUSS: Ripple as a sub-project of Cordova
Date Tue, 31 Jul 2012 14:49:59 GMT
On 30 July 2012 22:18, Gord Tanner <> wrote:
> What are the community requirements for ASF?

Entry into the incubator has no requirements other than a genuine
desire to build a diverse community.

Exit requires that you have demonstrated that the project environment
is either diverse or is run in such a way as to encourage diversity.
How this is measured varies from person to person. Some people like to
see a minimum number of contributors from different employers. Many
others just want to be convinced the project is a meritocracy. In
general as long as you have demonstrated an ability to identify,
welcome and assist potential new contributors things are good. Of
course, there are other more practical graduation requirements related
to licenses and so on.

> Ripple right now has a rather small community behind it (3 people core at
> RIM) and a few forks out in the wild that haven't been merged back in yet.

A focus on the appropriate forks would be the kind of thing we'd be
looking at. The ASF does not interfere with the technical objectives
of the project, but where forks exist we'd want to see a proper
evaluation and, if appropriate, an attempt to integrate the effort
into the core project.

>  Our main goal for Ripple being in the ASF is to try to build community
> around it and get the cordova / mobile web app developer bases behind it
> and able to contribute to it without the "This belongs to RIM" mindset we
> are getting now.

That's a very good start ;-)

The broader community goal is best served by being a separate podling.
The narrower Cordova goal might be better served by being a
sub-project and, as Jukka said, you can always spin-out of Cordova as
a TLP later.

I've snipped the bit where you conclude it might be better go be a
separate project, but if any Cordova contributors feel they need to
make an additional case for being a sub-project now is the time.


> This may be getting off topic now for the cordova mailing lists so who do I
> talk to from ASF to start setting up the donation of Ripple?

First off you need a Champion. Their role is to help guide you through
the proposal process which is described at [1]. The role of champion
is defined at [2]

A champion needs to be an Officer or Member of the foundation.
Officers are listed at [3] and members interested in the incubator
hang around the list. If you already have
a relationship with any of these people then approach them directly.
If you don't have anyone in mind then drop me a private mail and I'll
think of some potential candidates (private because the candidates
might not be interested rather than because it is sensitive).



> Gord
> On Mon, Jul 30, 2012 at 12:21 PM, Ross Gardler
> <>wrote:
>> On 30 July 2012 16:56, Michael Brooks <> wrote:
>> > If Ripple was donated as a standalone project, then a shared
>> > general@mailing-list between Cordova and Ripple would be very nice.
>> IMHO such lists don't (often) make sense. Jukka made the suggestion
>> using Hadoop as an example of a consortium of projects. However, there
>> is (to my knowledge - Jukka will correct me if I'm wrong) no such list
>> for Hadoop.
>> What topics would need to be discussed on a general mailing list
>> between the two projects which could not be adequately carried out on
>> the more focused project list?
>> Unless there is a very surprising answer to the above question, the
>> way I see it the options are...
>>   - Ripple as a sub-project of Cordova with all development on
>> cordova-dev (potential for too much non-cordova discussion) - example
>> lucene and friends
>>   - Ripple as a new podling with all development on ripple-dev and
>> cordova-dev (interested cordova and ripple devs cross-subscribe) -
>> example hadoop and friends
>> Remember, this is only my opinion based on my observations of what
>> works in the ASF today - the ASF is a flexible place. Changes to old
>> approaches can be adopted when good reason to do so is presented.
>> Ross
>> >
>> > On Mon, Jul 30, 2012 at 7:31 AM, Ross Gardler <
>> >
>> >> On 30 July 2012 15:06, Jukka Zitting <> wrote:
>> >> > Hi,
>> >> >
>> >> > On Thu, Jul 26, 2012 at 8:18 PM,  <> wrote:
>> >> >> I sometimes see cordova not as a specific platform (or set of APIs)
>> but
>> >> as a leader
>> >> >> in the open mobile web.  If we are able to step away from the idea
>> >> cordova being
>> >> >> a singular platform but the bleeding edge of mobile web r &
d it
>> makes
>> >> sense to
>> >> >> have ripple be a part of that.
>> >> >
>> >> > A good example of how such a vision is being realized at the ASF is
>> >> > the Hadoop project that has given birth to a growing ecosystem of
>> >> > related cloud and big data projects at and around the ASF. Instead
>> >> > Hadoop hosting related projects like HBase, Pig, ZooKeeper, etc. as
>> >> > subprojects under a single PMC, it simply acts as a central focus
>> >> > point for a larger cluster of projects.
>> >> >
>> >> > I'd love to see Cordova increasingly position itself as such a focus
>> >> > point for mobile web projects both within and outside the ASF.
>> >>
>> >> +1
>> >>
>> >> > One
>> >> > concrete idea towards such a goal could be to start a general@mailing
>> >> > list as a shared forum like the one Hadoop has for discussions that
>> >> > reach beyond the boundaries of individual projects or codebases.
>> >>
>> >> I'm not sure we're ready for that yet. What other projects would be
>> >> interested in this?
>> >>
>> >> Possibly Wookie (W3C Widget engine), others?
>> >>
>> >> Ross
>> >>
>> >> --
>> >> Ross Gardler (@rgardler)
>> >> Programme Leader (Open Development)
>> >> OpenDirective
>> >>
>> --
>> Ross Gardler (@rgardler)
>> Programme Leader (Open Development)
>> OpenDirective
> --
> Gord Tanner
> Senior Developer / Code Poet
> tinyHippos Inc.
> @tinyhippos

Ross Gardler (@rgardler)
Programme Leader (Open Development)

View raw message