[Incubator] zoo-project community sprint checklist hacking

[Jody Garnett]

Process:

1. version control

yes, svn :)

2. issue tracker

trac

3. project has documented its management process

A project committers guide
<http://zoo-project.org/docs/community/developer.html> is available, which
seems to focus on svn care and feeding, and not on how decisions are made.
It also talks about a COMMITTERS list which may be the list of folks
agreeing to license policy?

aside: Would love to see a less "business" word here like "project has
documented how the team functions"
aside: There is overlap here with a similar question under "open"

I am a bit confused on this section, perhaps the community guide says how
decisions are made and I am just missing it.

4. decisions

Okay details are in the wiki
<http://www.zoo-project.org/trac/wiki/PSC/process> (and looks very
complete).

5. public communication channels to make decisions

Checking the zoo-psc mailing list
<https://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc> shows:
- site:lists.osgeo.org/pipermail/zoo-psc/ meeting
- site:lists.osgeo.org/pipermail/zoo-psc/ vote
- site:lists.osgeo.org/pipermail/zoo-psc/ motion

Based on above last motion was passed in 2018, PSC does not appear active.
Should chat with mentor to determine how group functions etc...

Having a PSC is only idea, many projects discuss on developer list, or have
committers vote ...

The key thing is *however decisions are made it be transparent and have
some way for new individuals to eventually join the team and take part*.

Let me check zoo discuss

Checking the zoo-discuss mailing list
<https://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss> shows:
- site:lists.osgeo.org/pipermail/zoo-discuss/ meeting
- site:lists.osgeo.org/pipermail/zoo-discuss/ vote
- site:lists.osgeo.org/pipermail/zoo-discuss/ motion

Also not much found by searching
--
Jody Garnett


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

> Copyright and license
>
> 1. source license
>
> As above, break out into folder may be need?
>
> 2. Project documentation
>
> CC-BY-SA
>
> 3. providence review
>
> Check is completed in table
> http://zoo-project.org/trac/wiki/Provenance%20Review
>
> Doing some spot checks shows this to be outstanding, even files like
> schema.sql
> <http://www.zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql>
> has a header :)
>
> 4. The project maintains a list of all copyright holders
>
> I have kind of lost track of what this was about (like why it matters to
> have a list).  The answer provided is that the license file provides some
> of this information.
>
> This may be worth discussing with the incubation committee
>
> 5. contributors agree to project's license policy
>
> This is really seeking some kind of confirmation that the contributor
> (perhaps employer) was making open source on purpose.
>
> Looks like an email is sent as part of contribution guidelines.
> --
> 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/35612697/attachment-0001.html>