[MapProxy-dev] New and existing PRs and issues

[Ramūnas Dronga]

Hello,
You are right, PR #471 it's just for easier deploys, does not fix anything
in mapproxy itself.

Regarding PR in general, I think we can discuss and vote there. Would be
easier to understand the whole context.
And right now there is no need to vote for each PR in mapproxy-dev, see [1]

[1]
https://github.com/mapproxy/mapproxy/wiki/PSC-Guidelines#when-is-a-vote-required


On Tue, 29 Sep 2020 at 10:44, Johannes Weskamm <weskamm at terrestris.de>
wrote:

> Hi all,
>
>
> As a new Pull Request appeared today, i think we should talk about how
> to finally handle existing and new PRs.
>
> The new PR can be found here:
> https://github.com/mapproxy/mapproxy/pull/471
>
> I am interested in your opinions, do we have to vote for this? I
> personally think that the issue the author tries to solve may be fixed
> by a specific web server configuration (proxy config) and does not need
> a change in mapproxy itself, but i may be wrong.
>
>
> Besides, do we start discussion / voting directly in the PR?
>
> And what about existing PRs, should we check all of them against the
> current "rules" ?
>
>
> Greetings,
>
> Johannes
>
>
> _______________________________________________
> MapProxy-dev mailing list
> MapProxy-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy-dev
>


-- 
Best Regards / Pagarbiai,
Ramūnas
+37060047423
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20200929/fc56ca5f/attachment.html>