I used to maintain a small patch set of issues that affected me and were fixed on the GNOME bugzilla but ignored by main devs. This is was a motivating factor in my switch to to Unity years ago. Sad to hear this situation hasn't improved.

I don't want to agree with you, but I tried to make a few polishing contributions to GNOME games and they got ignored after the first developer response (they told me what to fix, I fixed it). They've been stagnant for over 3 years now.

Submitting changes and having them accepted by GNOME is an exercise in futility if you aren't a GNOME dev.

In order to prevent this PR from becoming too large to review, I left the spread test, the part of this feature which makes it work with user daemons (left a TODO) and the addition of ~/Snap, for follow-up PRs.

Open a separate PR to add Rails 6 to the CI matrix

This is failing CI because CI is testing against Rails < 6. I think the appropriate next steps are: Open a separate PR to add Rails 6 to the CI matrix Update this PR to only run CSP-related test code for Rails >= 6.0.0 Can you help with either or both of those?

I tried implement the retries with as little as possible change, but it's quite hard to do that and keep the code clean with the current system. If you prefer less changes, I'm happy to go back to just the first two commits:

This PR contains some minor changes, each in a separate commit so I can easily remove them if they are not wanted.

It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.

We've stated what's required multiple times now: #14540 (comment) #14540 (comment), and the follow up arguments weren't convincing. Follow Rafael's advice in new smaller PRs to advance this or it'll simply stay closed

When submitting new methods for consideration, it is best if each method (or tightly related set of methods) is in it's own pull request. If you have only one method to submit then a simple commit will do the trick. If you have more than one it best to use separate branches. Let me emphasizes this point because it makes it much more likely that your pull request will be merged. If you submit a bunch of methods in a single pull request, it is very likely that it will not be merged even if methods you submitted are accepted!

Forward refs to input component