Am Freitag, dem 17.01.2025 um 09:32 +0000 schrieb 45mg: > Hi Guix, > > I have seen different opinions [1][2] regarding sending pings to > patches that aren't getting reviewed or are otherwise lacking > attention. > > To get a better idea of peoples' opinions, I've created a survey. > Please do take it, it's only two questions long. > > https://sneakmonkey.limesurvey.net/286966?lang=en > > I think it would be good for Guix to have stated guidelines on this > subject, so that everybody knows in advance what is considered > acceptable and what isn't. Right now it is difficult for a new > contributor to judge whether sending a ping will help or not. > Hopefully the survey is a step in the right direction. For context, I already took the survey, but here are some comments that didn't quite make the cut for lack of a free-form field with additional concerns:
1. You should only ping a contribution that require action from committers/reviewers to be pushed forward. Do not ping contributions that have received reviews on which you haven't acted yet. 2. You should not automate the process of pinging old bugs, but instead ping issues that are still important to you after the delay has elapsed. 3. If possible, send updated patches rather than pings. For instance, if your commit that bumps libfoo to x.y.z hasn't received attention, you may still, without review, submit a v2 that bumps it to x.y.z+1. Likewise, you may improve code style, etc. to keep your patch fresh. 4. Avoid contextless pings – do provide information for readers to move your patch forward. 5. Make sure that the right people are informed. (For example, consult etc/teams.scm) Hope that helps ;)
