[Incubator] zoo-project community sprint checklist hacking

[Jody Garnett]

whew!

Thanks for working with me today Gerald!

While we found a few gaps in the checklist (where are decisions made, how
to test) that I expect these can be closed quickly.

Please just document how ZOO-Project works currently, all this stuff is
directed towards welcoming developers to ZOO-Project and making it easier
know how to take part.
--
Jody Garnett


On Sat, 31 Aug 2019 at 12:17, Jody Garnett <jody.garnett at gmail.com> wrote:

> Enjoying Gerald's company as we look at checklist, these are notes:
>
> https://wiki.osgeo.org/wiki/ZOO-Project_Incubation_Checklist
>
> *1. open *
>
> *1a: source license*
>
> This is actually interesting, lots licenses here and the license file is
> more go a guide :)
>
> I would kind of expect each license to be listed in full as part of the
> distribution (this is a requirement for some of them).
>
> For a similar situation eclipse foundation had JTS make one file
> <https://github.com/locationtech/jts/blob/master/LICENSES.md>, and then a
> directory of all the individual license files.
>
> One of the licenses is GPL, that is run as a separate component (so the
> other components do not need to be GPL).
> This will make a great example for other OSGeo project when you are done :)
>
> *1b: *open communication channels
>
> listed: email / IRC (not used much)
> discuss: gitter / riot.m
>
> *1c: *open decisions
>
> open issue tracker - in contributor guide
> discussion on level --> motion --> psc vote
>
> todo: add this to the contributor guide
>
> *2.* active health community
>
> *2a* active collaborative with developers / users
>
> Some discussion about private email being sent directly when testing beta
> / RC releases. Something to work on with the community as a whole.
>
> todo: Have a good email discussion with zoo-discuss, the recent release
> candidate had no public feedback. This is a missed opportunity to show
> collaboration for incubation.
>
> reporting bugs in the public issue tracker is going well.
> task: update link to new release procedure
>
> zoo-psc email has public archive, private member list by request.
>
> *2b* long term viability
>
> PSC and contributors lists shows a wide range of organizations. Casual
> discussion indicates project supported by a range of industries / academic
> :)
>
> Code also has some indications of "code supported by public funds" which
> is a classy touch!
>
> --- more to come now coffee --
>
>
>
>
> --
> Jody Garnett
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20190831/28cfac67/attachment.html>