Hi Paul! > -----Original Message----- > From: Paul Wouters [mailto:paul@xxxxxxxxx] > Sent: Tuesday, May 21, 2019 11:28 AM > To: Roman Danyliw <rdd@xxxxxxxx> > Cc: ietf@xxxxxxxx > Subject: Re: Call for Community Input: Web Analytics on www.ietf.org > > On Tue, 21 May 2019, Roman Danyliw wrote: > > > https://www.ietf.org/iesg/docs/www.ietf.org-AnalyticsProposal-forRevie > > w.pdf > > > > The IESG appreciates any input from the community on this proposal and > will consider all input received by June 4, 2019. > > I'm a bit confused that tools.ietf.org is not included. It's where I go mostly to > read RFCs. (in fact, I google "rfc XXX tools" to not get any ancient > www.ietf.org text versions but the proper html version on tools.ietf.org".. If the analytics meet their intent, the desired would be expand them across all of the web properties (e.g., tools.ietf, datatracker.ietf). However, in the spirit of starting with a smaller scope and getting operational experience, www.ietf was chosen as an initial target. > > Providing a publicly-available summary of analytics data will be explored. > > Since I'm part of the data collection, it makes sense to me to see the end > summary. I see no reason this should be restricted to the IESG and IETF > Secretariat - unless you don't trust your anonymization ? Agreed. This hesitance is a matter of not overcommitting, and getting initial operational experience with this new approach to gather usage data. Incomplete stats are currently shared at [1]. Thanks for the feedback. Roman [1] https://www.ietf.org/usagedata/ > Otherwise, the plan looks fine to me. > > Paul
