From W3C Wiki
Jump to: navigation, search

socialwg Teleconf 2016-10-25

Tuesdays at 10am US/Pacific, 1pm US/Eastern time for 60 minutes

  • Please plan 90 minutes for this week! We'll try to keep it to 60.
  • Check your timezone

Dialing / connection details:

Previous Meeting



  • Chair: Evan
  • Regrets
    • ...


Chair to start the meeting by typing on irc:

trackbot, start meeting

Trackbot should already be on the channel but if for some reason it is not call it with the following command:

/invite trackbot

Zakim won't know what meeting it is. Just ignore it. Pick a scribe from the list or ask Zakim to pick one up with the following command:

Zakim, pick a victim

Unfortunately Zakim has no idea who's scribed before so you may have to ask several times before getting an acceptable answer...

Then type:

scribe: xxx

Also, with WebEx, Zakim doesn't know who is on the call so, as people join they should record their attendance with the command: present+ <nickname>

For additional info, see the Zakim documentation page.



Approval of Minutes

Discussion Items

  • AS2 CR->PR status Evan & James (see CR to PR next steps below for details)
  • ActivityPub WD->CR status - cwebber
    • +1 if PROPOSED to publish new WD or WD->CR -- csarven (may not be able to attend meeting)
  • PubSub WD->CR status - Julien / Aaron
    • test suite? (Aaron volunteered last week)
  • Social Web Protocols: Publish new WD with updated status of our drafts
    • +1 if PROPOSED to publish new WD -- csarven (may not be able to attend meeting)
    • Updated for PubSub but still pending for LDN CR and Webmention PR - wait for those? - Amy Guy (talk) 15:29, 25 October 2016 (UTC)
  • Webmention issues
  • ...

Tracking Document Status

Explicit check for updates on all our documents - if not covered by individual Discussion Items above.

  • Document Status
  • Social Web Protocols: Discuss/Resolve a WD update if any of our documents changed status!

CR to PR next steps

CR to PR status and next steps (for any CRs not explicitly discussed above, let's ask these questions as we did at F2F7)

  • Any open normative issues? If so, review them
    • Any changes expected that will change conformance of existing implementations?
  • Disposition of comments?
  • State of the test suite - feature coverage? If not, when? If not, when plan?
  • Implementation reports?
  • Implementation report summary? (by feature, to determine state of CR exit)
    • How many implementations from non-editors of the spec?
    • How many implementations from people outside WG?
  • Errata process - how you will accept, process, and document errata once your spec is a REC. E.g. "github issues, processed in SWICG, documented ... github wiki or w3c wiki or another page on your one-off .net domain etc."
  • What else for CR to PR?

Next Meeting


Chair to close the meeting with the following command:

trackbot, end meeting

If you forget, trackbot will close the meeting for you when the activity dies down.

back to socialwg