Re: [tap] RFC Status?

Jonathan Kingston <jonathan@jooped.co.uk> Tue, 12 August 2014 20:47 UTC

Return-Path: <kingstonmailbox@gmail.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 2281B1A0110 for <tap@ietfa.amsl.com>; Tue, 12 Aug 2014 13:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.677
X-Spam-Level:
X-Spam-Status: No, score=-0.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_62=0.6, SPF_PASS=-0.001] autolearn=no
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 ai2ZdqI1ZuKD for <tap@ietfa.amsl.com>; Tue, 12 Aug 2014 13:47:47 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA411A010C for <tap@ietf.org>; Tue, 12 Aug 2014 13:47:47 -0700 (PDT)
Received: by mail-oi0-f47.google.com with SMTP id x69so6978141oia.20 for <tap@ietf.org>; Tue, 12 Aug 2014 13:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XbeQP6SOogwInM0lySYsPuKuswSP9kH/xGe2XMe5uB4=; b=m+cl4lsJ1H9jybNIhsmEfY0oEF1X4jsHNUHZHi0kyclMc2cawBdcyHebI4tALwrItZ TArTWRcW4+0q4+WZ4YAlHtsV8vVIEm+cstqIJ4vEul1IAKgTAXWkZoJcxH4JQRllBYPP n4Dw8IcLmCCOIEd2qZtJW+kWkKde74CtBr18lxtO5gjp2+UEQB3QOmZ9nodWr9JEYmIa W0bXJly6bx7OHKcMPxD7N0s4wHsfmFey0Dt+zz45MjG6L6EeGKW2hxRPe9iNz1a17mqQ Q6jU8m4p1t1sY13eMsfyb1LTq+aMcyYTqZm6pd6QY5+Ro+z8kRJBT9EHo7kwTVFnKleH fO5Q==
MIME-Version: 1.0
X-Received: by 10.60.123.19 with SMTP id lw19mr358079oeb.22.1407876467164; Tue, 12 Aug 2014 13:47:47 -0700 (PDT)
Sender: kingstonmailbox@gmail.com
Received: by 10.60.167.42 with HTTP; Tue, 12 Aug 2014 13:47:47 -0700 (PDT)
In-Reply-To: <CAP4gcswS4eOmE+eh+NAcWOdND=Dj4dz9LCOxZ6ak-+n+NCVkuw@mail.gmail.com>
References: <CAP4gcszybVr5Hw3mg=uTi8tqpA3wEVwo=zf2876RWhy_CmozZw@mail.gmail.com> <7250AD76-F5DF-494C-8A00-B4320053EBE7@ggvaidya.com> <1407788544.42539.YahooMailNeo@web163506.mail.gq1.yahoo.com> <CA+EVJMUfyvCAbU3=g2h_a238XBV23iK2kgErPOunjKUG+6T2yA@mail.gmail.com> <CAP4gcswS4eOmE+eh+NAcWOdND=Dj4dz9LCOxZ6ak-+n+NCVkuw@mail.gmail.com>
Date: Tue, 12 Aug 2014 21:47:47 +0100
X-Google-Sender-Auth: GtL-wd1yIvncZ9ykLaWRuLY1A3s
Message-ID: <CA+EVJMXk_tkP5fbrSOcAgp88LAu73EFy2K11ihsfAZe+LDC5Yg@mail.gmail.com>
From: Jonathan Kingston <jonathan@jooped.co.uk>
To: Andrew de Andrade <andrew@deandrade.com.br>
Content-Type: multipart/alternative; boundary=047d7b5d2f88b68b67050074c879
Archived-At: http://mailarchive.ietf.org/arch/msg/tap/iJ0tm7LeAvJvrKMzxNie77EdyEA
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
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: Tue, 12 Aug 2014 20:47:54 -0000

Hi Andrew,

The most conversation was there about the JSON / TAP/Y work:
https://github.com/TestAnything/testanything.github.io/pull/6

I have seen a lot of conversation on other lists but I will have to dig out
where they were, I think there was talk on http://karma-runner.github.io/
The issue as I see it is the ability for robust meta data with and agreed
set of parameters and meanings. TAP/Y(
https://github.com/rubyworks/tapout/wiki/TAP-Y-J-Specification) has gone
some way towards addressing these however not far enough in clearing up the
format.

There is smaller amounts of things that need merging in but most are
conversations, the issue realistically is that I'm not the authority so it
need people to vote and comment on them. So on the issue above I can add my
comments and merge it in but realistically it is so much of a change that I
don't think it is fair for me to just merge it in.

I am happy to be a gate keeper of the changes of the site as realistically
its not going to change at a rapid pace, however I am looking to the
community to contribute to the issues and out of that perhaps I can get
more moderators on side.

I have created a new repo(https://github.com/TestAnything/Specification)
for TAP which can be used to track changes better, conversations and also
building TAP 14 separate to the site itself which I see as a published
authority.

Thanks


On 12 August 2014 21:13, Andrew de Andrade <andrew@deandrade.com.br> wrote:

> On Tue, Aug 12, 2014 at 12:36 PM, Jonathan Kingston <jonathan@jooped.co.uk
> > wrote:
>
>> @Bruno I worked on the layout and the rest is on Github where
>> conversations can be continued for proposals as I didn't really like the
>> site being a wiki style. To gain any form of authority TAP needs to portray
>> itself much like any other body where conversations can be held elsewhere.
>>
>> My plan was to make a repo just for test proposals if you like in the
>> style of w3c proposals under the TestAnything org:
>> https://github.com/TestAnything
>>
>
> Agree. Moving everything under the TestAnything github org sounds like a
> solid approach.
>
>
>>
>> There is some bits that have been raised on Github which needs some
>> discussions as realistically people are developing alternatives to TAP
>> because of its shortcomings. However the JSON formats that have been
>> developed so far seem to have issues themselves despite being an attractive
>> concept.
>>
>
> Do you have any links to these alternatives and to discussions regarding
> what shortcomings in TAP that people are becoming frustrated with?
>
>
>> I am very much interested in it being an RFC however like the site
>> maintenance I am lacking a little in time.
>>
>
> Since the site is a github.io page, maintenance can be handled by any of
> us via a pull request. Are there any outstanding tasks that need to be
> addressed on the site?
>
>