Notice: The WebPlatform project, supported by various stewards between 2012 and 2015, has been discontinued. This site is now available on github.

Community Development

This is the Community Development Task Force meeting page.

See Community Development task force page.

Time: TBD

Zakim Bridge: +1.617.761.6200

Conference code: 3627 (“DOCS”)

VOIP: sip:zakim@w3.org

IRC Channel: #webplatform irc webchat

Tuesday, May 21, 2013 at 10:00 a.m. PDT / 1:00 p.m. EDT / 5:00 p.m. GMT

Agenda

  • Follow up on Action Items
  • Progress on projects
    • Doc sprints
    • University outreach
    • Recognition & rewards
    • Beta community efforts
    • Anything else?

Notes

Tuesday, May 07, 2013 at 10:00 a.m. PDT / 1:00 p.m. EDT / 5:00 p.m. GMT

Agenda

  • May 22nd NYC Doc Sprint has been canceled.
  • Tabled items from last week (see below)

Notes

Present: shepazu, julee, jswisher, scott_rowe, millo (IRC only)

  • Doc sprints

    • May 22nd NYC Doc Sprint has been postponed. Patrick is seeking a venue and a date.
    • North Carolina sprint (Doug) is looking unlikely.
    • No sprint for Portland/OSCON, as it’s mostly not a webdev conference; but do a WPD Wednesday that week.
    • Millo reports he has tentatively scheduled a sprint in Seattle for May 31st, in collaboration with U of Washington.
    • Jay Meissner is working on setting up a sprint in Zurich, in conjunction with a conference, August 28th.
    • Paul Verbeek (who attended the Berlin sprint) is organizing a sprint in conjunction with Fronteers in Amsterdam in October. Scott hopes to attend.
    • ACTION: Scott to update Events page (already DONE)
  • University outreach

    • Clarify what we’re asking academics to do
    • So far, just subscribe to a news list.
    • Not focusing (yet) on programs or direct recruiting
    • Reaching out to Tech Writing depts, like at UWash (not all U’s have them)
  • Beta community efforts

    • WPD Wednesday is to push towards beta content quality
    • Reviewing is one of the 5 tasks for WPD Wed, along with writing basic facts, writing explanations, writing examples with explanations, and filling in links to related content.
    • The CSS mailing list is a good place to recruit interested, knowledgeable people (not nec. CSS Working Group members, who are already over-burdened)
    • Can do a broadcast appeal on the list; better if comes from someone not affiliated with W3C. ACTION: Julee to send message that Doug has drafted.
    • Also approach list members 1-to-1: “Your post on X was great! Can you help write/edit/review WPD pages about X?” I.e., specific to that person, and their expertise, in response to something they did, asking for specific action. ACTION: Doug to ask Lea to keep an eye out for candidates; Julee is also on the list and can help.

Tuesday, April 30, 2013 at 10:00 a.m. PDT / 1:00 p.m. EDT / 5:00 p.m. GMT

Agenda

  • Progress on university outreach.
    • Spreadsheet created and sent to comm & recruiting TF members.
    • We want funding to go to content contributors, per Alex.
  • Should we have a launch plan for Beta: who will create & lead it?
  • Should we have a “New & Notable” checklist: a mini-launch list for great new content or features. Something like:
    • Get a couple of folks to look at it.
    • Get a campaign id for piwik.
    • Write a blog about it.
    • Send it out in social media.
    • Ask folks on the public list and IRC to re-tweet or whatever.
    • Get stewards to point to it from their highly-juiced pages.
  • Doc Sprint North Carolina (?)
  • Doc Sprint Zurich, targeted for August 28: Call for Experts, who can support the event on-site?
  • NYC Doc Sprint update
    • Patrick D’Souza working with venues to host the event before he starts promoting the event http://wpd-nyc.eventbrite.com/
    • One of the organizers of Patrick’s meetup has backed out because of some personal reasons so he’s working with another organizer Matt Mapplebeck to identify venues and promote it. Working with About.com to get them to host the event (tentative). Emails have been sent out to other potential venues and meetup organizers and I’m waiting for their response this week
    • Appnexus is unable to host the event as they are hosting some other events during that week.

Notes

Present

scottrowe, julee, patrickdsouza, shepazu, millo

Agenda items addressed

  • Progress on university outreach.
    • Spreadsheet created and sent to comm & recruiting TF members.
    • Considered jswisher’s (not present) recommendation against large-scale, cold-mailing.
    • Resolved to clarify purpose and approach for including university contacts on public-webplatform-news e-mail list.
      • Julee will respond to jswisher on public-webplatform e-mail list.
      • Approaching only known contacts, asking permission to include them first.
      • Working through contacts to recruit university students.
      • public-webplatform-news@w3.org:
        • Update current content areas of focus.
        • Announcements of fellowships, internships, etc.
        • Analytics & metrics (scoreboard), top pages, top contributors, etc. (patrickdsouza)
    • Millo will also reach out to contacts at IEEE and ACM university chapters
  • Should we have a launch plan for Beta: who will create & lead it?
    • Julee to include the following criteria in the Bet Criteria:
      • CSS Properties, HTML5 APIs complete
      • Gold standards and a representative page for each topic type
      • A cogent content architecture
      • Re-evaluate the flag system
        • More actionable: guide to contribution on the spot
        • Less cautionary: not so scary
        • A clear distinction as to the level of readiness for each page
      • Clearly defined on-boarding process
        • Editor’s guide, Getting Started guide improvements (julee and shepazu working on it)
        • More involvement from community leadership: office hours, content wrangling meeting
        • Clearly defined doc sprint process
  • Resources for achieving beta
    • Re-purpose steward resources toward beta priorities
    • Begin regular content wrangling sessions on IRC and direct new contributors through that process

Agenda items tabled

  • Clarify scope and purpose of university outreach with jswisher
  • Fellowships, funding for contributors in university outreach (jkomoros may have more information)
  • Beta leadership and timing
  • Doc sprints
    • New York, May 22-23
      • Patrick D’Souza working with venues to host the event before he starts promoting the event http://wpd-nyc.eventbrite.com/
      • One of the organizers of Patrick’s meetup has backed out because of some personal reasons so he’s working with another organizer Matt Mapplebeck to identify venues and promote it. Working with About.com to get them to host the event (tentative). Emails have been sent out to other potential venues and meetup organizers and I’m waiting for their response this week
      • Appnexus is unable to host the event as they are hosting some other events during that week.
    • North Carolina in August (?)
    • Zurich, targeted for August 28: Call for Experts, who can support the event on-site?
  • Should we have a “New & Notable” checklist: a mini-launch list for great new content or features. Something like:
    • Get a couple of folks to look at it.
    • Write a blog about it.
    • Send it out in social media.
    • Ask folks on the public list and IRC to re-tweet or whatever.
    • Get stewards to point to it from their highly-juiced pages.

===Minutes

10:03 AM <scottrowe_> community development task force meeting now starting 10:03 AM — scottrowe_ is scribe 10:03 AM ⇐ chrismills quit (~chrismill@135.244.112.87.dyn.plus.net) Quit: chrismills 10:03 AM — julee present 10:03 AM <Millo> present 10:03 AM → David_Herz joined (~wpd@46-116-231-237.bb.netvision.net.il) 10:03 AM — Millo 10:04 AM — Millo present 10:05 AM <scottrowe_> University outreach 10:06 AM <scottrowe_> jswisher (not present) recommends against cold-mailing. 10:08 AM <scottrowe_> we want to get folks on the news list 10:08 AM <scottrowe_> but the goals of University outreach may be beyond the news list and beta launch 10:10 AM <scottrowe_> milo recommends reaching out to IEEE and ACM 10:10 AM <scottrowe_> shepazu (not present) may have contacts 10:11 AM <scottrowe_> milo has contacts at IEEE and ACM 10:11 AM <scottrowe_> milo: need to define our goals, message 10:12 AM <scottrowe_> motion to table discussion until jswisher and shepazu can attend 10:14 AM — shepazu on the way 10:18 AM <patrickdsouza> sorry was away in meetings. 10:18 AM <patrickdsouza> still stuck in a meeting so i’m unable to attend 10:18 AM <patrickdsouza> the call 10:18 AM <scottrowe_> shepazu suggests that Milo take point of reaching out to ACM and IEEE 10:19 AM <patrickdsouza> following on irc 10:20 AM <scottrowe_> milo: need to define the message 10:20 AM <scottrowe_> AI: milo to define the message 10:21 AM <David_Herz> Sorry if this is out of line - I don’t know what the protocol is. Do I ask a question here? Can I put my hand up to make a comment? Anyway, what I want to ask is relative to the previous question about goals. In reaching out to universities, are we looking for collaborators or to make people aware of our docs as a source for developing best practices? In other words should people already be looking here as this being a com 10:21 AM <David_Herz> resource. If so, why start so late (i.e. university)? My kids, starting at 9 years old, are going to eCamp this summer. 10:22 AM <julee> We’re still going pursue University channels that are already there. 10:23 AM ⇐ Ryan_Lane quit (~Ryan_Lane@wikimedia/Ryan-lane) Ping timeout: 268 seconds 10:24 AM <scottrowe_> Resolved: still pursue university outreach, known, targeted audience 10:25 AM <scottrowe_> plan is to contact known persons directly and ask to be included on the news list 10:26 AM <scottrowe_> Criteria for Beta 10:27 AM <scottrowe_> issue: we don’t have enough resources to achieve beta status, as currently defined 10:27 AM <scottrowe_> link: 10:27 AM <julee> /docs/WPD/Project_Status 10:29 AM <scottrowe_> shepazu: do we have anyone driving creation of css pages? 10:29 AM <scottrowe_> julee: I am. Need to recruit (loop back to university outreach). 10:30 AM <julee> /docs/WPD/CSS_property_guide 10:30 AM <julee> https://docs.google.com/spreadsheet/ccc?key=0AkRs-89PKiZpdE0xdm9Sb1ZvRW1ZRzMtWEdyU0Z4OEE 10:30 AM <scottrowe_> shepazu: how many pages left to work on in CSS properties? 10:30 AM <scottrowe_> ^^ 10:31 AM → Ryan_Lane joined (~Ryan_Lane@wikimedia/Ryan-lane) 10:32 AM <scottrowe_> shepazu: proposes pulling our own resources off of other projects to drive CSS properties for beta 10:35 AM <patrickdsouza> do we have a hard deadline for beta ? 10:36 AM <scottrowe_> shepazu: proposes developing a task force for beta 10:42 AM <scottrowe_> shepazu: the task force comprised of web development people 10:44 AM <scottrowe_> milo: stewards could each take a batch of pages and drive their completion 10:52 AM <scottrowe_> julee: we need a recruiting plan 10:54 AM <scottrowe_> AI: julee to create recruiting plan with on-ramping description for CSS properties 10:55 AM <shepazu> patrickdsouza, we have a vague one, and we’re working toward a specific date 10:55 AM <patrickdsouza> thanks shepazu 10:58 AM <shepazu> David_Herz, right now, our main focus is on reference material, not the educational material. Once we’re in Beta, we’ll focus more on the educational stuff. So the current university push is to get web-savvy engineers and designers to help contribute 11:04 AM — Millo leave! 11:04 AM ⇐ Millo quit (836b93a9@gateway/web/freenode/ip.131.107.147.169) Quit: Page closed 11:04 AM <julee> /docs/WPD/Project_Status 11:12 AM <patrickdsouza> i’m thinking i should create a weekly analytics mail outlining the metrics for the last week 11:12 AM <patrickdsouza> top pages 11:12 AM <patrickdsouza> top tracking campaigns 11:13 AM <patrickdsouza> top trends 11:13 AM <patrickdsouza> do we want to pull data about pages worked on during the week 11:13 AM <patrickdsouza> top contributors for the week 11:13 AM <patrickdsouza> etc 11:21 AM ↔ patrickdsouza nipped out 11:23 AM <julee> shepazu: For Beta: CSS Properties are very good. 11:23 AM <julee> … Golden standards for each other topic type 11:23 AM <julee> … All of our msging should include links to those exemplars 11:24 AM <julee> … Re-evaluate the flag system 11:24 AM <julee> … Each flag a call to action 11:24 AM <julee> … how to display flags so they’re encouraging 11:24 AM <julee> … a very clear on-boarding process with a regular rythum 11:24 AM <julee> ummm… 11:24 AM <julee> ;-) 11:25 AM <julee> … a very clear Doc Sprint process 11:25 AM <julee> … and announcements 11:25 AM <julee> … flag system should make it clear whether page is ready to consume or ready to edit

Tuesday, April 23, 2013 at 10:00 a.m. PDT / 1:00 p.m. EDT / 5:00 p.m. GMT

Agenda

  • Progress on university outreach.
    • Spreadsheet created and sent to comm & recruiting TF members.
    • We want funding to go to content contributors, per Alex.
  • Doc sprints, tabled items from previous meeting.
  • Should we have a launch plan for Beta: who will create & lead it?
  • Should we have a “New & Notable” checklist: a mini-launch list for great new content or features. Something like:
    • Get a couple of folks to look at it.
    • Write a blog about it.
    • Send it out in social media.
    • Ask folks on the public list and IRC to re-tweet or whatever.
    • Get stewards to point to it from their highly-juiced pages.
  • Doug had a great idea
    • Add link to contributing to JS project on alert pages
    • Write a cool article about “do not track”
    • Promo it on reddit
    • Then, when folks come to visit they get the call to action~

Notes

Present

jswisher, scottrowe, patrickdsouza, shepazu

Agenda items addressed

  • Doc Sprint - New York, May 22-23
    • Patrick D’Souza has volunteered to be a leader/organizer
    • Doug will develop guidance, documentation, script for working on the JavaScript reference
    • Janet plans to attend
    • Scott plans to attend (tentative)
  • Doc Sprint OSCon, Portland, OR - July
    • Resolved to pursue running a small doc sprint during the week of the conference
    • Janet and Doug will be able to attend; Scott’s a maybe
    • Doug to look into getting space
  • Doc Sprint New York - September 13
    • No conference to coat-tail
    • Peter and Scott will handle all details
  • Doc Sprint Amersterdam - October
    • No new developments
    • Still on track
  • Doug’s great idea ~ discussion ensued
    • Develop a communication strategy for “seasonal” content (i.e. Do Not Track)
    • Recruit contributions
    • Utilize W3C and Steward company pipeline of releases and efforts (i.e. WebRTC)
    • Develop a WPD page banner for current area of emphasis
    • Blog, Tweet, etc.

Agenda items tabled

  • Progress on university outreach.
    • Spreadsheet created and sent to comm & recruiting TF members.
    • We want funding to go to content contributors, per Alex.
  • Should we have a launch plan for Beta: who will create & lead it?
  • Should we have a “New & Notable” checklist: a mini-launch list for great new content or features. Something like:
    • Get a couple of folks to look at it.
    • Write a blog about it.
    • Send it out in social media.
    • Ask folks on the public list and IRC to re-tweet or whatever.
    • Get stewards to point to it from their highly-juiced pages.
  • Doc Sprint North Carolina (?)

Minutes

10:01 AM <scottrowe_> Community Development Task Force Meeting Starting Now 10:05 AM → jswisher joined (~jswisher@cpe-173-174-46-161.austin.res.rr.com) 10:05 AM <jswisher> TOPIC: Doc sprints 10:06 AM <jswisher> scottrowe_: patrickdsouza is planning a doc sprint in NYC for 3rd week in May 10:06 AM <jswisher> patrickdsouza: what do you need to organize a doc sprint? 10:06 AM <jswisher> scottrowe_: a place, food, etc.; maybe get local sponsors 10:07 AM <scottrowe_> https://www.internetweekny.com/ 10:08 AM <jswisher> scottrowe_: also need a targeted promotion campaign 10:08 AM <jswisher> … if the audience is too general, not good 10:08 AM <jswisher> patrickdsouza: I have access to about 3000 JS devs through meetup 10:08 AM <jswisher> … what i need is someone with experience with doc sprints 10:09 AM <jswisher> scottrowe_: I might be able to make that, depending on the date 10:09 AM <jswisher> … Thursday is better than Friday, which is right before Memorial Day weekend 10:10 AM <jswisher> … Probably not good to do multiple days, in conjunction with Internet Week 10:10 AM <jswisher> shepazu: Should have a focus for the sprint, probably MS’s JS docs 10:11 AM <jswisher> … This should be an easy way to start participating, reviewing the imported docs 10:12 AM <jswisher> … Might be nice to have a per-page script to check for issues, or a checklist 10:14 AM <jswisher> … Need to find someone who is strong with JS to lead the sprint 10:14 AM <jswisher> scottrowe_: Need to define a process for people to follow, step by step 10:14 AM <jswisher> … Need someone to draw up the process, test it, etc. before the sprint 10:16 AM <jswisher> shepazu: Maybe get John Resig involved? 10:16 AM <jswisher> … I’ll see if he could do a keynote or something 10:17 AM <jswisher> jswisher: We should get someone who has experience with the WPD site 10:17 AM <jswisher> shepazu: I’m familiar with WPD and JS, and I’ll be there 10:17 AM <jswisher> scottrowe_: Might actually be a good idea to do multiple days 10:18 AM <jswisher> … There are a lot of other things going on that week, and that would give people more options of when to come 10:18 AM <jswisher> … Need to get the event onto the internet week event page 10:18 AM <jswisher> patrickdsouza: I can do that 10:19 AM <jswisher> shepazu: It’s only a month out, so need to start planning social media campaign now 10:20 AM <jswisher> patrickdsouza: How about Wednesday and Thursday? 10:20 AM <jswisher> scottrowe_: I can make it for that 10:21 AM <jswisher> TOPIC: Other doc sprints 10:22 AM <jswisher> scottrowe_: Dates for NYC sprint are May 22 and 23 10:22 AM <jswisher> shepazu: I should be able to make that 10:23 AM <jswisher> scottrowe_: Sprint at OSCON in Portland OR in July? 10:23 AM <jswisher> shepazu: I talked to someone from OSCON 10:24 AM <jswisher> … had a call last week, about WPD and W3Conf 10:25 AM <jswisher> … They are going to get back with me next week 10:25 AM <jswisher> … We may be able to get venue space from them 10:26 AM <jswisher> … In any case, we can find some venue in portland 10:28 AM <scottrowe_> http://www.oscon.com/oscon2013 10:31 AM <patrickdsouza> i need to peel off the call. i’m available on irc. 10:31 AM <patrickdsouza> yes wednesday and thursday. i’ll work on the venues. 10:34 AM <jswisher> http://www.communityleadershipsummit.com/ 10:37 AM <jswisher> jswisher: I’ll be in Portland that whole week, so maybe something Monday and Tuesday of that week 10:37 AM <jswisher> scottrowe_: Peter and I want to do a doc sprint in NYC on September 13 10:38 AM <jswisher> … To do thru Google, just have to fill out a form, and boom, instant doc sprint 10:38 AM <jswisher> … Not too close in time to Amsterdam sprint 10:39 AM <jswisher> … Amsterdam sprint is rolling along 10:40 AM <scottrowe_> /docs/WPD/Community/Meetings/Community_Development 10:41 AM <jswisher> TOPIC: Doug’s great idea 10:42 AM <jswisher> shepazu: patrickdsouza was talking about “evergreen” content vs. “seasonal” content 10:42 AM <patrickdsouza> yes 10:42 AM <jswisher> shepazu: e.g., evergreen is stuff that people will always be looking for, e.g., CSS properties 10:43 AM <patrickdsouza> seasonal is like the pointer event 10:43 AM <patrickdsouza> or do not track 10:43 AM <jswisher> seasonal is news-related or time-based 10:44 AM <jswisher> shepazu: It doesn’t make sense to buy ads for evergreen content, should do it for a seasonal campaign 10:44 AM <jswisher> … led me to think about what seasonal content we have 10:44 AM <jswisher> … currently, DRM and Do Not Track 10:45 AM <patrickdsouza> http://www.mediapost.com/publications/article/183963/ftc-defends-w3cs-do-not-track-initiative-to-congr.html#axzz2RJGLdvCH 10:45 AM <patrickdsouza> ftc 10:45 AM <jswisher> … Feds are telling ad companies to work with W3C if they don’t want external regulation 10:46 AM <jswisher> … Could have blog posts about technical aspects of these topics 10:47 AM <jswisher> … could drive traffic from hacker news, reddit, etc. 10:47 AM <jswisher> … We have our alpha disclaimer, but we don’t have a notice about our current push 10:48 AM <jswisher> … Let’s find a controversial thing to bring people to the site, and then they’ll see other things we’re working on 10:49 AM <jswisher> scottrowe_: sounds great, but how do you know when something is going to be in the news, and be prepared? 10:50 AM <jswisher> shepazu: Like what we did for pointer events, had presentations, wrote docs, coordinated with Last Call for the spec, did a blog post 10:50 AM <jswisher> … won’t always be feasible 10:50 AM <jswisher> … Should always have our current push in the banner 10:51 AM <jswisher> … things like DRM and DNT, have been bubbling for a couple of years 10:52 AM <jswisher> … W3C comms team is plugged into things that may come to the fore 10:52 AM <jswisher> … Stewards may also have info about upcoming news 10:52 AM → Ryan_Lane joined (~Ryan_Lane@wikimedia/Ryan-lane) 10:53 AM <jswisher> … We should have evergreen content ready to go, then do a blog post when there’s a news cycle about it 10:54 AM <jswisher> scottrowe_: some things like WebRTC are both new and exciting, and very slow moving 10:56 AM <jswisher> shepazu: we can’t always know, but if we know about something in advance, we should work on making sure we have docs for that 10:58 AM <jswisher> jswisher: We should look for ways to measure the effectiveness of different news cycles at bringing in contributors 10:58 AM <patrickdsouza> we can judge the effectiveness by using tracking campaigns 10:58 AM <scottrowe_> jswisher: need to establish success metrics around recruiting 11:03 AM <patrickdsouza> we definitely need to add tracking ids before a campaign to identify the success of a campaign(doc sprints or social media campaigns). number of comments and discussions around it and improvement in search engine rankings. 11:03 AM <patrickdsouza> and new v/s returning users. 11:04 AM <patrickdsouza> we can discuss this at the analytics task force meeting.

Tuesday, April 16, 2013 at 10:00 a.m. PDT / 1:00 p.m. EDT / 5:00 p.m. GMT

Agenda

  • Establish an irregular meeting time (lack of agenda cancels)
  • Doc Sprints - plan for up-coming events:
    • OpenHelp?
    • OS Con?
    • East Coast US?
    • Amsterdam?
  • Populate public-webplaform-news
  • Further planning

Notes

At today’s meeting of the Community Development task force, we had the following.

Agenda

  • Establish an irregular meeting time.
  • Develop a plan for university outreach and communication.
  • Decide when/where to hold up-coming doc sprints.

Actions

Meeting time
  • Resolved: the meeting’s appointed time shall remain Tuesdays via Zakim at 10:00 Pacific Time, to be held only if there is an agenda.
  • Doug (shepazu): confirm the Zakim reservation and reestablish the conference code, 3627 for these meetings.
University outreach
  • Julee to contact Alex (jkomoros) about potential internship funding and availability.
  • Julee to create internal spreadsheet listing contacts, their address and particulars.
  • All to fill in the spreadsheet with contacts - having done the legwork to sign them up.
  • Doug (shepazu) to contact W3C member universities.
  • Julee to edit student recruitment message [1] with more detail about internships and specific tasks/projects for recruits.
Doc Sprints
  • Resolved: Holding a doc sprint at OpenHelp would be contingent upon Mozilla also holding a doc sprint. Not likely.
  • Tabled: Doc sprint at OSCon, July in Portland, OR.
  • Tabled: Doc sprint to coincide with Internet Week New York [2].
  • Tabled: Doc sprint in North Carolina.
  • Tabled: Doc sprint in New York or Boston area late summer.
  • Scott: To work with Peter to identify conferences to target for New York/Boston late summer.
  • Tabled: Doc sprint in Amsterdam, with Frontiers conference in October.
Next meeting

We’ll hold another meeting next week to discuss progress on actions and tabled items.

Minutes

10:10 AM — julee present 10:12 AM <scottrowe_> present 10:12 AM — jswisher is present 10:12 AM <shepazu> present 10:12 AM <waiseto> present 10:12 AM → Ryan_Lane joined (~Ryan_Lane@wikimedia/Ryan-lane) 10:13 AM <scottrowe_> first decision: we’ll keep this time and bridge 10:13 AM <scottrowe_> Doug will make sure that the old conference number, 3627 is valid 10:15 AM <scottrowe_> /docs/WPD/Projects/Communications/Universities 10:17 AM <scottrowe_> University outreach: Julee edited the above 10:18 AM <scottrowe_> jkomoros mentioned that there may be internship money available. 10:23 AM <scottrowe_> AI: Julee to confirm with Doug, Alex that we have a program in place before we advertise it in public-webplatform-news. 10:23 AM <scottrowe_> It may be a Google Summer of Code or like program. 10:24 AM → jay_ joined (57bd77b9@gateway/web/freenode/ip.87.189.119.185) 10:25 AM <scottrowe_> jswisher: Summer of Code excludes documentation work 10:32 AM <scottrowe_> AI: Wei to send note to Web Education group of W3C, requesting subscriptions to public-webplatform-news, with the body of Julee’s Universities note. 10:43 AM <scottrowe_> AI: Julee to create an internal (not shared publicly) spreadsheet of addresses. 10:46 AM <scottrowe_> AI: All to contribute recruits to the spreadsheet. 10:46 AM <julee> W3C university members 10:46 AM <scottrowe_> AI: shepazu to contact Universities that are members of W3C 10:46 AM <waiseto> http://www.w3.org/Consortium/Member/List :) 10:47 AM <scottrowe_> jswisher: English writing programs, technical communication, engineering. 10:50 AM <scottrowe_> next topic, doc sprints 10:50 AM <scottrowe_> shepazu: would like to know who can help with an east coast doc sprint 10:51 AM <scottrowe_> julee: question on the suitability of OpenHelp 10:52 AM <scottrowe_> jswisher: OpenHelp does not attract a lot of web developers 10:52 AM <scottrowe_> shepazu: we would need to reruit our own attendees 10:56 AM <scottrowe_> shepazu: attending with Mozilla would build ties between us and Moz 10:56 AM <scottrowe_> shepazu: might be an opportunity to build content on both sites 10:58 AM <julee> https://www.internetweekny.com/ 11:01 AM <julee> /docs/WPD/Community/Community_Events 11:01 AM <scottrowe_> resolved: Doc Sprint at OpenHelp contingent upon Mozilla’s participation. 11:02 AM <scottrowe_> Meeting adjourned

[1] /docs/WPD/Projects/Communications/Universities [2] https://www.internetweekny.com/