W3C home > Mailing lists > Public > public-webplatform@w3.org > October 2013

RE: Notes from today's infrastructure meeting

From: Eliot Graff <Eliot.Graff@microsoft.com>
Date: Fri, 4 Oct 2013 15:30:36 +0000
To: Julee <julee@adobe.com>, WebPlatform Public List <public-webplatform@w3.org>
Message-ID: <0158f88c22814ca6a04f9d20f7ee8f70@BL2PR03MB228.namprd03.prod.outlook.com>
Hi Julee.

Sorry I didn't get back to you sooner on this.

I think that not showing the links to the IE sample server is a good idea. Not that I don't want the traffic, but we want the content to be agnostic. I would comment them out, though, rather than deleting them. If anyone wanted to use the sample or modify it, they would likely want to see the version on the server, as the code shown in the example is often just the meat of the thing, and the code on the server shows the whole example in context.

And for the love of all things better than HTML4.01, the CAPPED ELEMENTS should be updated to meet modern practices. We're currently going through that effort for the source that this content came from on MSDN, and that should definitely be done everywhere we encounter the old practices in the content we donated to WPD.

Eliot

From: Julee [mailto:julee@adobe.com]
Sent: Monday, September 30, 2013 2:29 PM
To: Eliot Graff; WebPlatform Public List
Subject: Re: Notes from today's infrastructure meeting

Sounds good. I'm sure Renoir & Doug will be putting some technical proposal out for this, but some other things to think about as we move forward with this:

For CSS properties:

* For remaining properties should script delete the example? Leave the example, but delete the link? Or move the example to code.webplatform.org?
* And if we move it, can we change the elements to lowercase?

For areas we haven't manually vetted:

Should we wait until there's an editing pass and just deal with the ones left? Or would you prefer some script solution to get rid of the reference to msdn as quickly as possible?

Julee
----------------------------
julee@adobe.com<mailto:julee@adobe.com>
@adobejulee

From: Eliot Graff <Eliot.Graff@microsoft.com<mailto:Eliot.Graff@microsoft.com>>
Date: Monday, September 30, 2013 2:20 PM
To: julee <julee@adobe.com<mailto:julee@adobe.com>>, WebPlatform Public List <public-webplatform@w3.org<mailto:public-webplatform@w3.org>>
Subject: RE: Notes from today's infrastructure meeting

Thank you, Julee.

For this item:

Script for deleting or converting code examples at samples.msdn.microsoft.com to code.webplatform.org

Although we should be mostly done with CSS, there are still many of these left in HTML and other areas. Any progress Renoir can make in automating the identification of samples still pointing to MSDN is greatly appreciated.

Eliot Graff

From: Julee [mailto:julee@adobe.com]
Sent: Monday, September 30, 2013 2:09 PM
To: WebPlatform Public List
Subject: Notes from today's infrastructure meeting

Hi folks:

In today's meeting, we focused on the infrastructure items that the CSS properties project is dependent on: compatibility tables, compatibility info graphics, flags UI, stability, script for msdn code examples

---------------------------

Compatibility tables - Doug & Renoir will isolate tasks that need to be done, so we can publicize and seek volunteers with appropriate skills

---------------------------

Compatibility infographics - Although there is always room for improvement, we consider this DONE for CSS props launch.

---------------------------

Stability - is good now, we now can see global health, ID glitches & fix them quickly. We consider this DONE for CSS props launch. (Switching to the new service provider cannot disrupt traffic.)

---------------------------

Script for deleting or converting code examples at samples.msdn.microsoft.com to code.webplatform.org - We don't expect a lot of these to be left, as they should have been updated/deleted/converted during the editing process. But Renoir will investigate how to ID any remaining examples and how to handle them.

e.g.: http://docs.webplatform.org/wiki/css/properties/-ms-scrollbar-highlight-color points to http://samples.msdn.microsoft.com/workshop/samples/author/dhtml/refs/scrollbarColor.htm

---------------------------

Flags UI - The flags UI (as it stands now or in the latest comps) is NOT sufficient for notifying a visitor that the page is not ready for consumption. So, we have modified proposal: one pictograph w/ explanation, flags displayed only in editing form, www landing page should also explain pictograph.

Doug & Renoir will isolate tasks that need to be done, so we can publicize and seek volunteers with appropriate skills.

I will send out a separate email (subject: What do you think about changing the UI for unfinished pages? (no flags, one big warning sign instead)), outlining the proposal. Will you please reply to that with any comments you may have?

---------------------------

Other things discussed: CSS properties project: Julee & Scott to take over verifying pages from Doug. This way, we can get to a list of what still needs to be done.

---------------------------

That's all for now!

Julee
----------------------------
julee@adobe.com<mailto:julee@adobe.com>
@adobejulee
Received on Friday, 4 October 2013 15:31:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:13:54 UTC