Re: WIMSE WG Landing Page

["Andrew G. Malis" <[e-mail]>]

Joel,

For your A2 question, the obvious place for a pointer is in the "Additional
resources" field on the WG's About page in the Datatracker. Many WGs
already use this field to include pointers to their Wiki and Github pages
(you can have multiple pointers in the field).

And of course, you would also advertise it in the WG Chair's intro slides
for each IETF meeting.

Cheers,
Andy


On Wed, Oct 30, 2024 at 4:31 PM Joel Halpern <[e-mail]> wrote:

> I have two reactions to Richard's question.  Before stating them, let me
> be clear that this is clear a useful tool.
>
> A1) As the IETF discovered several times over several years, the risk with
> free tools is that someone still has to maintain them.  That is why we
> moved to the current model.
>
> A2) The one drawback of what is being done is that the only way folks find
> that useful page is if they run into someone who tells them about it.
> Including the page in some useful place that is pointed to by other things
> would seem helpful.  However, every time I try to come up with a suggestion
> for where to put such pages, I fail.
>
> Yours,
>
> Joel
> On 10/30/2024 4:23 PM, Richard Barnes wrote:
>
> In what way would that be better than a simple, free tool that already
> exists and we don't have to maintain?
>
> Thanks for sharing, Justin :)
>
> On Wed, Oct 30, 2024 at 12:11 PM Michael Richardson <[e-mail]>
> wrote:
>
>>
>> Justin Richer <[e-mail]> wrote:
>>     > In WIMSE, we recently had one of our members put together a
>> fantastic
>>     > landing page for the working group, which we’ve got online at
>>     > https://ietf-wg-wimse.github.io/ with all of its code available at
>>     > https://github.com/ietf-wg-wimse/ietf-wg-wimse.github.io … if you
>> poke
>>     > around there, you’ll see it’s a single page with some relatively
>>     > straightforward CSS and HTML. No frameworks, no generators, no
>> dynamic
>>     > content. This means that it’s fairly easy to adapt, and SPICE has
>>     > already taken this shell and applied their own content to it at
>>     > https://ietf-wg-spice.github.io/
>>
>> Very nice.
>> How can we get this inhouse, since it's just static content?
>> Why wasn't the wiki enough?
>>
>> --
>> Michael Richardson <[e-mail]>, Sandelman Software Works
>>  -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*
>>
>>
>>
>>