@1ec5 commented on this pull request.
The roadmap is something I put together based on discussions with various
folks, not just contributors to this project. It’s in a separate repository to
give maintainers like @tomhughes a bit of breathing room. Even so, you have a
pretty important say about what goes in, since obviously it would be a work of
fiction otherwise. It’s intended to be a resource rather than a specification,
so if we need to correct or course-correct, that’s an important conversation to
have.
> +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.
Some people keep thinking have to ask for an issue to get assigned to them. We
have a note about that just above here, but it probably needs to have more
nuance. Basically, most bug reports are pretty straightforward, but feature
requests really need buy-in about the concept and design before diving in too
deep.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6543#pullrequestreview-3483824549
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
