#3896 closed enhancement (fixed)
Please add a 'needs-privacy-review' Workflow keyword
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Trac | Keywords: | has-patch commit |
| Cc: |
Description (last modified by )
Hello,
Following from recent meetings in #core-privacy we'd like to formally request a needs-privacy-review Workflow Keyword be added to Trac (Core/Meta/etc).
Originally proposed in Oct 17th 2018 meeting - https://make.wordpress.org/core/2018/10/19/core-privacy-office-hours-summary-17-october/
Following the existing definitions - https://make.wordpress.org/core/handbook/contribute/trac/keywords/
Proposed definition;
needs-privacy-review
A review is requested from #core-privacy with regards to the problem or the solution.
And should probably also add a 'has-privacy-review' tag to follow the other conventions with the definition of:
has-privacy-review
A review has been given from #core-privacy with regards to the problem or the solution.
This would allow developers to flag issues to #core-privacy people so they may conduct a review and indicate any privacy concerns.
Thank you
Attachments (2)
Change History (18)
This ticket was mentioned in Slack in #core-privacy by garrett-eclipse. View the logs.
7 years ago
#4
@
7 years ago
- Keywords needs-patch added
If someone wants to create a patch, adding the new keyword to wp-trac.js is what's required:
#5
follow-up:
↓ 7
@
7 years ago
Thanks @netweb I attempted this in 3896.diff
I understand this adds it to the WorkFlow Keywords. But I was wondering about the custom report under 'Tickets Needing Feedback' found here;
https://make.wordpress.org/core/reports/
I didn't see the make site in the meta repo is it controlled somewhere else?
Appreciated, Cheers
#7
in reply to:
↑ 5
;
follow-up:
↓ 8
@
7 years ago
Replying to garrett-eclipse:
Thanks @netweb I attempted this in 3896.diff
@garrett-eclipse If you're going to add the has-privacy-review then you'll also want to duplicate the functionality seen with similar keywords further down the code here. What this code does is acts as a toggle, if the keyword has-prvicacy-review is added then the needs-privacy-review keyword is removed.
I understand this adds it to the WorkFlow Keywords. But I was wondering about the custom report under 'Tickets Needing Feedback' found here;
https://make.wordpress.org/core/reports/
The reports listed on that link above come from reports generated via this page:
The custom keywords such as needs-screenshots and needs-privacy-review are not supported in these base reports. And for now just as needs-screenshots is not listed as a "report" on https://make.wordpress.org/core/reports/, needs-privacy-review would also not be listed, for now at least.
The Privacy component maintainers can edit the https://make.wordpress.org/core/components/privacy/ page, so adding a link to https://core.trac.wordpress.org/query?status=!closed&keywords=~needs-privacy-review on that page would be the way to go
#8
in reply to:
↑ 7
@
7 years ago
Replying to netweb:
@garrett-eclipse If you're going to add the
has-privacy-reviewthen you'll also want to duplicate the functionality seen with similar keywords further down the code here. What this code does is acts as a toggle, if the keywordhas-prvicacy-reviewis added then theneeds-privacy-reviewkeyword is removed.
I missed that thanks for the tip @netweb updated in 3896.2.diff
Replying to netweb:
I understand this adds it to the WorkFlow Keywords. But I was wondering about the custom report under 'Tickets Needing Feedback' found here;
https://make.wordpress.org/core/reports/
The reports listed on that link above come from reports generated via this page:
The custom keywords such as
needs-screenshotsandneeds-privacy-revieware not supported in these base reports. And for now just asneeds-screenshotsis not listed as a "report" on https://make.wordpress.org/core/reports/,needs-privacy-reviewwould also not be listed, for now at least.
The Privacy component maintainers can edit the https://make.wordpress.org/core/components/privacy/ page, so adding a link to https://core.trac.wordpress.org/query?status=!closed&keywords=~needs-privacy-review on that page would be the way to go
Thanks for pointing me in the right direction, I agree let's leave them off 'for now at least' until there's some traffic worthy of linking. And then we'll get it on the component page and reports page.
Looking at the Core Reports it would make sense to have a link to these tickets added under the 'Tickets Needing Feedback' section;
https://make.wordpress.org/core/reports/