Re: [Rfc-markdown] [irsg] Next iteration (was Experimental deployment of CodiMD)

Robert Sparks <rjsparks@nostrum.com> Wed, 17 June 2020 20:32 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C583A0AE3; Wed, 17 Jun 2020 13:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 No7IuglwlPGa; Wed, 17 Jun 2020 13:32:02 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D7953A0829; Wed, 17 Jun 2020 13:32:02 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 05HKW0pb040753 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 17 Jun 2020 15:32:01 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1592425922; bh=8chBmLC6okKOoz0d/6wZ0+0bzMpz5s/j7Vre3iInFoA=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=mGYhp2qjZW5HZ9PlmGKCoXKfh1nrnTFFF8I5uzGZbqdk+r5TFL8IbSh0y7psUDpbU yL7GhvF4PEpYtjLIcYUvRQythZXAHv4PdXeKcequKEXzGzPafINbQc0jZW46wON2VO p+Oze4xzAI2ZGDMGcJ1krJS8+VD9j9VxPircgfhU=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Carsten Bormann <cabo@tzi.org>
Cc: wgchairs@ietf.org, rfc-markdown@ietf.org
References: <1ddf1780-ca45-0da8-5c5d-c809ada46ff0@nostrum.com> <CALGR9oboqfA0iyrE4ybCFY7G2aWEChMq89oyL9fW+-y1jGjwCg@mail.gmail.com> <6637DB48-D371-42F5-8495-0D4FA7B32912@tzi.org> <CADyWQ+G9MKd1ZsHFTb-Ovt0ceEPVK-ECGt8p4cKVaLgHUfFqqw@mail.gmail.com> <39786019-9596-baa1-a328-eb67a318194b@nostrum.com> <3D76C545-E23C-4EFD-B55C-FF44759E386E@tzi.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <854bba4c-19e1-bd7e-e528-1bd95a2a7c45@nostrum.com>
Date: Wed, 17 Jun 2020 15:32:00 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <3D76C545-E23C-4EFD-B55C-FF44759E386E@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/L275jwW_7zylEHYMUFdoEJIo3TM>
Subject: Re: [Rfc-markdown] [irsg] Next iteration (was Experimental deployment of CodiMD)
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 20:32:15 -0000

On 6/17/20 3:20 PM, Carsten Bormann wrote:
> (This is the real-time markdown collaboration tool that is best known under its previous, now commercial name: hackmd.  It doesn’t do rfc-markdown right away, but often the ability to use snippets of markdown as editable material in a meeting is quite useful.  The tool even has a slide show mode!)
>
> Great news!  Thank you.
>
> Those that want to try this in various settings: There is a little pop-down in the right hand side of the tool that starts out with “editable — signed-in people can edit”.  In the long run, that may be the right setting, but until everyone has a datatracker account and gets used to using it, “freely — anyone can edit” may be the right, low-threshold setting during a meeting.
>
> Use
>
>    https://codimd.ietf.org/features?both
>
> to get an overview of what can be in these notes, and maybe
>
>    https://codimd.ietf.org/Cb5Guqn5RcmCptBWH1oLjg
fwiw, allow freeurl is set, so you can also create notes with readable 
names (like https://codimd.ietf.org/stir).
>
> to see some of that in action (upcoming ASDF BOF, maybe), and
>
>    https://www.ietf.org/id/draft-onedm-t2trg-sdf-00.html#section-2.2-3.1.1
>
> for how that later looks in the I-D or RFC...
>
> Grüße, Carsten
>
>
>> On 2020-06-17, at 21:43, Robert Sparks <rjsparks@nostrum.com> wrote:
>>
>> OAUTH2 integration with the datatracker is working now, and is the only way to login to https://codimd.ietf.org.
>>
>> The site has been stable. I encourage groups to try using this instead of etherpad for upcoming interims and for IETF108.
>>
>> Please let me know if you run into any difficulties.
>>
>> RjS
>>