Re: [ietf-outcomes] [OPS-AREA] IETF Outcomes wiki

In line. 

Regards,

Dan

> -----Original Message-----
> From: ietf-outcomes-bounces@ietf.org 
> [mailto:ietf-outcomes-bounces@ietf.org] On Behalf Of Dave CROCKER
> Sent: Wednesday, February 10, 2010 10:02 PM
> To: ietf-outcomes@ietf.org
> Subject: Re: [ietf-outcomes] [OPS-AREA] IETF Outcomes wiki
> 
> 
> 
> On 2/10/2010 2:45 AM, Romascanu, Dan (Dan) wrote:
> > 'The wiki is only as complete and accurate as community 
> effort makes it.'
> >
> > It would probably be good to add a phrase that makes clear that the 
> > information contained here does not represent the consensus 
> of the IETF.
> 
> 
> I'll offer a friendly amendment, in the hopes of achieving 
> some... ummm... 
> consensus...
> 
> 
> Outcomes home page
> ------------------
> 
> Currently:
> > The IETF has operated in its current form since 1989. Some of its 
> > standards have succeeded on a very large and visible scale. 
> Others are 
> > successful, but visible only to a more limited community. 
> Others have 
> > fared poorly. This wiki lists technologies and services that were 
> > developed in the IETF and represent notable successes or 
> failures. It 
> > is a collaborative effort of IETF participants, to provide 
> feedback to 
> > the community about the utility of IETF efforts, as well as to 
> > facilitate public understanding of IETF work and impact.
> 
> 
> Proposed revision:
> 
> The IETF has operated in its current form since 1989. Some of 
> its standards have succeeded on a very large and visible 
> scale. Others are successful, but visible only to a more 
> limited community. Others have fared poorly. This wiki lists 
> technologies and services that were developed in the IETF and 
> represent notable successes or failures. It is an informal, 
> collaborative effort of IETF participants, to provide 
> feedback to the community about the utility of IETF efforts, 
> as well as to facilitate public understanding of IETF work and impact.
> The contents of the are revised according to the views of 
> individual contributors and have not been subject to IETF 
> Rough Consensus assessment.

Looks OK but the phrase is missing something, maybe the word 'wiki'
between 'the' and 'are'. 

> 
> 
> 
> Charter page
> ------------
> 
> Currently:
> 
> > The IETF produces technical specifications, with the goal of their 
> > being used on the Internet. Once a specification is 
> published, there 
> > is no formal mechanism for assessing the eventual utility 
> of the work. 
> > However feedback about successes or problems can be useful in 
> > developing a shared community sense of the way work is -- 
> or should be 
> > -- done. The IETF Outcomes Wiki is a collaborative effort 
> to produce 
> > subjective assessments about successes and failures of 
> notable efforts, based on rough consensus.
> 
> 
> Proposed revision:
> 
> The IETF produces technical specifications, with the goal of 
> their being used on the Internet. Once a specification is 
> published, there is no formal mechanism for assessing the 
> eventual utility of the work. However feedback about 
> successes or problems can be useful in developing a shared 
> community sense of the way work is -- or should be -- done. 
> The IETF Outcomes Wiki is an informal, collaborative, 
> incremental effort among individual IETF participants, to 
> produce subjective assessments about successes and failures 
> of notable efforts.  Although tending to reflect a degree of 
> community agreement, the contents of the wiki are not subject 
> to formal IETF Rough Consensus assessment.

This looks OK to me. 

> 
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> ietf-outcomes mailing list
> ietf-outcomes@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-outcomes
> 