W3C home > Mailing lists > Public > www-archive@w3.org > April 2015

Re: Moving File API to Github

From: Arun Ranganathan <aranganathan@mozilla.com>
Date: Wed, 15 Apr 2015 09:28:50 +0700
Message-ID: <CAMFUyDGo5EF5xKfS+AdLX083HDn79Yta5DtKKmQjJahSYg1SQg@mail.gmail.com>
To: Arthur Barstow <art.barstow@gmail.com>
Cc: Arun Ranganathan <arun@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, "www-archive@w3.org" <www-archive@w3.org>
Art, Xiaoqian,

Thank you for helping with this.

The file Overview.html can be edited directly, and there's no reason to use
a Makefile as far as I can tell.

I agree with setting up a TR.html boilerplate. I think the best way to do
it is to place the "TR" CSS directly in the Overview.html template but
rename it TR.html.

-- A*

On Tue, Apr 14, 2015 at 3:46 AM, Arthur Barstow <art.barstow@gmail.com>
wrote:

> On 4/7/15 8:21 PM, Arthur Barstow wrote:
>
>> We've started moving WebApps' specs to Github and I'd like to get File
>> API moved as well as to publish a new Working Draft.
>>
>> Any objections from you if I go ahead with the GH import to <
>> https://github.com/w3c/FileAPI/>? If importing a CVS repo is as simple
>> as a Hg->Github import, it should be relatively straight forward.
>>
>
> Thanks to the good work of Xiaoqian, this is now complete <
> https://github.com/w3c/FileAPI>.
>
>  (BTW, does this spec still use xsltproc or is that now `cruft`?)
>>
>
> The spec needs a new WD publication, in particular to update the
> boilerplate data (f.ex. use the new ED URL <https://w3c.github.io/
> FileAPI/Overview.html>).
>
> If you can't do that this week, I'll take the first stab by running
> Makefile and then making the output "Pub Ready" (creating a new file
> "TR.html"). I will only update the boilerplate of TR.html (and fix any
> blocking bug the validators require). I don't plan to touch the .xml file.
> Please let me now.
>
> -Thanks, Art
>
>
Received on Wednesday, 15 April 2015 02:29:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 15 April 2015 02:29:20 UTC