[rfc-i] [IAB] draft-iab-html-rfc-03, "9.2 <address>"

julian.reschke at gmx.de (Julian Reschke) Wed, 06 July 2016 08:02 UTC

From: "julian.reschke at gmx.de"
Date: Wed, 06 Jul 2016 10:02:09 +0200
Subject: [rfc-i] [IAB] draft-iab-html-rfc-03, "9.2 <address>"
In-Reply-To: <3417879a-732f-24cd-c17b-533935b4d02c@rfc-editor.org>
References: <b26d0177-6041-6337-b78b-61023b4d2706@gmx.de> <9A7978E4-8FEB-4834-9A26-FC4FED311B7E@cisco.com> <19D9868D-C5AD-4F80-8F5A-074873D31397@att.com> <0c732115-c8a5-8256-86c1-2b2a3182070a@rfc-editor.org> <54379F18-B0DD-4643-91B5-610BEBB38385@cisco.com> <47E86DE8-3E4C-45D3-810E-2432CD8F963B@att.com> <3417879a-732f-24cd-c17b-533935b4d02c@rfc-editor.org>
Message-ID: <f75cbe7c-d076-313f-010c-61502440dc8b@gmx.de>

On 2016-07-06 00:13, Heather Flanagan (RFC Series Editor) wrote:
> On 7/5/16 2:38 PM, HANSEN, TONY L wrote:
>> And we can continue to use the github location of the PDF doc for its issues.
>>
>> However, I was wondering if there was should be a more centralized location. E.g., where do issues with the CSS and plaintext docs get listed?
>
> Each format-related draft has its own github repository:
>
> https://github.com/hlflanagan/draft-iab-rfc-framework
>
> https://github.com/paulehoffman/draft-iab-xml2rfc
>
> https://github.com/hildjj/draft-iab-html-rfc
> https://github.com/masinter/pdfrfc
> https://github.com/hlflanagan/draft-iab-rfc-plaintext
>
> https://github.com/hlflanagan/draft-iab-rfc-nonascii
> https://github.com/nevil-brownlee/draft-svg-rfc
> https://github.com/hlflanagan/draft-iab-rfc-css
>
> https://github.com/paulehoffman/rfcv3-preptool
>
> I'll make sure those get added to the FAQ
> <https://www.rfc-editor.org/rse/format-faq/>. For when we have code to
> create issues against, I expect that will be in github as well unless we
> have a good reason not to.
> ...

FWIW, the best place to state where issue tracking occurs is in the spec 
itself.

Best regards, Julian