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

[tony at att.com (HANSEN, TONY L)]

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?

On 7/5/16, 5:33 PM, "Joe Hildebrand (jhildebr)" <jhildebr at cisco.com> wrote:

I'm ok with using https://github.com/hildjj/draft-iab-html-rfc/issues, if that works for you, Heather.


> On Jul 5, 2016, at 2:27 PM, Heather Flanagan (RFC Series Editor) <rse at rfc-editor.org> wrote:
> 
> On 7/5/16 1:14 PM, HANSEN, TONY L wrote:
>> On 7/5/16, 4:00 PM, "rfc-interest on behalf of Joe Hildebrand (jhildebr)" <rfc-interest-bounces at rfc-editor.org on behalf of jhildebr at cisco.com> wrote:
>> 
>>> On Jul 1, 2016, at 4:32 AM, Julian Reschke <julian.reschke at gmx.de> wrote:
>>>> ?
>>> I'm fine with that.  Hold for document update; this shouldn't delay getting started on tooling, and has a minimal impact if we change it.
>> Do we have a place, other than the author?s notes, where such items will be collected?
>> 
>> 	Tony
>> 
> 
> I've been discussing setting up a tracker for this; right now, the items
> are in email messages. Julian has been using the xml2rfc issue tracker,
> which makes sense for some things given we don't have a better place
> yet, but I don't think that's the right longer-term location for issues
> and suggestions for the new format material.
> 
> -Heather
> 

-- 
Joe Hildebrand