Re: [pm-dir] Performance metrics doctors generated email - new version.

["MORTON JR., ALFRED (AL)" <[e-mail]>]

Hi Paul,

Thanks for continuing the discussion on tracking
draft review assignments and status.  I've been discussing 
this off-list with Benoit. Let me put my position on
the table here.

I'd prefer a solution where:
 - everyone can view the page
 - directorate reviewers can edit the page
 - all editing is WYSIWYG
 - no collisions between editors
  (if two people are editing, they can see each other and 
   pressing save does not overwrite a nested editing session)

Unfortunately, the last two points are beyond Trac's capability.
I think that I could create a doc on Google Drive that
would meet all the above criteria.
  
But, all Directorate members who are active/performing reviews
would need to have an account on Google and be willing to use
it for this purpose. I suspect that many of us already have
a gmail account.

If there is another solution that meets all the points above,
we could consider that as well.

Let's hear from all Directorate members on this, it's a cross-road
that will affect how we work together in the future.

regards,
Al


> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf
> Of Paul Aitken
> Sent: Friday, February 15, 2013 6:12 AM
> To: Benoit Claise
> Cc: [e-mail]; Alan DeKok
> Subject: Re: [pm-dir] Performance metrics doctors generated email - new
> version.
> 
> Benoit,
> 
> How often is the script run? I haven't seen any more postings these last
> 10 days.
> 
> If it's run regularly - eg, weekly or nightly - then it'd be useful as
> Al said, to send a delta from the previous run so we can easily see what
> changed.
> 
> I saved the current(?) list at
> http://trac.tools.ietf.org/wg/pmol/trac/wiki
> You could imagine additional columns, eg reviewer, comments, status, so
> the status and history can be seen at a glance.
> 
> Is this useful?
> 
> P.
> 
> 
> On 04/02/13 12:06, Benoit Claise wrote:
> > Dear all,
> >
> > This is a new version of the script, provided by Alan Dekok. Many
> > thanks Alan.
> > The important improvement is that we also list the drafts that contain
> > a specific keyword.
> > In this case, "performance metric". We could add some more...
> > With this new script, we can then engage sooner with the people who
> > don't know about this directorate and RFC 6390.
> >
> > Potential small optimization for the script: remove the drafts that
> > contain "performance metric" and that already reference RFC 6390
> >
> > Regards, Benoit
> >> Dear all,
> >>
> >> This is an automatically generated email.
> >> It lists the IETF internet-drafts that reference the PMOL RFC 6390,
> >> as a normative or informative reference.
> >> It also lists all the IETF internet-drafts that contain "performance
> >> metric".
> >>
> >> Regards, Benoit
> >>
> >> ===========================================================
> >>
> >> Normative References
> >> --------------------
> >> draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05 Active
> >>      Informative References
> >> ----------------------
> >> draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10   In IESG processing
> >> - ID Tracker state <Publication Requested>
> >> draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08      In IESG processing
> >> - ID Tracker state <Publication Requested>
> >> draft-ietf-xrblock-rtcp-xr-concsec-03             Active
> >> draft-ietf-xrblock-rtcp-xr-decodability-07        Active
> >> draft-ietf-xrblock-rtcp-xr-discard-11             Active
> >> draft-ietf-xrblock-rtcp-xr-jb-07                  Active
> >> draft-ietf-xrblock-rtcp-xr-loss-conceal-04        Active
> >> draft-ietf-xrblock-rtcp-xr-qoe-03                 Active
> >>
> >> drafts containing performance metric
> >> ------------------------------------
> >> draft-ietf-alto-deployments-05                    Active
> >> draft-ietf-alto-protocol-13                       In IESG processing
> >> - ID Tracker state <AD Evaluation::Revised ID Needed>
> >> draft-ietf-ippm-rate-problem-02                   Active
> >> draft-ietf-ippm-testplan-rfc2680-01               Active
> >> draft-ietf-karp-threats-reqs-07                   In IESG processing
> >> - ID Tracker state <RFC Ed Queue>
> >> draft-ietf-manet-olsrv2-mib-05                    Active
> >> draft-ietf-manet-smf-mib-06                       Active
> >> draft-ietf-mmusic-media-loopback-27               In IESG processing
> >> - ID Tracker state <RFC Ed Queue>
> >> draft-ietf-nvo3-framework-01                      Active
> >> draft-ietf-opsawg-oam-overview-08                 In IESG processing
> >> - ID Tracker state <Waiting for AD Go-Ahead::Revised ID Needed>
> >> draft-ietf-rtcweb-rtp-usage-05                    Active
> >> draft-ietf-rtgwg-cl-framework-02                  Active
> >> draft-ietf-xrblock-rtcp-xr-burst-gap-discard-10   In IESG processing
> >> - ID Tracker state <Publication Requested>
> >> draft-ietf-xrblock-rtcp-xr-burst-gap-loss-08      In IESG processing
> >> - ID Tracker state <Publication Requested>
> >> draft-ietf-xrblock-rtcp-xr-concsec-03             Active
> >> draft-ietf-xrblock-rtcp-xr-decodability-07        Active
> >> draft-ietf-xrblock-rtcp-xr-discard-11             Active
> >> draft-ietf-xrblock-rtcp-xr-discard-rle-metrics-05 Active
> >> draft-ietf-xrblock-rtcp-xr-jb-07                  Active
> >> draft-ietf-xrblock-rtcp-xr-loss-conceal-04        Active
> >> draft-ietf-xrblock-rtcp-xr-qoe-03                 Active
> >> draft-ietf-xrblock-rtcp-xr-summary-stat-06        In IESG processing
> >> - ID Tracker state <Waiting for AD Go-Ahead>
> >> draft-ietf-xrblock-rtcp-xr-synchronization-02     Active
> >> _______________________________________________
> >> pm-dir mailing list
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/pm-dir
> >>
> >>
> >
> > _______________________________________________
> > pm-dir mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/pm-dir
> 
> _______________________________________________
> pm-dir mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/pm-dir