I sent this diagram of ticket states around shortly after the last meeting, but I didn't get any comments back. So perhaps it would be better to send it to a wider audience. According to this diagram, any ticket in the "Not ready" / "Forum feedback requested" / "Waiting for reviews" state could be waiting for reviews. Perhaps we need something better than this (i.e., a separate bit indicating that a ticket is awaiting reviews). On Dec 5, 2008, at 11:13 AM, Supalov, Alexander wrote:

Hi,

It would be great to learn how to identify tickets that are up for review in the first place. All colors and fields I can see in the standard reports don't seem to help much in this.

Best regards.

Alexander

-----Original Message----- From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden] ] On Behalf Of William Gropp Sent: Friday, December 05, 2008 5:07 PM To: Bronis R. de Supinski; MPI 2.2 Subject: Re: [Mpi-22] MPI 2.2 Reminders

As an immediate step, we can do the following:

Authors of tickets that are ready for review should do the following: (a) add a comment to the ticket with the names of the reviewers (the relevant chapter author and 3 other volunteers) (b) contact the reviewers to remind them

Having a separate, searchable field would be nice, but this would capture the data now.

Bill

On Dec 5, 2008, at 10:00 AM, Bronis R. de Supinski wrote:

...

Bill and Jeff:

It will be really useful if the tickets listed reviewers. In the least we need some way to map tickets to reviewers (I am thinking about chapter authors in particular), Could Jeff add a field (or fields) that the owner is responsible for completing that indicates the reviewers?

As it is I am really unclear over what I am supposed to review. I am guessing there are at least one or two for my chapter...

Bronis

On Fri, 5 Dec 2008, William Gropp wrote:

...

Our next MPI 2.2 discussion is in just over a week, and we have a lot to do. Please have a look at the wiki for the following (see https:// svn.mpi-forum.org/trac/mpi-forum-web/report for the reports):

1) For your own tickets, make sure that they are up to date. If reviewers are needed, please contact them and encourage them to submit their reviews. If revised text is needed, please update the text and if you would like early feedback, notify this list.

2) For items on which you are a reviewer (particularly MPI 2.1 chapter authors), please review the relevant tickets. When you are reviewing text, make sure that you are looking at the current MPI 2.1 standard; check page and line numbers as well as the context to ensure that the change is correct.

3) For other tickets, review them and raise any issues that you have *now* so that we can start the discussion before our meeting.

Thanks!

Bill

-- Jeff Squyres Cisco Systems *