W3C home > Mailing lists > Public > public-webplatform@w3.org > January 2014

Re: Attribution to MSDN on JavaScript pages

From: Max Polk <maxpolk@gmail.com>
Date: Wed, 29 Jan 2014 21:58:25 -0500
Message-ID: <52E9BFD1.2030100@gmail.com>
To: Julee Burdekin <jburdeki@adobe.com>, PhistucK <phistuck@gmail.com>, Doug Schepers <schepers@w3.org>
CC: Eliot Graff <Eliot.Graff@microsoft.com>, Eliezer Bernart <eliezer.bernart@gmail.com>, Renoir Boulanger <renoir@w3.org>, WebPlatform Public List <public-webplatform@w3.org>
On 1/28/2014 1:48 PM, Julee Burdekin wrote:
> I spoke with Eliezer, who said he can try and do this post import. The 
> only outstanding issues for the final import are now:
>
>  1. Move return values into their own section — if Max can. If not,
>     Eliezer can create the section and we can move it manually.
>  2. Move the content currently in the javascript namespace into the
>     Meta:* namespace.
>
> Max & Eliezer: would you kindly let us know if this isn’t the case?

Those are the only outstanding issues.  Someone should move the content 
currently under /javascript manually because there are only 17 pages, 
and some of them you probably do *not* want to move:

     javascript
     javascript/data types
     javascript/es
     javascript/feature detection
     javascript/functions
     javascript/functions/parseFloat
     javascript/functions/parseInt
     javascript/libraries
     javascript/methods/getDate
     javascript/objects
     javascript/objects/Array
     javascript/objects/Date
     javascript/operators
     javascript/pt-br
     javascript/statements
     javascript/syntax
     javascript/tutorials

The "landing" page in the test wiki was not imported.  I typed that in:
     http://docs.webplatform.org/test/javascript

It links to the original landing page:
     http://docs.webplatform.org/test/javascript/javascript_reference

We already have a good JavaScript landing page:
     http://docs.webplatform.org/wiki/javascript

So we likely will need to have someone, after the import, hook that 
landing page in to the new content, possibly keeping things like 
libraries and tutorial, possibly fixing the links to functions and 
objects, possibly adding new links, possibly incorporating parts of the 
original imported landing page, or other things to make it ready, 
deciding what pages to leave alone, what to move away, and so forth.
Received on Thursday, 30 January 2014 02:58:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:57 UTC