[OSGeo-Discuss] Incubator Sponsor idea.
euzuro at gmail.com
Fri Sep 12 11:18:25 PDT 2008
On Fri, Sep 12, 2008 at 12:17 PM, Jody Garnett <jgarnett at refractions.net> wrote:
> Hi Bob; you will find that a few of the open source projects nurture new
> talent this way.
> The GeoTools library has the facilities in place to allow new developers to
> come online and start an "unsupported" module with the support of the
> community. Each module in GeoTools is an entire project (often making use of
> the same interfaces and so forth). When a module meets the QA requirements
> it can be included in the GeoTools download for the general public.
For the record, OpenLayers has *finally* taken steps towards following
this model as well with the advent of our /addins directory... it is a
place where OpenLayers developers can put code that they've written
and would like to share with the community... but which doesn't
necessarily belong in the core OL library. For now the involvement of
the OL PSC is pretty limited and informal... but the creation of a new
/addin does require a soft vote from the PSC in order to be
established... and with that comes a [n at least superficial] code
review and some guidance.
With the upcoming release of OpenLayers 2.7, we will be formally
announcing two new /addins... with the hopes that this will inspire
developers out there to contribute more.
> Is this what you had in mind?
> I understand that some something similar to Jakarta is often requested from
> the OSGeo foundation. Thus far the incubation committee has been really
> focused on getting existing projects through our incubation process (and
> defining what the expectations are for such projects).
> Bob Basques wrote:
>> I have a question about a possible way to get some smaller projects into
>> the system without the requirements of going full bore (as I perceive it
>> now) I'm not really targeting any project per se at this point, but . . .
>> What about have a "Super" project that can act as a sponsor for a smaller
>> project. When I say smaller, I mean where there might only be one, two or
>> three developers. The end result being that the "Super" project basically
>> vouches for the smaller project in some fashion for it to get some sort of
>> OSGEO stamp applied to it. This could possibly be a criteria where some of
>> the established vetting is handled via a voucher system, where other "Super"
>> projects can add their credentials to the mix over time.
>> Just a thought, still a little muddled too, but it seems like there might
>> be something workable in the concept. Any other thoughts?
>> Discuss mailing list
>> Discuss at lists.osgeo.org
> Discuss mailing list
> Discuss at lists.osgeo.org
More information about the Discuss