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

Re: Notes on our chat today

From: Julee Burdekin <jburdeki@adobe.com>
Date: Mon, 4 Mar 2013 17:57:56 -0800
To: Jonathan Garbee <jonathan@garbee.me>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-ID: <CD5A90E5.5BC7D%jburdeki@adobe.com>
All sounds good, Garbee. Yes, the Analytics Task Force should probably have it's own project, as should the Communications & Outreach Task Force. Do you need to set these up? I was planning to do the Analytics one myself.


From: Jonathan Garbee <jonathan@garbee.me<mailto:jonathan@garbee.me>>
Date: Monday, March 4, 2013 5:55 PM
To: "public-webplatform@w3.org<mailto:public-webplatform@w3.org>" <public-webplatform@w3.org<mailto:public-webplatform@w3.org>>
Subject: Re: Notes on our chat today
Resent-From: <public-webplatform@w3.org<mailto:public-webplatform@w3.org>>
Resent-Date: Monday, March 4, 2013 5:55 PM

I will work on getting a Beta milestone setup in the Content section tomorrow. It will be pretty painless to do. As far as setting milestones up in other sections I would feel better waiting until the rest of the bugs are pulled in for the sake of keeping the configuration as clean as possible until heavy usage (and documentation) starts. That way tracking down any issues that may (probably will) crop up will be easier to track down.

As far as this Analytics Task Force it sounds like we should have a project created specifically for it, plus a team as well for the members to join. So should we consider this a test-bed for the team system? Either way I can have this created tomorrow afternoon for issues to start being filed in it. We can work out the team situation later on.

On Mon, Mar 4, 2013 at 7:50 PM, Julee <julee@adobe.com<mailto:julee@adobe.com>> wrote:
Hi, Doug and everyone:

Here are some notes from a chat Doug and I had today.


We want to ensure we're succeeding at promoting content. We also want to make sure we're giving everyone a sense of the activity on the site.

For instance, we tried out a process for making sure new content gets promoted with pointers. Eliot commented last week that it "seemed" effective. We need to have some analytics to make sure we're effective.

We have Julee, Patrick D'Souza, Scott Rowe, and Doug on the Analytics Task Force. This is a good number to start with. Let's focus the Analytics team on the following tasks:

1. Set up the project page.
2. Begin with a basic audit and clean up, including generating a site map.
3. Define basic analytics infrastructure.
4. Create a framework for reporting to the larger community, with regular blog posts about things like traffic and new content written.

Doug will add Julee to piwik.

===Milestone tracking===

Garbee has done a lot of work to get the project/issue tracking up and working. Next we want to define milestones, especially milestones to Beta, and get them as projects into bug genie:

For example, to get to Beta, what content do we need and what's that criteria? What technical milestones are there?

We'd then break down the projects in the bug genie. For example, with caniuse, we want to map that structure to ours so we can ensure coverage.

1. Generate a site map of the current site
2. Identify what pages should be there that aren't
3. Do we want to stub in those pages so users don't have to worry about creating them -- or creating them in the wrong places?


Received on Tuesday, 5 March 2013 01:58:26 UTC

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