Learn more about these different git repos.
Other Git URLs
I've been told to change my attitude after sending this automated comment by a script in this repository:
Hello, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
Hello,
This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
I'd appreciate it if some native speaker helped me change the attitude of it so packagers don't feel offended by the script following the policy.
When do you need this? whenever
When is this no longer needed or useful? when we change the policy
If we cannot complete your request, what is the impact? packagers being offended
Metadata Update from @kevin: - Issue tagged with: low-gain, low-trouble
How does:
Hello, This is the ___ email on long term FTBFS following the process outlined at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs . The package is currently in a state where it no longer builds from source in the Fedora Build System and will be removed at ___ time if this does not change. 1. If you are able to fix this problem, please acknowledge by setting the bugzilla status to ASSIGNED. 2. If you are not able to fix this problem, please ask on the Fedora Devel list for help to see if others are able to do so. You may also orphan the package to allow others to take it over 3. If you have looked at the problem, and do not see this package able to be fixed, please move the bug to CANTFIX. This will allow for other maintainers of dependent packages to be better aware of the problem.
Here's my cut:
Greetings.
This is an automated comment, added by a script at https://pagure.io/releng/scripts/etc...
This package fails to install and maintainers are advised to take one of the following actions:
or
If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue and this package may be orphaned.
I like Kevin's better.
FWIW, I personally don't find the tickets offensive, but I know they're automated. I appreciate the time that you put in to the FTI/FTBFS/orphaning processes. It keeps the distribution in better shape, and I like knowing when my things are or will be broken.
This is also somewhat of a problem with other automated processes like SCM requests. With that, people get upset when their issue is closed as invalid and nobody responds to their comments.
In any case, I think softening the language and making clear that this is an automated process and not "Miro doesn't appreciate my contributions" will make the process better for everyone involved. I like Kevin's wording, but I think "will continue and this package may be orphaned" should be changed to "will continue and this package may be orphaned in 8+ weeks" so people know how long they have to fix the issue and aren't blindsided when the package is automatically orphaned.
I think the most significant improvement is adding "This is an automated comment" to make it clear it's not a human writing that to the assignee specifically. I think people tend to react differently when they realize something is automated, and are less likely to take it personally. @kevin's version with @gotmax23's slight adjustment sounds great to me.
I think the most significant improvement is adding "This is an automated comment"...
That was the first thing I've added: https://pagure.io/releng/pull-request/11167
Thanks folks. See https://pagure.io/releng/pull-request/11203
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.