IETF Logo Mail Archive

Re: [Codestand-develop] Fwd: IETF CodeStand on revamped website

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 15 February 2017 15:16 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: codestand-develop@ietfa.amsl.com
Delivered-To: codestand-develop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ABB0129621 for <codestand-develop@ietfa.amsl.com>; Wed, 15 Feb 2017 07:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_IMAGE_RATIO_06=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LX2sjGuuMUTm for <codestand-develop@ietfa.amsl.com>; Wed, 15 Feb 2017 07:15:58 -0800 (PST)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 2EC091295A6 for <codestand-develop@ietf.org>; Wed, 15 Feb 2017 07:15:58 -0800 (PST)
Received: by mail-qk0-x22c.google.com with SMTP id p22so62385544qka.0 for <codestand-develop@ietf.org>; Wed, 15 Feb 2017 07:15:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aHEaKKTa1041K0CzBXrptq4M5+82rlXz1ZT1k3nQbws=; b=l3meb5PQQU+K9qlXFxuAzpCGzYBCE94V9iiHZ/LVG0pKejETa2Bxqtypj0pWPs1iRJ H6qSFlM3vpIpizHC53Z4QtNAnb0kAw/XQlx2kGyGS2F3BydjhhvHJNzdhQKlpCizWsRa BpBLExzTwk1WH1RFPW48fNT96cQu8t4oeszlA6zXoIdeVdIDyRAebaNbhCMmFPO5pcWm 9W6SM26tP0Mq0lagXLG8xwCZtk3+6bZ8NKt5sCR2KXCytIcYfHJweUw3FxqQ8ypewThM bYfFTgc/tegX4bfpqpGfHT99Yv2nkf3NFT6h6dUljlOc6jcmRD5hTWlXqBi1RjTuEq7h 9whA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aHEaKKTa1041K0CzBXrptq4M5+82rlXz1ZT1k3nQbws=; b=kGa83MWfyETeH5M1p2Noa4pq0QlkjtV+5PLFUBuEPF/EPpIaK0ZML+nDbLP/HLk6NB CpgwEVKUwgYga8MYndDwjbiQw6lC1lgqhX5g+vo58YXys/EHJV73ad15s/LDgb9wQKq1 vply+DomgWuZ36ejtZfuYMymO3BWqNQ65j7rdyEbu+jkqSMAk5GU1F415bKm3l5nJYKn yrcJuPkuELxH+CsQ2llBBU0yc8COUOeCm7+WuHDNpeeIpiWUvngyJo3SH6GKgzT+xomF 1FXt0L5n5KqYeyuUaj0qPkOkTVblG1tUAEOfLWISji24O3722Ufd1K/cB4v0356UWXsk MhBg==
X-Gm-Message-State: AMke39l7DR5Tf5fTG7cVKb2GuSOmwXvfj28FQSoD8QDiEojklq+F/+1d9ydu3jamgA2vKgOw7aLfFbiNgLj3xA==
X-Received: by 10.55.9.15 with SMTP id 15mr33057048qkj.118.1487171757332; Wed, 15 Feb 2017 07:15:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.170.30 with HTTP; Wed, 15 Feb 2017 07:15:56 -0800 (PST)
In-Reply-To: <CF2217A4-CB7A-460C-BE4A-8FA06EC28105@isoc.org>
References: <FBBD8CBD-A67C-4184-ACBC-B58DB48B6EE2@isoc.org> <CF2217A4-CB7A-460C-BE4A-8FA06EC28105@isoc.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 15 Feb 2017 10:15:56 -0500
Message-ID: <CAHbuEH7ymYza0Dpt5WxBTHEULqx4ztfoW81tJSzdp-S9t2P7kw@mail.gmail.com>
To: "Christian O'Flaherty" <oflaherty@isoc.org>
Content-Type: multipart/related; boundary=001a114c847251613b05489328f2
Archived-At: <https://mailarchive.ietf.org/arch/msg/codestand-develop/X1nZSDWBlPInM_DkSwPPvV7oso0>
Cc: "codestand-develop@ietf.org" <codestand-develop@ietf.org>
Subject: Re: [Codestand-develop] Fwd: IETF CodeStand on revamped website
X-BeenThere: codestand-develop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "\"Discussion forum for the planning, coordination, and development of CodeStand\"" <codestand-develop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codestand-develop>, <mailto:codestand-develop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codestand-develop/>
List-Post: <mailto:codestand-develop@ietf.org>
List-Help: <mailto:codestand-develop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codestand-develop>, <mailto:codestand-develop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 15:16:01 -0000

Thanks, Christian & Greg!

I have the BoF planning call today, so I may be late or wind up not being
able to join, but will do my best.

On Wed, Feb 15, 2017 at 9:47 AM, Christian O'Flaherty <oflaherty@isoc.org>
wrote:

> Hi team,
>
> Find below an email from Greg Wood who is working with others in the
> updated IETF site.
>
> We can include a section in “How We Work” -> “Running Code” -> “Codestand"
>

Very good!

>
> He has already suggested some text (included below) and he has a couple of
> asks...
>
> Christian O'Flaherty  oflaherty@isoc.org
> Regional Development - Internet Society
> Skype/Gmail/Yahoo!:  christian.oflaherty
> Mobile/WhatsApp: +598 98769636 <+598%2098%20769%20636>
>
> Begin forwarded message:
>
> *From: *Greg Wood <wood@isoc.org>
> *Subject: **Re: IETF CodeStand on revamped website*
> *Date: *February 15, 2017 at 8:47:21 AM GMT-3
> *To: *Christian O'Flaherty <oflaherty@isoc.org>
>
> Hi Christian,
>
> I can’t join the call today, but the article text is very helpful. Here’s
> some text I’d propose.
>
>
> CodeStand connects the IETF standards process with open source and
> proprietary software. Authors of IETF Documents benefit from knowing about
> implementations of their proposals and developers can receive support from
> experienced working group participants and IETF document authors) while
> they are creating code based on a IETF proposals.
>
> CodeStand showcases opportunities to develop running code for IETF
> protocols that can benefit students in a class or researchers in projects,
> lowering barriers to IETF participation. When developers have questions,
> they may suggest changes to IETF documents to improve accuracy and
> interoperability for future implementations.
>
>
The text looks good to me, thanks!

>
> The CodeStand team will definitely have a chance to test drive a live
> version of the revamped website before it goes to production, but for the
> moment, it would be helpful to know from the team if there is:
>
> - a particular “call to action” (i.e. link to go somewhere else on the
> IETF website or elsewhere on the Web (perhaps visit the IETF CodeStand
> website!) to appear in the darker blue box at the bottom of the page, and
>
>
I'd say a call to action should be to populate codestand - linking drafts
to existing implementations.

>
> - a particular email list folks should sign up for (I think we discussed
> something like “codestand-announce’ or “codestand-discuss”)?
>
> Hmm, that's a good idea rather than codestand-develop.  How about
codestand-discuss?

Thanks,
Kathleen

>
> Thanks,
> -Greg
>
>
>
>
>
> _______________________________________________
> Codestand-develop mailing list
> Codestand-develop@ietf.org
> https://www.ietf.org/mailman/listinfo/codestand-develop
>
>


-- 

Best regards,
Kathleen

v2.8.7 | Report a Bug | By Email