Re: [tap] RFC Status?

For those that have been around the longest, can someone share some links
that describe what exactly is going to be required in terms of know-how and
time to take ownership of a process like this. Of course, I've found some
general guides on the IETF process (links below), but if there is anything
specific to what's been done with TAP in general, that would be useful. In
the past, who had taken ownership of the process, so we can at least go
back in the archives and see how the previous person handled ownership of
this process with respect to TAP.

I'm about the change jobs in ~1 month to work entirely on engineering tool
for front-end teams at Uber, so I can't promise anything yet, but if the
commitment involved is reasonable and it's ends up aligned with my
responsibilities at my new job, I just might be able to take ownership
here. No guarantees just yet.

This is what I found and will go through to better understand the IETF
process.

https://www.ietf.org/about/standards-process.html
http://www.ietf.org/about/process-docs.html
https://www.ietf.org/rfc/rfc2026.txt
http://en.wikipedia.org/wiki/Request_for_Comments
http://www.rfc-editor.org/rfc/rfc6410.txt
http://tools.ietf.org/html/rfc2028

On Tue, Aug 12, 2014 at 10:17 PM, Ovid <publiustemp-tapx@yahoo.com> wrote:

> 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>; 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
>
>
>

-- 
Q: Why is this email four sentences or less?
A: http://four.sentenc.es