Re: IETF - Let's Get Started

the charter format from RFC 2418 to make a skeleton charter at testanything.org: http://testanything.org/wiki/index.php/IETF_WG_Proposed_Charter Two small and one big question: 1. Who is/are going to be the chair(s)? 2. Which area of IETF are we under? You can see the list of areas at http://ww

IETF - Let's Get Started

I'm a bit disappointed that after all of our effort to get the TAP IETF process started, we have let it languish. I'd like to restart this effort. We understand what a lot of basic issues are, so let's get some traction on this. Background links: Initial proposal disc

Re: IETF list? (was Re: JSON TAP Diagnostics?)

On 21 Aug 2008, at 23:37, Michael G Schwern wrote: What IETF list? https://www.ietf.org/mailman/listinfo/tap -- Andy Armstrong, Hexten

IETF list? (was Re: JSON TAP Diagnostics?)

Ovid wrote: > Folks, this really, really needs to go to the IETF list. What IETF list? -- Ahh email, my old friend. Do you know that revenge is a dish that is best served cold? And it is very cold on the Internet!

Re: File/Line # (Was: IETF)

* David E. Wheeler <[EMAIL PROTECTED]> [2008-08-18 19:25]: > I don't believe it's possible to get that info in JS, is it? Just seen: http://eriwen.com/javascript/js-stack-trace/ Regards, -- Aristotle Pagaltzis //

Re: File/Line # (Was: IETF)

On Aug 18, 2008, at 15:08, Ovid wrote: --- On Mon, 18/8/08, David E. Wheeler <[EMAIL PROTECTED]> wrote: But I don't have file or line numbers in Test.Builder (JavaScript). I don't believe it's possible to get that info in JS, is it? This is precicely part of the reason we want "non-Perl" i

Re: File/Line # (Was: IETF)

--- On Mon, 18/8/08, David E. Wheeler <[EMAIL PROTECTED]> wrote: > But I don't have file or line numbers in Test.Builder > (JavaScript). I > don't believe it's possible to get that info in JS, > is it? This is precicely part of the reason we want "non-Perl" implementations represented. The co

File/Line # (Was: IETF)

On Aug 18, 2008, at 02:53, Ovid wrote: Also, pulling in people developing TAP for things other than Perl would be good (such as David Wheeler's PostgreSQL work. That came up a few times as uri/line# diagnostic information isn't quite as applicable there). Well, it would be handy if I cou

Re: IETF

you. What Salve brought up is not that the *working group* needs to attend IETF meetings thrice yearly, but *the chairman* of the WG does. We’re talking about one person, the chair, not about the entire working group. As I see it, The purpose of the IETF meetings are to give WG members well-pla

Re: IETF

--- On Mon, 18/8/08, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote: > I think your initial mail was misleading and Schwern > promptly > misunderstood you. What Salve brought up is not that the > *working group* needs to attend IETF meetings thrice yearly, but > *the chairman

Re: IETF

ght up is not that the *working group* needs to attend IETF meetings thrice yearly, but *the chairman* of the WG does. We’re talking about one person, the chair, not about the entire working group. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>

Re: IETF

(Now copying to appropriate lists, hence the response not being trimmed) --- On Mon, 18/8/08, Michael G Schwern <[EMAIL PROTECTED]> wrote: > Ovid wrote: > > One issue Salve raised is that the IETF apparently > requires *physical* meetings three times > > a year. Shor

Re: IETF

Ovid wrote: > One issue Salve raised is that the IETF apparently requires *physical* > meetings three times > a year. Short of people individually ponying up the money, this suggests some form of > sponsorship. Anyone have any thoughts on this? I roll to disbelieve. It seems not l

IETF

Hi all, At YAPC::EU, Salve, Aristotle, Andy (Armstrong) and myself hammered out a rough draft of some of the issues we'll need to cover with an IETF proposal. I'll try to post those when I can, but right now I'm at work and my laptop is not. One issue Salve raised is that the