Re: [Codematch-develop] Site name - codematch

kathleen.moriarty.ietf@gmail.com Wed, 20 July 2016 15:14 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: codematch-develop@ietfa.amsl.com
Delivered-To: codematch-develop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 265B812D872 for <codematch-develop@ietfa.amsl.com>; Wed, 20 Jul 2016 08:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 3TH3NOTCNgWh for <codematch-develop@ietfa.amsl.com>; Wed, 20 Jul 2016 08:14:47 -0700 (PDT)
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 48A1012D910 for <codematch-develop@ietf.org>; Wed, 20 Jul 2016 08:14:39 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id s63so47966685qkb.2 for <codematch-develop@ietf.org>; Wed, 20 Jul 2016 08:14:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t7TAsKEn2AMWm4FTmkGENK7b5kreolndmb9TOzbbdEw=; b=pZnNCZSbJRNm4LjSS3xrO1hVdJi91QtxyiM8OqCe2t0EYbQX+9efsydPr52TuQA4al YbfSJsBz7F4ei168Lf26zrr5Lx95Mq0eboLLRzGQqvQnwu215VOlmMvD3HAVf+uP2ROH E0AvJ9EDeUuHKR9UYHG/0W6ZiTdNvUpQ8H3qC2DfOMS9hAHR14MOaZGTDsT6pXGYTnoE F3YxCQjjNaUvfanu6nsaQAvDuV3QHer+Yp7z8aDnraEzaOXiTBtKLK9t1/KRg1wnLUcj xVsIj2ftODBmSp3krMlKbqMh4dQQ5t0EqglxLSeM8Yu+Sl8YH/pOEeosgKdw7VLglVJH E3jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t7TAsKEn2AMWm4FTmkGENK7b5kreolndmb9TOzbbdEw=; b=j43TN/LHLG1VGn8Mt4aeY7O9geDds15mfor7c5TLOru3UhH/IMALKYlmaZg4soLPir 9PkaY3APaNwEUULFwcnSeC2/8cemgwcM+QL1ewYAe4cM8ka+Qh8V/tXbhxKHhXXsZhOk 457nI3bqZ33huxIYrJGNLSDOrdFBH4MGCUgOktelgMz1Ibz72l1ilmGsJusaV7zCnatx JIosmCsfgzwxF598L8mS1RWfc20LDd83Bbh/xhpPuI6LIm5ocGdIAwXmsOD6nlT51KYv 6Z2+WqDLV0Oqkxs2UzVFwW/XFpbman9yAuh7VGjW91fzDnlJk5BF4V1WI0dq/5g5uyXx w8jA==
X-Gm-Message-State: ALyK8tJybDKOrLnsz2sqxMEcQ2laUHpDw1PoEu9p4VFf5qnqpI/0nP5KgtyV9DCld01qyQ==
X-Received: by 10.55.24.215 with SMTP id 84mr62831521qky.51.1469027678200; Wed, 20 Jul 2016 08:14:38 -0700 (PDT)
Received: from [31.133.143.214] (dhcp-8fd6.meeting.ietf.org. [31.133.143.214]) by smtp.gmail.com with ESMTPSA id i13sm1643639qte.42.2016.07.20.08.14.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 20 Jul 2016 08:14:37 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <bc0bdca7-128c-f4c5-26cc-2de60fc09ea3@gmail.com>
Date: Wed, 20 Jul 2016 17:14:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <88B39AB9-9794-4497-999D-E68E15A0AE4A@gmail.com>
References: <CAHbuEH6idTjeViwqj37GVW+omR0DUrifqt6jfNM5LStzXPRATA@mail.gmail.com> <3FFBDA46-0B36-451C-A3CE-5024A82191AF@isoc.org> <bc0bdca7-128c-f4c5-26cc-2de60fc09ea3@gmail.com>
To: carlos@lacnic.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/codematch-develop/zsuEELINp-vP1WMulwdeY8Pzcko>
Cc: "codematch-develop@ietf.org" <codematch-develop@ietf.org>, Christian O'Flaherty <oflaherty@isoc.org>
Subject: Re: [Codematch-develop] Site name - codematch
X-BeenThere: codematch-develop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "\"Discussion forum for the planning, coordination, and development of CodeMatch\"" <codematch-develop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codematch-develop>, <mailto:codematch-develop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codematch-develop/>
List-Post: <mailto:codematch-develop@ietf.org>
List-Help: <mailto:codematch-develop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codematch-develop>, <mailto:codematch-develop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2016 15:14:51 -0000

RunningCode shows up as an application by a company in the Ukraine.  It also shows up vey prominently as an IETF term.  I'm not sure if we can use it or if we would have to call it RunningIETFCode of some variant that  breaks up the name.  I like it too...

Kathleen 

Sent from my iPhone

> On Jul 20, 2016, at 5:02 PM, Carlos M. Martinez <carlosm3011@gmail.com> wrote:
> 
> Actually Alvaro Retana came up with the idea. I just said I liked it a
> lot :-D
> 
> Any name you choose, let me know so I can create the proper DNS records.
> 
>> On 7/20/16 4:58 PM, Christian O'Flaherty wrote:
>> 
>> Carlos suggested “RunningCode” as a name and I like it. 
>> 
>> Christian O'Flaherty  oflaherty@isoc.org
>> Regional Development - Internet Society 
>> Skype/Gmail/Yahoo!:  christian.oflaherty 
>> Mobile/WhatsApp: +598 98769636
>> 
>>> On Jul 20, 2016, at 12:11 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
>>> 
>>> Hello,
>>> 
>>> We need to come up with a new name.  At the time we decided to use
>>> CodeMatch as the name, search results didn't show any use of the term.
>>> As it turns out, someone beat us to it and ironically it is a program
>>> that is used to detect copyright infringement.
>>> 
>>> This is unfortunate, but maybe we can come up with something better.
>>> Ideas are welcome.
>>> 
>>> Object of our application:  Connect/match code to standards
>>> 
>>> The code may be open source or proprietary and the standards can be
>>> published or drafts.  A mentoring connection is possible, not not
>>> required.
>>> 
>>> Proposals (more welcome and encouraged):
>>> 
>>> CodeStandards
>>> StandardsCode
>>> Connect Standards and Code (CSAC)
>>> Connect Code and Standards (CCAS)
>>> Match Standards and Code (MSAC)
>>> Match Code and Standards (MCAS)
>>> 
>>> Anything others?  Any preferences?
>>> 
>>> This may mean that we have to rename some other terms or at least review them.
>>> 
>>> 
>>> -- 
>>> 
>>> Best regards,
>>> Kathleen
>>> 
>>> _______________________________________________
>>> Codematch-develop mailing list
>>> Codematch-develop@ietf.org
>>> https://www.ietf.org/mailman/listinfo/codematch-develop
>> 
>> _______________________________________________
>> Codematch-develop mailing list
>> Codematch-develop@ietf.org
>> https://www.ietf.org/mailman/listinfo/codematch-develop
>>