[MapProxy-dev] MapProxy PSC, RFCs and GitHub PR

[Just van den Broecke]

Hello All,

And sorry for my delayed answer.

I work as an independent within Open Source Spatial under the company 
name Just Objects [0]. I am also chair of OSGeo.nl [1] the Dutch local 
chapter.

Fan and user of MapProxy about 10 years, running MP professionally for 
my map service Map5 [2] and various other projects.

I am developer within several (geopython) projects: Stetl 
(founder/lead), GeoHealthCheck (lead) and pygeoapi (also in PSC), all 
within the GeoPython GitHub org [3].

I have an interest in letting MP blossom and grow. Not just as I run MP 
professionally but also given recent developments in OGC REST APIs and 
their realization within the pygeoapi project (as Tom mentioned). We're 
looking into MP integration there.

[0] https://justobjects.nl
[1] https://osgeo.nl
[2] https://map5.nl
[3] https://github.com/geopython

Kind regards,

--Just

Just van den Broecke  just at justobjects.nl
Just Objects B.V.     tel +31 65 4268627
The Netherlands       https://justobjects.nl


On 13-05-20 14:10, Oliver Tonnhofer wrote:
> Hi everyone,
> 
> sorry for the slow progress on the PSC.
> 
> I'm happy that we now have a list of seven candidates for the PSC. All of you are long time users of MapProxy and most of you also contributed in the past. So far we have:
> 
> Denis Rykov
> Johannes Weskamm
> Just van den Broecke
> Matt Walker
> Oliver Tonnhofer
> Ramūnas Dronga
> Tom Kralidis
> 
> Maybe you can all introduce yourself with 2-3 sentences on how you are using MapProxy, your affiliation with a company that uses MapProxy, do you have any plans within your PSC membership?
> 
> 
> Next step is, that we all agree on the PSC guidelines. Please take a look at https://github.com/mapproxy/mapproxy/wiki/PSC-Guidelines which is more a less a copy of the guidelines from MapServer, OpenLayers and PyGeoAPI.
> Make sure you all understood the responsibilities: https://github.com/mapproxy/mapproxy/wiki/PSC-Guidelines#membership-responsibilities
> 
> The only major change is that I increased the review period from two days to five business days. I think two days is quite short. (Minor changes aren't affected by the voting process anyways and a revert is just one command away.)
> 
> I'm also not sure how we should handle GitHub issues & pull requests? Do we want to keep all discussion on this list? Do we want an RFC for each PR? Would be it be OK if the PR is the RFC and we only vote on the mailing list? Should we just add a PR template [0] and mention that they should write to the mailing list if they want to bring this PR forward? (Otherwise they would need to wait till one of us is enough interested in the PR to make an RFC on their own.)
> 
> I'm quite open to all of these options.
> 
> [0] https://help.github.com/en/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
> 
> 
> Regards,
> Oliver
>