[68ATTENDEES] Moving ahead with tools.ietf.org

On Tue, 27 Mar 2007, Henrik Levkowetz wrote:
> on 2007-03-27 11:52 Pekka Savola said the following:
>>   1) They should (for most part) replace the current IETF official pages.
>>      For example, a non-IETF-goer asked (IMHO appropriately), "why aren't
>>      the "tools.ietf.org/wg/foo" the official page, instead of the less
>>      informative official IETF page?
>>
>>      In other words, there has been a lot of very good tools activity, but
>>      some of that should really be taken a few steps ahead into
>>      'production' use.
>
> Agreed to some extent, but there's a matter of how this is done.  For
> instance, how much of the limited secretariat resources should be spent
> on moving tools pages over to the NSS servers?  My viewpoint has been
> that it's more important to get NSS to implement tracker extensions,
> which will provide input of information not available today, making more
> advanced services and information presentation possible.
>
> If we find a solution which (for now) accomplish 1) above by better cross-
> linking, the cost in NSS manpower and IASA funds would be much less, and
> we could accomplish this much faster.
...

Yeah, I agree that this is a fine line (and it would likely also slow down 
the further development of the tools) and is a reason why I haven't pushed 
for this more.

One potential cross-referencing approach might be to consider whether 
http://www.ietf.org/html.charters/wg-dir.html could provide references to 
the http://tools.ietf.org/wg/foo/ pages instead of the current ones.

(The only shortcoming with the tools WG page for non-IETF folks is that 
the charter of the group is not quite as obvious but I'm not sure if this 
could be made any better)

I haven't thought about whether the other current IETF pages should better 
be "toolsified", maybe so (e.g., direct pointers to tools-enabled IETF 
agendas or some I-D or RFC post-processing and diffing mechanisms).

>>   2) The tools site should have very easy changelog that describes all the
>>      changes made to services (or at least gives pointers to distinct,
>>      tool-specific changelogs).  Modifications and enhancements are made
>>      all the time, and you can't really exploit all of them unless you know
>>      what they are or stumble on them by accident.
>
> Good point.  I'll set up a RSS and/or Atom feed for tool changelog
> notes, and aggregate these into a once-per-week message on the
> tools-discuss list, and maybe a once-per-month message to ietf-announce.
>
> Does this sound like a plan?

Sounds excellent to me.  Please put a prominent "What's new?" or "What's 
changed?" on the web pages as well for the benefit of those who don't use 
RSS/ATOM feeds nor subscribe the mailing lists (e.g., non-IETF goers, 
non-regular participants).

_______________________________________________
68ATTENDEES mailing list
68ATTENDEES@ietf.org
https://www1.ietf.org/mailman/listinfo/68attendees