IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] Draft of an SoW for the 2019 yangcatalog projects

Robert Sparks <rjsparks@nostrum.com> Fri, 18 January 2019 22:38 UTC

Return-Path: <rjsparks@nostrum.com>
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 01A241312C1 for <tools-development@ietfa.amsl.com>; Fri, 18 Jan 2019 14:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 ZOCau01pkJMw for <tools-development@ietfa.amsl.com>; Fri, 18 Jan 2019 14:38:44 -0800 (PST)
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 78254131440 for <tools-development@ietf.org>; Fri, 18 Jan 2019 14:38:44 -0800 (PST)
Received: from unescapeable.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x0IMcg8P095422 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 18 Jan 2019 16:38:43 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1547851124; bh=4Hf0XhHV8efWthLmV71xxOrjdOo9AB3OzPAQUBez/2A=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=pzHhYEWz49/TfrVSl1gaAXFln34JCReUufIYrhbUsRE3kJP2pRPXVqggQZ+X0DEIW v4Z41Tf2qAobs36VuWHBioNrBDlIRQujVAKukIhv/bXPv031+0po8jTmoGqt4MqH6I CmqVY2FAWHF9YtnjKWf0xfsrzZDs12xt+B9eYQjA=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unescapeable.local
To: Russ Housley <housley@vigilsec.com>
Cc: IETF Tools Development <tools-development@ietf.org>
References: <86d5b213-3c0b-308d-b9a7-0460c52996dd@nostrum.com> <05AFE215-11BE-45B2-AEBB-965945CE83D1@vigilsec.com> <1fc7b761-c4ab-3022-16d5-abe659b1008f@nostrum.com> <98316941-FBA8-487F-AE02-BFBA660AF1CB@vigilsec.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <a1682c62-ee32-4b8f-2273-e6ead8ac1e52@nostrum.com>
Date: Fri, 18 Jan 2019 16:38:42 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <98316941-FBA8-487F-AE02-BFBA660AF1CB@vigilsec.com>
Content-Type: multipart/alternative; boundary="------------BC4DDC91F32598C3490B2747"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/A8uw16x69isWaZlyjPY-JcUem0E>
Subject: Re: [TOOLS-DEVELOPMENT] Draft of an SoW for the 2019 yangcatalog projects
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: Fri, 18 Jan 2019 22:38:46 -0000

On 1/18/19 4:29 PM, Russ Housley wrote:
>
>
>> On Jan 18, 2019, at 5:08 PM, Robert Sparks <rjsparks@nostrum.com 
>> <mailto:rjsparks@nostrum.com>> wrote:
>>
>>
>> On 1/18/19 4:01 PM, Russ Housley wrote:
>>> Robert:
>>>
>>> I suggest that we structure it as three tasks in one SOW, and the 
>>> bidder may bid on one, two, or all three.
>> That was what I tried to write in the first place.
>>>  Further, the hourly rate for a person dong the first task may be 
>>> different from the rate of the person doing the second task.
>> Right - that's why it's a different bid.
>>>
>>> See attachment.
>> The only change I see in the attachment that concerns me is you 
>> removed the request to bid the cost of attending the hackathon at 
>> IETF104 and replaced it with a statement that covering the hours 
>> would be guaranteed. What about travel expenses?
>
> I do not see anything in the original wording that says anything about 
> travel.
It wasn't explicit enough at "a bid for attending the IETF-104 Hackathon".
>  I am assuming we should cover travel too.  I suggest:
>
> This task requires a bid for hourly work as requested by the
>
> IETF Tools Team, as well as hours and actual travel expenses
>
> to attend the IETF-104 Hackathon. Hours and travel expenses
>
>  to attend the IETF-104 Hackathon are guaranteed to the winner.
>
>  Additional hours depend on the work that is needed over the
>
>  period of the contract.
>
That works for me.
>
> Russ
>
>

v2.23.0 | Report a Bug | By Email