IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Making SOWs accessible to a broader pool

Alissa Cooper <alissa@cooperw.in> Thu, 27 June 2019 15:47 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81DA31200F8 for <tools-development@ietfa.amsl.com>; Thu, 27 Jun 2019 08:47:29 -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, 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=cooperw.in header.b=n1/yMnUr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=o2EbidA4
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 GZwq5rhtefsq for <tools-development@ietfa.amsl.com>; Thu, 27 Jun 2019 08:47:27 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9BF1120125 for <tools-development@ietf.org>; Thu, 27 Jun 2019 08:47:26 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id EC382326; Thu, 27 Jun 2019 11:47:25 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 27 Jun 2019 11:47:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=w 513Mtth9JFLZM4TMHtMXJAc37+ayCfagOq4/ItWfSc=; b=n1/yMnUrIza7EoTgS zGued+Y3r6vkvfkgNhs0g/SGVe3scqPIqJ744emu3jv3cP8uXqCxviRy/k2GOI2p J3aX2RX351QoXnxA2dGbVpNNWxr5yOP8X9G/lGTeRBQfr49xrAOPsW6lREL4ilH7 ubki7lMemVCS9WOkiiG1nkXyG5UsdEhq/Q7pKSRgy2fnkE3PsB5eBRp7o6vzWym4 I4fobzwmt7iz3VJquCwV7D3UmdlLqE/Tc8yCUExJuFaZh78B5rhVGnzaIgowtCqX cNbv1lLo0TeAAulsvQp+nZeXQQCVMHY8qxDhFvvryuoaJiv3BeQB118Zz/cCgdyd yLUPQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=w513Mtth9JFLZM4TMHtMXJAc37+ayCfagOq4/ItWf Sc=; b=o2EbidA4us/mv1eAWRBZC9Gu4sLL05IB91F/YoEObzm8v/kUYyxWh+hMn 5fEBYLYZkOEDXbPglSm+u8lM03RBfeyImoRKQtLHDBT0PDIBt701XQbyFZqesLb8 IfXKaWkzWoEen3hYSBEzCWJ17aCiYhI4Vi72/f9F4y+yAO2VD9uVxa6t4yDxxx62 PG/40svOO7JgdqWPuR4A7/67Leqpgjb1lsn6DgIa+tBHiEZBUnNmyqhf6BZvR/Ww LNDJeTLFUDLUcibgKeGAkR+HU7wbfKA8g2zK1e+rSZeGIw960a8fe6pzVMozbFIU iMs4xH/zjuzonD4hQUYKpzeRodFOA==
X-ME-Sender: <xms:DeUUXTT9Xr1FsZmMDqOMMOYfU8jmgANZSY8Z2P5JOBW1vKuuo0m2vw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudekgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdelvdenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:DeUUXfulDgxSP05QAUcMjnaxLVoUKConGjcYSh_GePMQFoECgmfRIw> <xmx:DeUUXX2kyAaDOcWw4V6yDjfxWgjlPIxZrA0atLvPTG6ty3n0WOqC8A> <xmx:DeUUXYVbQC9m1avn17_aUC5YqU-Wg2gyzNxuUNdZv569_00quDBKJQ> <xmx:DeUUXXVJjHWRk9cCZlcxvq9bw9JySsRE4XgZSiMaAPC_4lHgmY9ZoQ>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.92]) by mail.messagingengine.com (Postfix) with ESMTPA id 1BEC38005A; Thu, 27 Jun 2019 11:47:25 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <89FBA6E1-4CFD-4AB1-ADF2-A91F72564902@vigilsec.com>
Date: Thu, 27 Jun 2019 11:47:23 -0400
Cc: IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABB0DC34-92B0-4814-BE31-F95A71D111E9@cooperw.in>
References: <8EEB78FC-4F6A-40F5-8486-03B3F664BED3@cooperw.in> <89FBA6E1-4CFD-4AB1-ADF2-A91F72564902@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/vQ3zzGkTq2lOjNUuEKZyneXoOp4>
Subject: Re: [TOOLS-DEVELOPMENT] Making SOWs accessible to a broader pool
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 15:47:29 -0000


> On Jun 26, 2019, at 4:31 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> I agree that we want to make these "bidable" by the largest possible audience.  That said, some of them are easier to do without IETF jargon than others.  

To be clear, I think it’s fine to use jargon as long as it is explained upon first use. I doubt these would make any sense if we tried to avoid jargon altogether. ;-)

Alissa

> In all cases we have been including pointers to the code itself, which reall does help a potential bider understand the size of the application and where the enhancement fits.
> 
> Russ
> 
> 
>> On Jun 26, 2019, at 4:23 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>> 
>> I’m wondering if there are some steps we could take to write our SOWs in such a way as to make them accessible and understandable to a broader pool of potential bidders. I’ve noticed that recent ones tend to use a lot of IETF-specific jargon and acronyms without explanation and assume significant familiarity with the existing infrastructure and code base. Might it be possible to develop some boilerplate text that could be re-used across datatracker-focused RFPs that provides an introduction to the IETF, an introduction to the project, a description of the technologies in use, and links to the source code and other relevant information? 
>> 
>> Thanks,
>> Alissa  
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>

v2.23.0 | Report a Bug | By Email