@pablobm commented on this pull request.
> +Before spending any significant time, we recommend that you create an issue
+or a draft PR that communicates your intention clearly.
+Make sure that you have buy-in from the maintainers and you will have a
+much easier time getting your code merged.
I have reworded the whole thing now. I tried to make some distinction between
features (which can find more resistance if unrequested) and bug fixes (which
_should_ be straightforward). All while not losing sight that both can end up
being more effort than initially planned and therefore should lean on
communicating early and often.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6543#discussion_r2545352772
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6543/review/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
