[Mpi-22] MPI 2.2 Reminders

[Bronis R. de Supinski]

Both solutions (Jeff's and Bill's -- particularly b) work for me.
At this point, I have received no emails (either automatic or not)
so I will assume nothing is ready for my review until I do.

On Fri, 5 Dec 2008, Jeff Squyres wrote:

> FWIW, I've been telling people to use the "CC" field to fill in the
> email addresses of reviewers.
>
> Not only does this make a searchable list of reviewers (by e-mail
> address, at least), but it also makes them get emails when the ticket
> changes.
>
> It ain't perfect, but it seems to work...
>
>
> On Dec 5, 2008, at 11:07 AM, William Gropp wrote:
>
> > 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
> >>>
> >>> William Gropp
> >>> Deputy Director for Research
> >>> Institute for Advanced Computing Applications and Technologies
> >>> Paul and Cynthia Saylor Professor of Computer Science
> >>> University of Illinois Urbana-Champaign
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> mpi-22 mailing list
> >>> mpi-22_at_[hidden]
> >>> http://  lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
> >>>
> >>>
> >> _______________________________________________
> >> mpi-22 mailing list
> >> mpi-22_at_[hidden]
> >> http:// lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
> >
> > William Gropp
> > Deputy Director for Research
> > Institute for Advanced Computing Applications and Technologies
> > Paul and Cynthia Saylor Professor of Computer Science
> > University of Illinois Urbana-Champaign
> >
> >
> >
> >
> > _______________________________________________
> > mpi-22 mailing list
> > mpi-22_at_[hidden]
> > http:// lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
>
>
> --
> Jeff Squyres
> Cisco Systems
>
>
>