Bug 435794 - [pmi] Fix wording: "Request" a review instead of "Schedule" a review
Summary: [pmi] Fix wording: "Request" a review instead of "Schedule" a review
Status: CLOSED MOVED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Project Management & Portal (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Martin Lowe CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: polish
Depends on:
Blocks:
 
Reported: 2014-05-26 10:51 EDT by Wayne Beaton CLA
Modified: 2022-02-15 06:07 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2014-05-26 10:51:25 EDT
Only the EMO can actually schedule a review. The message at the top of the release record page, however, invites the committer to "Schedule" a review. This should read "Request" a review. Further, we need to provide more help to the committer to understand how the process works.

e.g. The EMO will schedule the review as soon as the IP Log has been approved by the IP Team, and the review materials have been approved by the PMC.

We should also note that the requested review period may be changed to align with other reviews (we are required by the board to limit the number of review periods to two/month).
Comment 1 Eclipse Genie CLA 2016-05-16 13:00:49 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2019-03-27 02:20:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Martin Lowe CLA 2019-10-02 15:00:06 EDT
(In reply to Wayne Beaton from comment #0)
> Only the EMO can actually schedule a review. The message at the top of the
> release record page, however, invites the committer to "Schedule" a review.
> This should read "Request" a review. Further, we need to provide more help
> to the committer to understand how the process works.
> 
> e.g. The EMO will schedule the review as soon as the IP Log has been
> approved by the IP Team, and the review materials have been approved by the
> PMC.
> 
> We should also note that the requested review period may be changed to align
> with other reviews (we are required by the board to limit the number of
> review periods to two/month).

Just to ensure I'm capturing all of the requirements of this issue, we should be enhancing the wording on the review request screen for listing releases. This update will remove any mention of scheduling to use the terminology "request". Additionally, the message about the review should be updated as follows:

Note that this is not a fully automatic process; the review will be created in a 'pending' state and must be approved by the PMC and EMO. The EMO will schedule the review as soon as the IP Log has been approved by the IP Team, and the review materials have been approved by the PMC.

Does that cover this request?
Comment 4 Wayne Beaton CLA 2019-10-18 11:22:04 EDT
+1
Comment 5 Eclipse Genie CLA 2021-10-13 11:25:25 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Frederic Gurr CLA 2022-02-15 06:07:19 EST
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/it/websites/projects.eclipse.org/-/issues/27.