Re: Update and move of codimd

Toerless Eckert <tte@cs.fau.de> Wed, 11 August 2021 19:52 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B90A13A223A; Wed, 11 Aug 2021 12:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OE-Bly1bApw5; Wed, 11 Aug 2021 12:52:12 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E96A23A2238; Wed, 11 Aug 2021 12:52:09 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 22798548015; Wed, 11 Aug 2021 21:52:01 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 1C7E84400EF; Wed, 11 Aug 2021 21:52:01 +0200 (CEST)
Date: Wed, 11 Aug 2021 21:52:01 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: Greg Wood <ghwood@ietf.org>, Working Chairs <wgchairs@ietf.org>, Mark Nottingham <mnot@mnot.net>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Update and move of codimd
Message-ID: <20210811195201.GF23297@faui48f.informatik.uni-erlangen.de>
References: <4A6FEAAF-C9DE-4CFE-A08E-E8239EA0ACB2@nbcuni.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4A6FEAAF-C9DE-4CFE-A08E-E8239EA0ACB2@nbcuni.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/J1nBaKSIZJaURnvEQ_NSO7mqhfs>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2021 19:52:19 -0000

Thanks Glenn,

I don't think etherpad was ever limited to just meeting minutes even
when its main offical use was such. I have seen it being used also 
to track ongoing discussions of technical items and as such pages 
being updated sometimes over months (i think).

We simply need a declaration as to what the tools team does and does
not commit to do.

E.g.: if i put something into a notes.ietf.org page, what period
of time will IETF attempt to keep up that pages content before it might
get erased by IETF activity for whatever reason (new software versions,
change of server/URL, whatever). 

Maybe we want to discourage to use this for ongoing edits longer than
e.g.:2 months, or whatever the reasonable prepare, live and post-edit phase
for meeting minutes is. Even if declaring that intent is the only thing we
do, and the content (like on codimd) hangs around opportunistically forever -
or until somebody thinks we need a better tool in 2 years ;-)

Cheers
    toerless

 On Wed, Aug 11, 2021 at 07:07:41PM +0000, Deen, Glenn (NBCUniversal) wrote:
> Hi
> 
> The contents of notes.ietf.org should all be covered by Notewell (https://www.ietf.org/about/note-well/)  since they are part of an IETF meeting or interim meeting and Notewell applies to those meetings.
> 
> The IETF Trust will own the copyright just like it does for the videos recorded of the meeting sessions.
> 
> It might make sense to add some boiler plate noting the Notewell applies at the top of new notes when first created.  I realize that this can be edited out, but placing it there is a nice reminder.
> 
> In terms of archiving, that might be redundant (and unneeded) since once the group chairs submit it the notes to Datatracker they get the Datatracker treatment that the other Contributions to the IETF get.
> 
> -glenn
> 
> On 8/11/21, 9:19 AM, "WGChairs on behalf of Toerless Eckert" <wgchairs-bounces@ietf.org on behalf of tte@cs.fau.de> wrote:
> 
>     I would like to see a clear description of the expected rules of use:
> 
>     e.g.:
> 
>     Q: is everything put into notes.ietf.org deemed public ?
>     Q: If not deemed public, then what exactly is the deemed level of
>        confidentiality ? "AD-hoc - if you do not share a page name, its kinda confidential ?"
> 
>     Q: Would it be permissible for IETF to create a public list of all pages ?
>     Q: Wold it be permissible for IETF to make content older than some time (e.g.: 3 years) public ?
> 
>     Q: Is there an expectation for pages to be archived ?
> 
>     Q: If there is no expectation of archival of pages, how long
>        will pages be guaranteed not to be changed/taken-down by IETF ?
> 
>     Q: If pages are not deemed public, how then would use of this tool
>        go along with the IETF note well ?
> 
>     Aka: IMHO, all pages should be deemed public, there actually should be a
>     list/search across them, and that way archiving and IETF note well are not an issue.
> 
>     Cheers
>         Toerless
> 
>     On Wed, Aug 11, 2021 at 09:32:30AM -0400, Greg Wood wrote:
>     > Hi Mark (and everyone),
>     > 
>     > I’m looking into what’s possible at the moment, but if there are specific attributes you think would make the “Intro” page more useful, please feel free to send suggestions directly to me.
>     > 
>     > -Greg
>     > 
>     > 
>     > > On 10, Aug2021, at 20:01, Jay Daley <jay@ietf.org> wrote:
>     > > 
>     > > Looping in Greg as the person responsible for adding IETF branding to new services.
>     > > 
>     > > I believe a custom /intro.md is supported so this is possible.
>     > > 
>     > > Jay
>     > > 
>     > >> On 11/08/2021, at 11:38 AM, Mark Nottingham <mnot@mnot.net> wrote:
>     > >> 
>     > >> Nice!
>     > >> 
>     > >> Are we planning to update the front page to IETF-brand it?
>     > >> 
>     > >> 
>     > >>> On 11 Aug 2021, at 6:59 am, Robert Sparks <rjsparks@nostrum.com> wrote:
>     > >>> 
>     > >>> This is done.
>     > >>> 
>     > >>> The result is at notes.ietf.org.
>     > >>> 
>     > >>> RjS
>     > >>> 
>     > >>> On 8/6/21 6:19 PM, Mark Nottingham wrote:
>     > >>>> Just a suggestion - can we use a host name that reflects the function, rather than the product used?  Eg ‘pad.ietf.org’?
>     > >>>> 
>     > >>>> Sent from my iPhone
>     > >>>> 
>     > >>>>> On 7 Aug 2021, at 5:40 am, Robert Sparks <rjsparks@nostrum.com> wrote:
>     > >>>>> 
>     > >>>>> FYI -
>     > >>>>> 
>     > >>>>> Next Tuesday 10 Aug, around 2000 UTC, we will be moving where codimd.ietf.org is running, and moving to the latest version (which will reflect the rename of the project to Hedgedoc). Editing and reading notes during that time may be interrupted.
>     > >>>>> 
>     > >>>>> RjS
>     > >>>>> 
>     > >>>>> 
>     > >>>>> 
>     > >> 
>     > >> --
>     > >> Mark Nottingham   https://urldefense.com/v3/__https://www.mnot.net/__;!!PIZeeW5wscynRQ!56nGoBi0eqPWWA3dJcFs3T2Oq84z2CBtmspNWnd9SEXpMMZVo8ZsrPaaY0bKJdri$ 
>     > >> 
>     > > 
>     > > -- 
>     > > Jay Daley
>     > > IETF Executive Director
>     > > jay@ietf.org
>     > > 
> 
>     -- 
>     ---
>     tte@cs.fau.de
> 
> 

-- 
---
tte@cs.fau.de