<trackbot> Date: 06 May 2015

<janina> trackbot, start meeting

<trackbot> Meeting: Protocols and Formats Working Group Teleconference

<trackbot> Date: 06 May 2015

<janina> agenda: this

<scribe> scribe: fesch

preview agenda with items from two minutes

js: need to look at telecom and going public

Previous Meeting Minutes https://www.w3.org/2015/04/22-pf-minutes.html

RESOLUTION: publish minutes as posted

New Minuting Procedure

js: PF is OK with going fully public, Judy added to charter discussions
... MC and JS checked into how to go public, talked to admin,

mc: has not heard back from admin on member PF list, being read only

js: Any opinions on going public?

<richardschwerdtfeger> go publix

<richardschwerdtfeger> public

js: PROPOSES to go public immediately

jn: can we ask whether something should be minuted?

js: sure

mc: please say in advance, please don't minute that --- helps the scribe :)

jn: scribe doesn't always accurately captured what you said, and potential liability

mc: we could ask minutes generator, putting a disclaimer - about the accuracy of scribing

js: might put in policy statement on the web page for the renamed group

PROPOSAL: make minutes public today,

RESOLUTION: PF will being posting all minutes into the public list and will seek to make the member list read only

<JF> +1

js: not many groups in members (only) space
... how do we handle old member only space - keep it member only

rs: what are the chances we can make the issues and actions list public?

mc: we will need to do it with the new group, rather not make the current one public for a month, and need to protect old stuff

jn: what is the harm in having an aria and pf tracker?

mc: lists technical issues

js: was going to put on the agenda whether we want separate lists for aria and apa
... scope of permitted work of (ARIA, APA) groups would be

sm: thought we were going to git anyway?

mc: bugzilla was a plan, still using tracker because of IRC integration
... need to decide on use of tracker or not and if so configuration

sm: lives and breathes perl...
... speaks bugzilla API, hasn't looked at github

js: would be interesting to know how big a job integrating with bugzilla, github would be

sm: another group, maybe web payments has already done it

<MichaelC> ACTION: shane to investigate possibilities of IRC bot integration with Bugzilla and GitHub [recorded in http://www.w3.org/2015/05/06-pf-minutes.html#action01]

<trackbot> Created ACTION-1630 - Investigate possibilities of irc bot integration with bugzilla and github [on Shane McCarron - due 2015-05-13].

jn: hates tracker

<MichaelC> action-1630 due 2 weeks

<trackbot> Set action-1630 Investigate possibilities of irc bot integration with bugzilla and github due date to 2015-05-20.

Welcome to Webex

js: zakim is being decommissioned due to cost
... moving to webex temporarily
... this meeting will be on webex by June
... android client is reasonably accessible, other clients less so
... JW wasn't able to edit
... need to play with it, before committing to it
... do whatever you need to do audio over webex

<MichaelC> MIT WebEx

js: will continue to use IRC
... need to record your attendence
... webex can call you

cs: can I call from a phone?

mc: don't know of a touch tone method to get on the queue
... can get the conference code and dial in
... code will be different for every meeting
... code not mnemonic

jn: code different each week?

mc: no

js: each weekly call will have a code

jf: you can set up a recurring meeting and keep the same code
... can use a link (URI) to access it

sm: on reason to use webex is for screen sharing are we using that?

JS: not using screen sharing
... can create a astrix solution
... I think that cost is an issue
... might be a misunderstanding on what it takes to support a 100 users over SIP with an astrix server

<Zakim> Michael_Cooper, you wanted to talk about screen sharing and to talk about ¨interim solution¨

mc: cost of zakim will become $50K a month...

js: axtrix should also have built in web RTC support

mc: webex has screensharing, most likely not accessible ... discovered strange issues with presenter status being stolen... don't plan to use it, except in exceptional cases

js: thanks Shane for looking at astrix
... most POTS, would expect more SIP, have more SKYPE users
... a lot of companies use SIP calls internally

cs: are their accessible SIP clients?

js: yes

Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open

action-1615

<trackbot> action-1615 -- Janina Sajka to Review media capture and streams http://www.w3.org/tr/mediacapture-streams/ -- due 2015-05-06 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1615

new on TR http://www.w3.org/TR/tr-status-drafts.html#tr_LCWD

<MichaelC> Credential Management Level 1

mc: no new last calls or CR

sm: already reviewing... this is really password management

<MichaelC> ACTION: shane to review Credential Management Level 1 http://www.w3.org/TR/credential-management-1/ [recorded in http://www.w3.org/2015/05/06-pf-minutes.html#action02]

<trackbot> Created ACTION-1631 - Review credential management level 1 http://www.w3.org/tr/credential-management-1/ [on Shane McCarron - due 2015-05-13].

Rechartering Continued

Community Groups http://www.w3.org/community/groups/

mc: no community groups this week

Rechartering Continued

js: conversations have slowed down, drafts of charters... both together and split

<MichaelC> Draft updates to the APA charter

mc: minor changes to existing group

<MichaelC> Draft ARIA charter

mc: two other charters if we split, ARIA might not be a good name

<MichaelC> Draft spec review charter

mc: take over non recommendation track doc work

<MichaelC> Web Technology Accessibility Guidelines

cs: where would Web Technology Accessibility Guidelines go?

mc: spec review group - as a working group note - would be cool if it were rec track...

cs: don't know how seriously it would be taken as a note

mc: we should discuss that
... it is in the spec review charter

sm: CR only applies to normative requirements, if no normative requirements we don't have to worry about it

<Zakim> joanie, you wanted to ask about ARIA deliverables on the milestones

jd: on draft ARIA charter, for ARIA 1.1, milestone table - do we plan to be ARIA 1.1 feature frozen by July 2015?

mc: milestones same in charters, but are out of date, should talk about that before sending charter forward

cs: ARIA 2.0 is not in the charter

<joanie> +1 to 2.0 in the charter

cs: would like to see ARIA 2.0 in the charter

mc: wording says ARIA 1.1 and later... which allows us to work on it

rs: I don't think we can wait more than 3 years to work on ARIA 2.0

mc: have 9 docs, need a reasonable time line

sm: need to give subgroups an action to come back with it next week

rs: want to discuss extension issues, what is happening with user context properties?

mc: in draft ARIA charter

rs: worried about having too much in the ARIA group
... where is the COGA work?

js: stays in APA
... we have a call for consensus please respond

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/protect/need to protect/
Found Scribe: fesch
Inferring ScribeNick: fesch
Default Present: Fred_Esch, James_Nurthen, Rich_Schwerdtfeger, Michael_Cooper, Joanmarie_Diggs, janina, +1.612.406.aaaa, ShaneM, JF, Cynthia_Shelly, Tzviya, Matt_King
Present: +1.612.406.aaaa Cynthia_Shelly Fred_Esch JF James_Nurthen Joanmarie_Diggs Michael_Cooper Rich_Schwerdtfeger ShaneM janina
Agenda: https://lists.w3.org/Archives/Public/public-pfwg/2015May/0038.html
Found Date: 06 May 2015
Guessing minutes URL: http://www.w3.org/2015/05/06-pf-minutes.html
People with action items: shane