Re: [tap] RFC Status?

Ovid <publiustemp-tapx@yahoo.com> Wed, 13 August 2014 05:17 UTC

Return-Path: <publiustemp-tapx@yahoo.com>
X-Original-To: tap@ietfa.amsl.com
Delivered-To: tap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 181AB1A0ADD for <tap@ietfa.amsl.com>; Tue, 12 Aug 2014 22:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.665
X-Spam-Level:
X-Spam-Status: No, score=-2.665 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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, URIBL_DBL_ABUSE_REDIR=0.001, URIBL_DBL_REDIR=0.001] autolearn=ham
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 5GGwuNLai--X for <tap@ietfa.amsl.com>; Tue, 12 Aug 2014 22:17:29 -0700 (PDT)
Received: from nm1-vm0.bullet.mail.ne1.yahoo.com (nm1-vm0.bullet.mail.ne1.yahoo.com [98.138.91.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93B8E1A09D5 for <tap@ietf.org>; Tue, 12 Aug 2014 22:17:29 -0700 (PDT)
Received: from [98.138.100.111] by nm1.bullet.mail.ne1.yahoo.com with NNFMP; 13 Aug 2014 05:17:28 -0000
Received: from [98.138.89.192] by tm100.bullet.mail.ne1.yahoo.com with NNFMP; 13 Aug 2014 05:17:28 -0000
Received: from [127.0.0.1] by omp1050.mail.ne1.yahoo.com with NNFMP; 13 Aug 2014 05:17:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 751740.95447.bm@omp1050.mail.ne1.yahoo.com
Received: (qmail 61023 invoked by uid 60001); 13 Aug 2014 05:17:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1407907048; bh=MMcoS26HKIV3IVf4dmGYRHnY3WJFF+C6Y7Egzrelyms=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=iICrT+it6Bjc20c2mMplZ5aDJUkkn30dBPg4b7Bb1/oNYNeQt45wRd1jjey28VXfkGrnTmVG8hC2JJwa5/uGNV08BA5/ItWUNrUCcSW+3d7LeQyjzhbkGh6QQD79bsopYLaK5dg23fDGo83L6PMLodUbUCnpBN+5WkNZtSRI04c=
X-YMail-OSG: Ld.Lx4MVM1lNO3gGSBPRE9_4S6LbFJxhA1Cb1P2luocRazw 3nyXGzYiLCSkMiRGvf71voULbZwaH8A_Qh2tNRjPsebbfUeLiSlhJFVqczmw yxtYPmm_gIhLyYKe6OB2Ro_Rq3AUG7x.xXtkOCwYPgnpMZkY0NBlp.2VpeNA EMSmqUsSfsxa5MM4HpubOTSpOJpmCgXgLUXa5iV4_pm9CuOtty2itGKkfzM3 GC4.U6DCmdKPxVHy5Qd5jDCp6uzGfJXvGEKrcWFKx3irPyvR9DnBwClow2nl UAaHiQ0cBpA6PEsJirFQevzkKNvJ0uiCFTO7Yjr2SeUFiPOKpoIZlEsDHJaa fmI7WhPoSFCOXRiHd7nrE_em8IBl1lBvINj1hIxGAQ7mlk_Svjg1BFm._wN0 rNHJopyUIjf363wEwLXsaNgVs4qiMTIYfJHvCnWcmoXUi3VEh68xSPs1oRvW zaXGgRGq.Qch0066Nhzn7vvqi59T6tOXz0e8DuRLWfAKM3L2uBNUK5E5Hjfg hqu7lFtcZZ6ZnlSy08wR.NVrMogmDgZdfKzIFuk43xMEYF7yv5tB56D6dYMm Xbcs47mNJZ2XKZckTJpceb9qpnuxaHpQbzFo8pVzMUCiJ.KcZVFQWmVE.cbP tjuZXDAS9pNy.9Hd6GMIinZ.aZp.YoQD3eGha1JAKYiZjiHyLhReKB2H7vjg EPP9hHEQcInH.QgOhS4GlL5f7D6tdcIrHf6vcSUZKtjHzr1NGTXp3fewGkvS gmx_c1KdZBSrjcu3g96DFAmGBS1u1Gw3X4.7W9OZZL_xlbG05nVzSyzqjihK qX6r3u_JJT0SIPPiqLMnM_XE7FwzhMeu4nggKst0TgKFLusDl5W3yHnqxyG1 WI5gSzpsswBy6bQpCJvp3yLuoUJPJOjzuBGUG01hnCIMhJJZej4lHsioVdPE 6M4qEhJ1UV7Q-
Received: from [86.206.169.249] by web126104.mail.ne1.yahoo.com via HTTP; Tue, 12 Aug 2014 22:17:28 PDT
X-Rocket-MIMEInfo: 002.001, SSBjZXJ0YWlubHkgY2FuJ3Qgdm9sdW50ZWVyIHRvIHJ1biBpdC4gTXkgdGltZSBpcyBjcmF6eSwgSSdtIHdvcmtpbmcgYSBjb3VwbGUgb2YgZGlmZmVyZW50IGNvbnRyYWN0cyByaWdodCBub3csIG9mdGVuIGhhdmUgdG8gYmUgYXQgY29uZmVyZW5jZXMgYW5kIHNvbWV0aW1lcyBnZXQgY2FsbGVkIGF3YXkgb24gc2hvcnQgbm90aWNlIHRvIHRyYXZlbCB0byBvdGhlciBjb3VudHJpZXMuIE9uIHRvcCBvZiB0aGF0LCBJJ20gYSBmYXRoZXIgYW5kIGh1c2JhbmQuIE15IHRpbWUgaXMgc29tZXdoYXQgbGltaXRlZCABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.201.700
References: <CAP4gcszybVr5Hw3mg=uTi8tqpA3wEVwo=zf2876RWhy_CmozZw@mail.gmail.com> <7250AD76-F5DF-494C-8A00-B4320053EBE7@ggvaidya.com> <1407788544.42539.YahooMailNeo@web163506.mail.gq1.yahoo.com> <CAP4gcswppT=HEy4ew-TejcvJjWT8AwXXRjnG2ECZa7tWnbT7ZQ@mail.gmail.com> <1407829749.48636.YahooMailNeo@web126105.mail.ne1.yahoo.com> <1407853316.14571.YahooMailNeo@web163504.mail.gq1.yahoo.com> <1407903000.34343.YahooMailNeo@web126105.mail.ne1.yahoo.com> <1407904315.3488.YahooMailNeo@web163504.mail.gq1.yahoo.com>
Message-ID: <1407907048.42036.YahooMailNeo@web126104.mail.ne1.yahoo.com>
Date: Tue, 12 Aug 2014 22:17:28 -0700
From: Ovid <publiustemp-tapx@yahoo.com>
To: "Bruno P. Kinoshita" <brunodepaulak@yahoo.com.br>, Andrew de Andrade <andrew@deandrade.com.br>
In-Reply-To: <1407904315.3488.YahooMailNeo@web163504.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1966909624-928731032-1407907048=:42036"
Archived-At: http://mailarchive.ietf.org/arch/msg/tap/MkWBvT3hrVrdL5N92st1aGFijBc
Cc: "tap@ietf.org" <tap@ietf.org>
Subject: Re: [tap] RFC Status?
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ovid <publiustemp-tapx@yahoo.com>
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tap/>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 05:17:32 -0000

I certainly can't volunteer to run it. My time is crazy, I'm working a couple of different contracts right now, often have to be at conferences and sometimes get called away on short notice to travel to other countries. On top of that, I'm a father and husband. My time is somewhat limited to brief bursts of energy in my "spare" time :)
 
And you now have 3 readers for your subreddit, but I'm subscribed to enough subreddit's that I may very well miss changes there!

Best,
Ovid
--
IT consulting, training, international recruiting
       http://www.allaroundtheworld.fr/.
Buy my book! - http://bit.ly/beginning_perl
Live and work overseas - http://www.overseas-exile.com/


On Wednesday, 13 August 2014, 6:32, Bruno P. Kinoshita <brunodepaulak@yahoo.com.br> wrote:
 

>
>
>Hello,
>
>
>> The immediate need is for someone to take ownership of the IETF process and publicly say "I'll see this through." There was a lot of great work done in the past, but we're obviously not there yet.
>
>
>Great idea, let's see if someone will step forward to volunteer (maybe you? :-). I'm relocating to another continent in less than 1 year, but if no one else volunteers I can work on this till June next year. 
>
>
>> With that, we can start scratching items off out TODO list one-by-one. I would humbly suggest that we not go with monthly meetings as they're so hard to organize. Instead, keep the list open, have the TODO list on a github wiki and let's see what we can make happen.
>
>
>Sounds good to me. Let's use https://github.com/TestAnything/Specification ? 
>
>
>Even though I do like keeping decisions and discussions in the mailing list (like the Apache way), I feel sometimes it helps to have something like an IRC channel, for real time chat, validate some ideas before sending to the mailing list or brainstorm with somebody else. What do you think? I started collecting TAP-related links in a subreddit too, but is has very low activity and got only 2 readers http://www.reddit.com/r/testanythingprotocol
>
>
>Thanks Ovid!
>Bruno
>
>
>
>>________________________________
>> From: Ovid <curtis_ovid_poe@yahoo.com>
>>To: Bruno P. Kinoshita <brunodepaulak@yahoo.com.br>br>; Andrew de Andrade <andrew@deandrade.com.br> 
>>Cc: "tap@ietf.org" <tap@ietf.org> 
>>Sent: Wednesday, August 13, 2014 1:10 AM
>>Subject: Re: [tap] RFC Status?
>> 
>>
>>
>>What do you think that would be the next steps to push forward a TAP 14 draft, and make some progress on the RFC? Maybe something like monthly meetings in IRC or some other IM, and some discussion panels in hackathons/meetups? 
>>The immediate need is for someone to take ownership of the IETF process and publicly say "I'll see this through." There was a lot of great work done in the past, but we're obviously not there yet.
>>
>>
>>Next, the goal needs to be clearly defined. I would also suggest we define why we want the goal accomplished. Once done:
>>	1. What we've successfully done.
>>
>>	2. What we still need to do.
>>
>>	3. What might need to change (danger, Will Robinson!)
>>
>>Those three items can give us a TODO list. Item #1 might seem superfluous, but when tackling a large project, I like to remind people of all of the groundwork already laid to keep things in perspective. Plus, a sense of historical context might help those who are unfamiliar with the history.
>>
>>
>>With that, we can start scratching items off out TODO list one-by-one. I would humbly suggest that we not go with monthly meetings as they're so hard to organize. Instead, keep the list open, have the TODO list on a github wiki and let's see what we can make happen.
>>
>>
>>Best,
>>Ovid
>>--
>>IT consulting, training, international recruiting
>>     
  http://www.allaroundtheworld.fr/.
>>Buy my book! - http://bit.ly/beginning_perl
>>Live and work overseas -
 http://www.overseas-exile.com/
>>
>>
>
>_______________________________________________
>tap mailing list
>tap@ietf.org
>https://www.ietf.org/mailman/listinfo/tap
>
>
>