Re: [tap] RFC Status?

["Bruno P. Kinoshita" <[e-mail]>]

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 <[e-mail]>
>To: Bruno P. Kinoshita <[e-mail]>; Andrew de Andrade <[e-mail]> 
>Cc: "[e-mail]" <[e-mail]> 
>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/
>
>