[Incubator] recognizing projects that are not incubating

[Jody Garnett]

I would be happy to help you fill in the checklist, there is a copy of it
as both as both a PDF and Markdown.

I also note that the nature of community activity has changed in the last
ten years, now that we have engineers who have always open source their
expectations with respect to participation (or lack of participation) are
being challenging.

Let’s fill in the checklist, and we can discuss if the level of community
involvement is appropriate.

This may also be a chance to reach out to your community that you do have
(the folks you mentioned) and explain you are willing to be more open (less
private email) and expect their increased involvement. Review the the
social context associated with your project and do a bit of a “reset” of
expectations on both sides.

It may seem like a bit of overhead (it is) but both parties are paid back
in a safer project.

On Wed, May 15, 2019 at 4:06 AM Mäkinen Sami (MML) <
sami.makinen at maanmittauslaitos.fi> wrote:

> Hi,
>
>
>
> I’m from the Oskari team and we are still interested in graduating. The
> problem is we don’t really know what we can do to take the next
> step/graduate. The last messages about the incubation for our project as I
> gathered was that people who posted on this list seemed happy with how we
> are handling things but our mentor Arnulf pointed out that there doesn’t
> seem to be too much of a visible community activity around the project. We
> have the mailing list which we are urging people to use instead of private
> emails, we have companies that are doing business using Oskari here in
> Finland, we have Iceland who has adopted Oskari as their geoportal, we have
> Gitter where people occasionally drop by to ask something in addition to
> GitHub issues. I agree that outside of the core development there’s not too
> much external communication or pull requests coming in and I don’t know the
> specifics how to decide if it’s enough to justify graduating. I think we
> would be happy to be a community project as well if being a “full member”
> is not justified.
>
>
>
> Best regards,
>
> Sami Mäkinen
>
>
>
>
>
> *Lähettäjä:* Incubator <incubator-bounces at lists.osgeo.org> *Puolesta *Jody
> Garnett
> *Lähetetty:* tiistai 14. toukokuuta 2019 19.29
> *Vastaanottaja:* OSGeo-incubator <incubator at lists.osgeo.org>
> *Aihe:* [Incubator] recognizing projects that are not incubating
>
>
>
> I think we have an easy way to recognize projects that are not interested
> in incubation.
>
>
>
> The following projects have not updated their "incubation status" page to
> the "graduation checklist". Kind of means no progress/interest since since
> the document was released at least five years ago:
>
>    - istSOS Incubation Status
>    <https://wiki.osgeo.org/wiki/IstSOS_Incubation_Status> - last updated
>    in 2016 to change mentor to Jeff McKenna
>    - MetaCRS Incubation Status
>    <https://wiki.osgeo.org/wiki/MetaCRS_Incubation_Status> - Individual
>    projects can enter the "OSGeo community" program, and enter incubation as
>    their interest. In practice MetaCRS itself is operating as an initiative
>    gathering up interested projects for the occasional collaboration?
>    - Oskari Incubation Status
>    <https://wiki.osgeo.org/wiki/Oskari_Incubation_Status> - last edited
>    2017
>    - TEAM Engine - it is not on the wiki but I Luis was working on a
>    checklist during the FOSS4GNA sprint?
>
> I would like to propose these projects be dropped from the incubation
> program, they can reapply when they are interested in working towards
> graduation.
>
> --
>
> Jody Garnett
>
-- 
--
Jody Garnett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20190515/02947ecc/attachment.html>