[Incubator] Masterportal application to OSGeo community program

[Jody Garnett]

Catching up with master portal:

The team has applied back in January, and have been working on meeting our
requirements for code of conduct, code review and so forth.


   1. Be geospatial
      - Confirm by checking README or project description

      https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/README.md

      - project page on the osgeo website
      https://www.osgeo.org/projects/masterportal/ (looks good)
      - We ask projects have some user documentation, for example an OSGeo
      Live quickstart

      https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/doc/setup.md

      2. Have a free license or an open source license.
      - The license must be OSI approved

      https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/License.txt
       (MIT)
      - We ask that the project team check the file headers and double
      check the license has been appropriately applied
      Not sure I see this anywhere yet? Seeking a statement from the team...
      Doing a spot check of a few files:
      -
         https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/modules/menu/checkChildrenDatasets.js
(no
         header)
         -
         https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/modules/menu/desktop/staticlink/view.js
(no
         header)
         -

*Jody: So not sure what to do here, perhaps provide the team with examples?
         The point is not really the headers, the point is the
confidence that you
         can distribute this as open-source Teams traditionally find a few code
         snippets from stack exchange, or an example from another project, that
         requires attention.*
      3. Welcome participation and new contributors.
      - We look for a clear contribution policy
         - *Jody: **I did not see anything here? The developers docs have
         code conventions and git workflow - but nothing about the
         contributing/license/side of things*
         -

*https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/cff117bb78225af2f3c01a3f895c8cec3e792e4f/doc/gitWorkflow.md
         <https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/cff117bb78225af2f3c01a3f895c8cec3e792e4f/doc/gitWorkflow.md>
         This indicates some boundaries about external-developers and
commit rights,
         but not about permission or providence of code being offered as a
         pull-request. This boundary about commit rights is fine for an "osgeo
         community" project, but not for a full "osgeo project" which
requires some
         avenue for folks to ear full commit rights and participate in the
         governance of Masterportal.*
      - We ask that the project demonstrate collaboration, perhaps with a
      history of bug report or pull requests
      https://bitbucket.org/geowerkstatt-hamburg/masterportal/pull-requests
      - Projects are required to have a code of conduct

      https://bitbucket.org/geowerkstatt-hamburg/masterportal/src/dev/CODE_OF_CONDUCT.md


The masterportal team is very intent on entering incubation; and keep
trying to skip ahead 🙂

I am going to take the unusual step of opening bug tickets for the
remaining discussion points:

   -
   https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues/1076/osgeo-community-project-application-clear
   -
   https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues/1077/osgeo-community-project-application-check


When these tickets are closed I will be happy to motion that this project
be accepted into the "osgeo incubation" program.
--
Jody Garnett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20230911/c863caed/attachment.htm>