15:52:05 <RRSAgent> RRSAgent has joined #ab
15:52:05 <RRSAgent> logging to http://www.w3.org/2014/12/01-ab-irc
15:52:39 <virginie> agenda?
15:52:44 <virginie> agenda+ welcome
15:53:11 <virginie> agenda+ AB project reminder and working method
15:53:38 <virginie> agenda+ picking priorities and directions
15:53:48 <virginie> agenda+ action list
15:53:58 <virginie> agenda+ next call (if required)
15:54:01 <virginie> agenda?
15:55:26 <dka> dka has joined #ab
15:58:49 <Zakim> AB_(Project)11:00AM has now started
15:58:56 <Zakim> +??P0
15:59:16 <virginie> zakim, ??P0 is me
15:59:16 <Zakim> +virginie; got it
16:00:47 <timeless> Zakim, code?
16:00:47 <Zakim> the conference code is 2277 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), timeless
16:01:09 <Zakim> +timeless
16:01:13 <timeless> Zakim, mute me
16:01:13 <Zakim> timeless should now be muted
16:01:22 <timeless> Zakim, who is on the call?
16:01:22 <Zakim> On the phone I see virginie, timeless (muted)
16:01:24 <Zakim> +[IPcaller]
16:01:32 <ArtB> ArtB has joined #ab
16:01:34 <Zakim> +dka
16:01:39 <timeless> scribe: timeless
16:01:49 <rubys> rubys has joined #ab
16:01:59 <virginie> zakim, who is on the phone ?
16:01:59 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka
16:02:11 <Zakim> +Jeff
16:02:28 <virginie> zakim, who is on the phone ?
16:02:28 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka, Jeff
16:02:33 <Zakim> +Sam
16:02:37 <Zakim> +Art_Barstow
16:02:47 <jeff> jeff has joined #ab
16:02:50 <virginie> zakim, who is on the phone ?
16:02:50 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka, Jeff, Sam, Art_Barstow
16:02:56 <timeless> Zakim, take up agenda 1
16:02:56 <Zakim> agendum 1. "welcome" taken up [from virginie]
16:03:36 <timeless> virginie: roundtable ... introductions, maybe?
16:03:47 <timeless> ... elf-pavlik
16:04:35 <timeless> virginie: virginie xx
16:04:45 <timeless> ... i offered to lead w3 coordination discussion
16:04:53 <timeless> ... is it good, possible ways to improve
16:04:58 <chaals> zakim, code?
16:04:58 <Zakim> the conference code is 2277 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), chaals
16:05:04 <virginie> zakim, who is on the phone ?
16:05:04 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka, Jeff, Sam, Art_Barstow
16:05:13 <timeless> Zakim, unmute me
16:05:13 <Zakim> timeless should no longer be muted
16:05:25 <bkardell_> bkardell_ has joined #ab
16:05:38 <Zakim> +[IPcaller]
16:05:41 <timeless> timeless: Josh Soref, BlackBerry
16:05:44 <chaals> zakim, [ip is me
16:05:44 <Zakim> +chaals; got it
16:05:57 <timeless> ... coordination is important, and there are cases where it doesn't work
16:06:00 <timeless> elf-pavlik: XXX
16:06:09 <timeless> ... I joined because we
16:06:15 <timeless> ... i was involved in schema.org
16:06:17 <dka> elf you keep dropping out
16:06:21 <timeless> Zakim, mute me
16:06:21 <Zakim> timeless should now be muted
16:06:27 <timeless> ... I was involved w/ Action Handlers
16:06:37 <dka> though timeless seems ot have no problem. :)
16:06:38 <timeless> ... I also worked w/ Liaison TF in Social IG
16:06:48 <timeless> dka: dka, Telefonica, CoChair of TAG
16:06:54 <ArtB> ArtB: I'm here as "Friend of the Consortium". I support this effort to try to get better technical coordination for Consortium's broad set of technical work.
16:06:55 <timeless> ... with a TAG hat that i'm here
16:07:05 <timeless> ... general "W3C" making W3C work better hat
16:07:23 <timeless> ... to reflect tbl's comments
16:07:37 <timeless> ... if this involves source control (github), we have a positive view on
16:07:41 <timeless> ... maybe i can channel on that
16:07:49 <elf-pavlik> minutes from Social WG + Schema.org meeting at TPAC http://www.w3.org/2014/11/tpac-social-minutes.html
16:08:04 <timeless> jeff: Jeff Jaffe, W3C CEO
16:08:18 <timeless> ... we have a lot of places to coordinate, and need solutions in places
16:08:24 <rubys> http://intertwingly.net/blog/2014/11/20/WHATWG-W3C-Collaboration
16:08:26 <timeless> rubys: Sam Ruby, CoChair of HTML WG
16:08:34 <timeless> ... I'm an editor of the URL spec
16:08:36 <virginie> zakim, who is on the phone ?
16:08:36 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka, Jeff, Sam, Art_Barstow, chaals
16:08:44 <ArtB> sorry, I'm muted
16:08:55 <ArtB> ArtB: I'm here as "Friend of the Consortium". I support this effort to try to get better technical coordination for Consortium's broad set of technical work.
16:09:20 <timeless> chaals: Chaals Nevile, Yandex, CoChair Web Apps
16:09:27 <timeless> ... do stuff across w3c for a very long time
16:09:36 <bkardell_> "Chapters" efforts to involve scores of developers will pose some interseting new challenges as well... sorry I'm having phone issues
16:09:41 <timeless> ... i think it's important that we work out coordination across large areas
16:09:48 <virginie> zakim, who is on the phone ?
16:09:48 <Zakim> On the phone I see virginie, timeless (muted), elf-pavlik (muted), dka, Jeff, Sam, Art_Barstow, chaals
16:09:49 <timeless> ... it's an important part of W3C
16:09:56 <virginie> agenda?
16:10:14 <timeless> Zakim, take up agenda 2
16:10:14 <Zakim> agendum 2. "AB project reminder and working method" taken up [from virginie]
16:10:32 <timeless> virginie: because the scope is quite large, and each of us may have different priorities
16:10:39 <timeless> ... this is where we may choose priorities
16:10:44 <timeless> ... and try to make an action list
16:10:50 <timeless> ... and see if we need a call after this
16:10:58 <Zakim> +[IPcaller]
16:11:02 <timeless> ... we have an hour call, (50mins left), we can end it quicker
16:11:13 <timeless> bkardell_: Brian Kardell
16:11:22 <rubys> zakim, [ is bkardell_
16:11:22 <Zakim> +bkardell_; got it
16:11:38 <timeless> ... it sounded intriguing to me, that we have a group trying to help synchronize
16:11:57 <virginie> https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_synchro_consistency_plan
16:11:59 <timeless> ... it's a really necessary thing, i'm heading up efforts to involve scores of developers in reviews
16:12:03 <timeless> ... something we've never done before
16:12:11 <timeless> i//Brian/Topic: Welcome/
16:12:16 <timeless> Zakim, take up agenda 2
16:12:16 <Zakim> agendum 2. "AB project reminder and working method" taken up [from virginie]
16:12:34 <timeless> virginie: it was proposed to the AC members during the AB meeting
16:12:42 <timeless> ... W3C is developing lots of new features
16:12:53 <timeless> ... and there may be interest to make sure we don't lose control of development
16:13:00 <timeless> ... to make sure everyone is aware of what's going on
16:13:22 <timeless> ... we need to make sure that different communities around W3 are coordinated
16:13:30 <timeless> ... WGs, W3C, developers
16:13:54 <timeless> ... formatting information, threading it, using appropriate tools
16:14:03 <timeless> ... making sure that W3C is coordinated
16:14:12 <timeless> ... Domains (Activities, ...)
16:14:25 <timeless> ... making sure that there's correct socialization of new technologies
16:14:36 <timeless> ... i added what tbl wrote to the list
16:14:54 <timeless> ... potentially adding Good Practices to the Process
16:15:11 <virginie> q?
16:15:13 <timeless> ... most of w3c activities are led by humans, it's not just process, it's also communicating
16:15:35 <timeless> ... you can add your own ideas / share your views on how w3c communities can be better synchronized
16:15:39 <timeless> ... we decided to work in public
16:15:43 <timeless> ... potentially using calls
16:15:45 <timeless> ... using the Wiki
16:15:50 <timeless> ... there's also an ML
16:15:54 <virginie> mailing list : http://lists.w3.org/Archives/Public/public-coord-mechanisms/
16:16:00 <timeless> ... you can subscribe
16:16:06 <dka> q+
16:16:08 <timeless> ... questions?
16:16:10 <timeless> ack dka
16:16:36 <timeless> dka: i don't know if you've ever been on a Coordination Group Call
16:16:40 <timeless> timeless: I haven't
16:16:46 <timeless> dka: those have been around for a while
16:16:56 <timeless> ... are those in the thinking of how we attack this problem
16:17:01 <ArtB> (FYI, I just added a Scope section to the wiki: https://www.w3.org/wiki/AB/2014-2015_Priorities/w3c_synchro_consistency_plan#Scope)
16:17:04 <timeless> ... a warning about that
16:17:10 <timeless> ... for years I was on HTML Coordination
16:17:15 <timeless> ... it became the most dreaded call in my diary
16:17:18 <timeless> ... there was no information
16:17:34 <timeless> ... not that it was boring, but it wasn't useful
16:17:45 <timeless> ... i don't want to create things that take up people's time in the name of coordination
16:17:51 <timeless> ... i like the idea of using automated tools
16:17:53 <timeless> ... dashboards
16:18:08 <timeless> ... i'm warning against mechanisms that require a lot of individuals' time
16:18:12 <timeless> virginie: very good warning
16:18:13 <timeless> q?
16:18:15 <virginie> q?
16:18:40 <timeless> virginie: i had more in mind to format information
16:18:44 <timeless> ... rather than having calls
16:18:48 <timeless> ... i know everyone is very busy
16:18:53 <timeless> ... i agree that tools would be great
16:18:59 <elf-pavlik> tools/dashboard reminds me of http://okfnlabs.org/dashboard/
16:19:03 <timeless> ... one of the questions i had during the last AB meeting
16:19:09 <timeless> ... imagine we invented a great tool
16:19:16 <timeless> ... how do we make sure we have one great tool in w3c
16:19:34 <timeless> ... we need to put high priority on developing the tool
16:19:52 <timeless> ... for me one of the facets would be distribute appropriate (?) information
16:19:54 <dka> Something like an activity feed…
16:19:57 <timeless> ... i see elf-pavlik provided a dashboard
16:19:58 <chaals> q+
16:20:09 <timeless> ack chaals
16:20:22 <timeless> chaals: having a dashboard that you can look at is pretty helpful
16:20:25 <timeless> ... it's a lot of work
16:20:29 <timeless> ... when do you need to be aware of stuff
16:20:38 <timeless> ... there are a few straigth-forward things
16:20:43 <timeless> ... knowing what a piece of work is
16:20:51 <timeless> ... we got a request in WebApps from A11y
16:21:02 <timeless> ... you have a pile of specs, it doesn't explain what is going on
16:21:14 <timeless> ... to have to read the entire spec to figure out if it's worth commenting
16:21:25 <timeless> ... having a way to look at the specs, figure out what they do
16:21:34 <timeless> ... once upon a time you could probably use the /TR/ page
16:21:43 <timeless> ... but recently when I tried, that failed
16:21:49 <timeless> ... you have to keep clicking
16:22:04 <ArtB> (FYI, Dashboard wiki https://www.w3.org/wiki/Dashboard )
16:22:04 <timeless> ... usually the a11y people are the only ones who know if you need a11y input
16:22:17 <timeless> ... but the people working on the spec don't know
16:22:34 <timeless> virginie: ArtB put a dashboard link in irc
16:23:00 <timeless> ... i think IanJ also mentioned trying to improve communication tools of W3C
16:23:07 <timeless> ... i should check on the status
16:23:12 <virginie> q?
16:23:13 <bkardell_> ?+
16:23:18 <timeless> s/?+/
16:23:19 <timeless> q?
16:23:20 <Zakim> -virginie
16:23:21 <bkardell_> lol
16:23:21 <timeless> q+ bkardell_
16:23:30 <timeless> s/lol//
16:23:34 <timeless> RRSAgent, draft minutes
16:23:34 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html timeless
16:23:36 <dka> you dropped?
16:23:40 <virginie> sorry, was dropped :)
16:23:41 <timeless> RRSAgent, make logs world
16:23:46 <timeless> s/you dropped?//
16:23:51 <timeless> s/sorry, was dropped :)//
16:23:54 <timeless> RRSAgent, draft minutes
16:23:54 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html timeless
16:24:01 <timeless> chair: virginie
16:24:13 <bkardell_> ok, so here's my q...
16:24:38 <Zakim> +??P0
16:24:45 <timeless> s/ok, so here's my q...//
16:24:48 <timeless> ack bkardell_
16:24:52 <virginie> zakim, ??P0
16:24:52 <Zakim> I don't understand '??P0', virginie
16:25:03 <virginie> zakim, ??P0 is me
16:25:03 <Zakim> I already had ??P0 as virginie, virginie
16:25:05 <timeless> bkardell_: what kind of data are you hoping to capture in the dashboard?
16:25:17 <timeless> ... lots of developers have no idea what specs are being worked on/what state they're in
16:25:22 <timeless> ... that's hard to track
16:25:34 <timeless> ... browsers keep something of what they've spiritually agreed to
16:25:41 <timeless> ... what they haven't commented on
16:25:45 <timeless> ... that data is available
16:25:48 <timeless> ... if you needs review
16:25:55 <virginie> q?
16:25:55 <timeless> ... what sorts of things do you think need to be in a dashboard
16:26:19 <timeless> virginie: for myself, the kind of information i'd expect to be propagated across w3c contributors
16:26:30 <timeless> ... specs, status, potential impact on the open web platform
16:26:40 <timeless> ... level of commitment (lively) to the spec
16:26:50 <timeless> ... this is a long term effort
16:27:19 <timeless> ... i wouldn't be able to tell you which dashboard i'd like to have
16:27:29 <timeless> ... from my experience, not living in Silicon Valley
16:27:37 <timeless> ... not having Browser Vendors as my best friends
16:27:43 <timeless> ... not taking coffee with them every day
16:27:46 <timeless> ... it's hard for me to know
16:27:54 <timeless> ... I'm looking for a snapshot of current development
16:28:03 <timeless> ... and being able to dive in
16:28:07 <bkardell_> +1 to all that
16:28:14 <timeless> ... without having to join a ML w/ 500 emails
16:28:29 <chaals> q+
16:28:34 <timeless> ... depending on who you are, you should be able to get the information you want
16:28:41 <timeless> ... i know there's the idea of developing a spec on github
16:28:46 <timeless> ack chaals
16:29:01 <timeless> chaals: i'm reminded that there used to be an SVG that the Team would trot out
16:29:07 <timeless> ... that shows the WGs
16:29:12 <timeless> ... afaik, that's no longer maintained
16:29:16 <timeless> ... the UCs I have
16:29:36 <timeless> ... 1. "we are interested in some kind of feature some where, how do we do it, who cares? what spec/group?"
16:29:42 <timeless> ... I go ping people/hunt around random sources
16:29:55 <timeless> Meeting: AB Specification Coordination Teleconference
16:30:03 <bkardell_> even more complex when you go outside the organization :)
16:30:15 <timeless> ... the recent list for "requests for review" is helpful for tracking "when things are coming up now"
16:30:26 <timeless> ... answers "what do i need to ask people to look at"
16:30:30 <timeless> ... the other side is
16:30:35 <timeless> ... WebApps has "PubStatus"
16:30:36 <Zakim> +[IPcaller]
16:30:46 <timeless> ... PubStatus tells you where each document is up to
16:30:52 <timeless> ... it doesn't tell you much about what a document is
16:30:58 <timeless> ... I know, because i'm in webapps
16:31:08 <timeless> ... for people in other groups, that document wouldn't be enough to understand what the work is
16:31:33 <timeless> virginie: would you see a categorization of the features
16:31:39 <timeless> ... what would help to find the appropriate information?
16:31:57 <timeless> chaals: there's a point where "if you don't have two full time librarians", "you won't achieve much"
16:32:05 <bkardell_> q+
16:32:06 <timeless> ... ideally you'd have people who could describe features
16:32:14 <timeless> ... so you could browse by features
16:32:21 <timeless> ... being able to look at what a group works on
16:32:22 <bkardell_> q-
16:32:26 <timeless> ... and the specs that they have
16:32:29 <timeless> ... see what specs are related
16:32:31 <ArtB> Sounds like we need some Best Practices re documenting a "good" Abstract, Introduction, UCs, etc.
16:32:40 <bkardell_> q+
16:32:44 <timeless> ... how you easily collect that information beyond a search engine
16:32:48 <timeless> ... there are metadata solutions
16:32:55 <timeless> ... but that's pretty hard to maintain
16:33:08 <timeless> ... groups are useless at providing good metadata
16:33:10 <elf-pavlik> re specs relevance: if we automate tracking dependencies we can detect some similarities
16:33:14 <timeless> ... (historically)
16:33:26 <jeff> q+
16:33:31 <timeless> ack bkardell_
16:33:50 <timeless> bkardell_: if we shoot for perfect, we'll never get there
16:34:02 <timeless> ... i know the annotation stuff, i know it isn't quite ready, but pretty close
16:34:12 <timeless> ... if we could get the ability for individuals to annotate on specs
16:34:21 <timeless> ... especially if the community could do legwork for us
16:34:26 <chaals> [+1/2]
16:34:29 <timeless> ... i feel that could be useful, and mostly maintained by the community
16:34:32 <timeless> q?
16:34:37 <timeless> ack jeff
16:34:48 <timeless> jeff: i wanted to share an idea which came up in a different context
16:34:55 <timeless> ... at TPAC, we had a Chairs breakfast
16:35:01 <chaals> [Things that are mostly maintained by the community but on which we really rely have some issues - although as Brian points out, perfect is the enemy of good...]
16:35:01 <timeless> ... one of the questions that came up from the Chairs
16:35:14 <timeless> ... there was the sense that they also need some kind of coordination
16:35:28 <timeless> ... i didn't interpret it as a tight closed loop kind of coordination
16:35:37 <timeless> ... like the kind once hoped for in Coordination Groups
16:35:44 <timeless> ... or a wiki where you can get everything you want
16:35:57 <timeless> ... i interpreted it as a request for loose coordination
16:36:04 <timeless> ... in the Team we have a Project Review
16:36:20 <timeless> ... from time to time, if someone's Project (WG, WG Document) has made an advance
16:36:29 <timeless> ... the Team Contact would schedule an hour/two
16:36:37 <timeless> ... and everyone on Team could get an update on that item
16:36:48 <timeless> ... we had the idea to broaden that concept beyond the Team
16:36:54 <timeless> ... maybe Team + Chairs + TAG + AB
16:37:15 <timeless> ... anyone in that group of "Thought Leaders for W3C" who thinks it could/should be shared broadly
16:37:19 <timeless> ... could request a timeslot
16:37:28 <timeless> ... to give an informal discussion/formal presentation
16:37:36 <timeless> ... have a once a week timeslot
16:37:38 <virginie> zakim, who is on the phone ?
16:37:38 <Zakim> On the phone I see timeless (muted), elf-pavlik (muted), dka, Jeff, Sam, Art_Barstow, chaals, bkardell_, virginie, [IPcaller]
16:37:46 <timeless> ... koalie volunteered to work on it
16:37:57 <timeless> ... i'm not proposing that this would solve this TF's task
16:38:09 <timeless> ... but it's an approach that could address part of this problem
16:38:18 <timeless> timeless: i'd like to have that as Publicly available for others
16:38:31 <timeless> virginie: dka briefly mentioned at the beginning of the call
16:38:51 <timeless> ... each WG chooses its Work Method / Tools
16:38:59 <timeless> ... reporting from each WG is different
16:39:07 <timeless> ... there's a trend to move to GitHub management
16:39:17 <elf-pavlik> eg. https://github.com/jasnell/w3c-socialwg-activitystreams
16:39:22 <timeless> ... there was a request from BradHill to have Best Practices for moving to Github
16:39:31 <timeless> ... there's a guideline provided by npdoty
16:39:35 <timeless> ... that can be improved
16:39:47 <timeless> ... I'm not saying it's a solution for great coordination across w3 communities
16:39:57 <timeless> ... having reliable tools, would be good
16:40:07 <timeless> ... a direction we should look for
16:40:19 <timeless> ... jeff ... you may have access to information on priorities
16:40:33 <timeless> ... is there anything planned... moving everyone to a Github like tool?
16:40:40 <timeless> jeff: i don't think we have a plan like that
16:40:47 <timeless> ... i know darobin and others are looking at
16:40:54 <timeless> ... how do we make github more usable/more consistent
16:41:01 <timeless> ... in terms of a forced march
16:41:19 <timeless> ... I don't think we're likely to duplicate github, and we're not going to force people to use it
16:41:23 <timeless> ... nothing so comprehensive
16:41:41 <timeless> dka: i get worried about people moving to a Github-like-tool
16:41:54 <timeless> ... i think people want to move to Github because that's where there other work is
16:42:00 <timeless> ... there's network effects w/ github
16:42:03 <timeless> q+
16:42:10 <timeless> ... my concern w/ Github is on the long term
16:42:11 <bkardell_> +1
16:42:16 <timeless> ... i think tbl had concern in his email
16:42:23 <virginie> dan refers to http://lists.w3.org/Archives/Public/public-w3process/2014Dec/0004.html
16:42:24 <timeless> ... part of the value of W3C is long term history
16:42:42 <timeless> ... W3C's Mission outlasts other things on the web
16:42:46 <timeless> ... stuff on the web might come/go
16:42:52 <timeless> ... W3C continues to play its role
16:43:00 <timeless> ... I'd expect W3C to outlast Github
16:43:12 <timeless> ... even though right now the developer community won't think about Github going away
16:43:12 <bkardell_> "github like" may be counter productive actually, i think it would be really off-putting
16:43:17 <elf-pavlik> i could try checking with sys team about option to setup open source clone https://about.gitlab.com/
16:43:19 <timeless> ... W3C needs to plan on
16:43:43 <timeless> ... concretely, it's important that w3c has a backup of what is in Github
16:43:50 <timeless> ... those are the concerns i have
16:43:59 <timeless> ... when I mentioned Activity Streams earlier
16:44:04 <bkardell_> instead of people saying "yay it's git" I think people will just say "look how out of touch W3C is"
16:44:06 <timeless> ... I had in mind a Github stream
16:44:15 <timeless> ... What people have mentioned you
16:44:23 <timeless> ... being able to wrap it up in a dashboard
16:44:28 <timeless> ... replicating that/having that view would be good
16:44:29 <timeless> q?
16:44:31 <virginie> q?
16:44:34 <timeless> ack me
16:44:50 <elf-pavlik> timeless: tried github to give formal feedback on specs
16:45:03 <elf-pavlik> ... by creating pull request with lots of changes
16:45:21 <elf-pavlik> ... every now and then something would get dropped since it didn't apply any more
16:45:34 <elf-pavlik> ... my rebases would loose most of the things, comments
16:45:51 <elf-pavlik> ... unless doing something ood like have branches for each set of comments
16:46:06 <elf-pavlik> ... useful to see which comments caused given change
16:46:19 <timeless> s/loose/lose/
16:46:35 <timeless> virginie: w3c would need something to map github to w3c working method
16:46:40 <timeless> ... we're not there yet
16:46:49 <timeless> ... to dka's comment on having a dashboard, that would be great
16:47:10 <timeless> ... i think this would only be realistically implemented if there's consistency
16:47:17 <timeless> ... we should go to SysTeam
16:47:33 <timeless> ... if we were to develop a dashboard based on Tracker/Github/Bugzilla
16:47:52 <timeless> ... what I had in mind was duplicating Github, but dka said we'd lose the network effect
16:47:55 <LJWatson> LJWatson has joined #ab
16:48:03 <timeless> ... Thanks for coming to the call
16:48:15 <timeless> ... I think we need to look for information/getting people to be involved in getting the information
16:48:21 <elf-pavlik> s/ood/odd/
16:48:22 <timeless> ... one work method is interviewing people
16:48:32 <timeless> ... possibly interviewing w3c domain leaders
16:48:38 <timeless> ... discuss w/ IanJ
16:48:50 <timeless> ... see where there's a lacking/what's a priority
16:48:57 <chaals> q+
16:48:57 <timeless> ... perhaps people could do interviews
16:49:05 <timeless> ... what do people think about interviewing?
16:49:08 <timeless> ack chaals
16:49:17 <timeless> chaals: generally i'm skeptical about interviewing, it's hard to do
16:49:29 <timeless> ... but, "where do they run into problems?:
16:49:32 <timeless> s/:/"/
16:49:41 <timeless> ... my guess is that the information is probably somewhere
16:49:49 <timeless> ... but they don't find it, it takes too long to find what they need
16:50:03 <timeless> ... i think it'd be useful to talk to chairs of groups who do horizontal review
16:50:06 <timeless> ... and industry IGs
16:50:20 <timeless> ... in the last few years there's been a trend to form an IG
16:50:25 <timeless> ... the IG lets them talk to eachother
16:50:41 <timeless> ... they talk to eachother, work out what they want, and then talk to the relevant WG about each REQ/UC
16:50:48 <timeless> ... i think that'd be a good set of people to talk to
16:50:54 <timeless> ... Chairs and Staff Contacts for those groups
16:51:07 <timeless> ... what information do you know/what goes wrong/what do you do
16:51:21 <timeless> ... also AC Reps where their Orgs seem to be involved in several bits of work
16:51:22 <elf-pavlik> in Social IG we try to get going with Liaison TF https://www.w3.org/wiki/Socialig/Liaison_TF
16:51:24 <timeless> Zakim, mute me
16:51:24 <Zakim> timeless should now be muted
16:51:38 <timeless> ... ideally you'd talk to AC Reps who aren't involved in work but want to be
16:51:43 <timeless> ... but it's hard to identify them
16:52:07 <timeless> RRSAgent, draft minutes
16:52:07 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html timeless
16:52:19 <virginie> q?
16:52:44 <timeless> Zakim, take up agenda 4
16:52:44 <Zakim> agendum 4. "action list" taken up [from virginie]
16:52:51 <timeless> virginie: a call for volunteers
16:53:00 <timeless> ... who feels they'd be willing to put more effort into this project?
16:53:06 <elf-pavlik> +1
16:53:10 <timeless> ... is this not something you have time
16:53:10 <virginie> +1
16:53:15 <timeless> ... i'm interested
16:53:16 <jeff> +1
16:53:21 <bkardell_> _1
16:53:24 <bkardell_> +1
16:53:29 <timeless> s/_1//
16:53:37 <chaals> [There are tasks that I think I would take on…]
16:53:51 <timeless> ... i'll try to make a list of the ideas that were listed
16:53:58 <timeless> ... maybe i'll go for a proposal after that
16:54:07 <timeless> ... i'll send a summary to the ML
16:54:11 <timeless> ... i hope you're all subscribed
16:54:12 <virginie> http://lists.w3.org/Archives/Public/public-coord-mechanisms/
16:54:23 <elf-pavlik> i subscribed today
16:54:50 <timeless> ... since i've only been in w3c 3 years, i think interviewing will be helpful for me
16:54:59 <timeless> ... the next step is possibly putting things in the wiki
16:55:02 <timeless> ... is that ok?
16:55:12 <timeless> Zakim, take up agenda 5
16:55:12 <Zakim> agendum 5. "next call (if required)" taken up [from virginie]
16:55:27 <timeless> virginie: another call? or some other preferred working method?
16:55:28 <virginie> working method : mail and wiki
16:55:28 <elf-pavlik> mail & wiki first and then call once when we see need
16:55:31 <jeff> [/me is flexible to work however wants to work]
16:55:40 <Zakim> -elf-pavlik
16:55:48 <timeless> timeless: my neck is hurting, so i'm happy to not have calls
16:56:01 <chaals> [like Jeff… but think we should have meetings only "as necessary"]
16:56:07 <timeless> virginie: my target is to present something in May 2015 to AC reps
16:56:17 <timeless> ... it takes time to gather ideas
16:56:26 <timeless> ... we'll synchronize by mail+wiki
16:56:28 <dka> another call ok
16:56:34 <dka> mail & wiki also ok :)
16:56:45 <timeless> ... thanks for taking the time for this call
16:56:57 <dka> thx virginie!
16:56:59 <Zakim> -dka
16:57:04 <Zakim> -Art_Barstow
16:57:07 <timeless> ... thanks timeless for scribing
16:57:10 <Zakim> -Jeff
16:57:12 <Zakim> -virginie
16:57:13 <timeless> [ Adjourned ]
16:57:13 <Zakim> -Sam
16:57:14 <LJWatson> LJWatson has left #ab
16:57:17 <Zakim> -chaals
16:57:24 <virginie> thansk josh timeless :)
16:57:33 <timeless> s/thansk/thanks/
16:57:34 <elf-pavlik> thank you virginie & timeless !!!
16:57:39 <Zakim> -bkardell_
16:58:06 <virginie> RRSAgent, draft minutes
16:58:06 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html virginie
16:58:46 <virginie> rrsagent, publish minutes
16:58:46 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html virginie
17:01:13 <timeless> s/elf you keep dropping out//
17:01:20 <timeless> s/though timeless seems ot have no problem. :)//
17:01:50 <timeless> s/sorry, I'm muted//
17:02:04 <timeless> s|i//Brian/Topic: Welcome/||
17:02:17 <ArtB> ArtB has left #ab
17:02:20 <timeless> i/Brian Kardell/Topic: Welcome/
17:02:44 <timeless> s|#Scope)|#Scope )|
17:03:23 <timeless> s/<elf-pavlik> .../<timeless> .../g
17:03:28 <Zakim> -[IPcaller]
17:03:36 <timeless> s/<elf-pavlik> timeless:/<timeless> timeless:/
17:03:39 <timeless> RRSAgent, draft minutes
17:03:39 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html timeless
17:04:13 <timeless> s/welcome/Welcome/
17:05:03 <timeless> s/virginie xx/Virginie Galindo, Gemalto/
17:07:07 <Zakim> -timeless
17:07:08 <Zakim> AB_(Project)11:00AM has ended
17:07:08 <Zakim> Attendees were virginie, timeless, dka, elf-pavlik, Jeff, Sam, Art_Barstow, [IPcaller], chaals, bkardell_
17:07:15 <timeless> s/[IPcaller], //
17:07:27 <timeless> trackbot, end meeting
17:07:27 <trackbot> Zakim, list attendees
17:07:27 <Zakim> sorry, trackbot, I don't know what conference this is
17:07:35 <trackbot> RRSAgent, please draft minutes
17:07:35 <RRSAgent> I have made the request to generate http://www.w3.org/2014/12/01-ab-minutes.html trackbot
17:07:36 <trackbot> RRSAgent, bye
17:07:36 <RRSAgent> I see no action items