-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Assessment Trial Service #1817
Comments
Possible bug candidates for trial:
I could not tell if the others were or were not covered by the pull request @walshbr has in progress re Python lessons. Maybe he can let me know if there are outstanding python bugs to add to the list. |
Small note: can we please make sure the bug fixer/tester is made aware of knock on implications of their recommendations (e.g. https://github.com/programminghistorian/jekyll/wiki/The-Programming-Historian-Digital-Object-Identifier-Policy-%28April-2020%29) |
In the case of #1672, the actionable they decided on was just to remove a particular paragraph. And #1662 the suggestion similarly was to modify the text (we should decide what that means re: DOIs before those changes are made). So I think #1669 or #1777 could be candidates for this (neither of those are covered by the PR I have open, which only closes #1768). |
@ZoeLeBlanc no they would not be a technical team member. As previously agreed, fixing bugs is editorial work not technical work. This would be a service for editors and would only apply to bugs within published lessons. Not wider problems with the website. |
We're moving towards a test on either #1777 or #1669 and will report to everyone when we know more about how it has gone. @svmelton will receive a recommendation in her role as ME and it will be her decision on how to proceed (fix or retire). We'll be doing this with our retirement and DOI policies in mind. |
Just keeping track of this old page on troubleshooting which is live but not linked anymore: https://programminghistorian.org/troubleshooting A possible solution for reducing false bug reports, if reworked. |
The trial will take place on ticket #1669 and @mariechristineb is going to conduct it. She will make a recommendation to @svmelton as the Managing Editor. We will then report to the team how this test went. |
@mariechristineb has now submitted her recommendation to @svmelton who will make a decision on the particular issue. We'll then be able to report to the team on the bug assessment process. |
The pull request with the fix has now been merged. |
Some suggestions for how we might take this process forward as a clear workflow:
|
I've added the proposed workflow for this to our Wiki using the copyediting workflow as a guide: https://github.com/programminghistorian/jekyll/wiki/Bug-Assessment If this is approved at the ProgHist board meeting #1824 I will set everything up for Managing Editors and we can start using it. |
I'm pleased to say we have majority support to offer this service on an on going basis. Thanks in particular to @mariechristineb and @svmelton for helping us test and refine the process. I've added instructions on using this service to the wiki and I will email MEs so they can ask any questions. https://github.com/programminghistorian/jekyll/wiki/Bug-Assessment |
As per issue #1790 we've had a suggestion for a 'big fixer / bug tester' as a paid service provided by ProgHist. This service would support managing editors (MEs) by assessing and making recommendations on bugs that are reported by users, drawing upon our guidelines for retirement.
In order to asses if this is helpful for MEs (the goal is to both resolve bug tickets faster and reduce the effort required of MEs) we are going to try a test of this service on an existing bug ticket.
I will be leading on the test, but the relevant ME will have full control over whether or not to accept the advice.
I hope to have this test completed to share feedback with the team as soon as practical.
The text was updated successfully, but these errors were encountered: