#social 2015-09-08

2015-09-08 UTC
bblfish, the_frey, jasnell, jasnell_ and jasnell__ joined the channel
jasnell, jasnell_, elf-pavlik and bblfish joined the channel
#
elf-pavlik
hola #social o/ greetings from Barcelona
jasnell joined the channel
bblfish, melvster1 and cwebber2 joined the channel
#
elf-pavlik
aaronpk, hi o/ do you know some special channel to contact tantek to make sure that he knows that wiki page marks him as chair for today meeting and both Evan and Arnaud sent their regrets? I don't see him in history of today's agenda edits!!! https://www.w3.org/wiki/index.php?title=Socialwg/2015-09-08&action=history
#
ben_thatmustbeme
he mentioned it yestertday about being chair
#
elf-pavlik
ben_thatmustbeme, thanks!
#
melvster1
elf-pavlik: there was something on the agenda with your name re: "approved" user stories?
#
melvster1
do you have any more detail?
#
melvster1
' User Stories -- what are the implications of a story being "accepted"? (per elf-pavlik and Ben Roberts)'
#
melvster1
also btw bi directional links are normally considered a bad idea
#
melvster1
it is possible to use rev and rel
#
melvster1
there are 519 -- +1 "yes, I need it, will implement, worth doing" -- but nowhere near 519 of the voters followed through less than 90% or even closer to 99%
#
melvster1
the voting is not representative
tantek joined the channel
tilgovi joined the channel
#
elf-pavlik
bi directional != defining inverse properties in vocabulary
#
melvster1
ok
#
elf-pavlik
i also plan to explain today alternative to defining as:Follow & as:isFollowing & as:isFollowedBy
#
elf-pavlik
with simple reuse of as:follow (a rdf:Property not a owl:Class!)
#
melvster1
elf-pavlik: got it, im using sioc : follows right now, so does not affect my implementation
#
elf-pavlik
melvster1, you can see my draft for Issue/Pull Request here, will just add diagrams illustrating it https://github.com/w3c-social/social-vocab/wiki/Verbs---owl:Class-vs.-rdf:Property
#
elf-pavlik
needs to focus on finishing this draft before telecon!
#
melvster1
good luck, no strong opinion on that one, already have terms I can reuse in my implementations
#
melvster1
but your argument makes sense
#
elf-pavlik
i would like to avoid creating multiple vocabulary terms where we can simply reuse a single instance of rdf:Property (~ link relation)
VinceW joined the channel
#
elf-pavlik
melvster1, would you like to take a look at version with diagrams? :) https://github.com/w3c-social/social-vocab/wiki/Verbs---owl:Class-vs.-rdf:Property
csarven joined the channel
#
melvster1
elf-pavlik: nice work!
#
elf-pavlik
I get 'Meeting Number Not Found' for 642 112 960
#
csarven
That's not the number
#
csarven
+1617324000
#
csarven
tel:+1-617-324-000
#
elf-pavlik
csarven, can you imagine adding some equivalent examples in JSON-LD or diagrams illustraing how you see modeling it?
#
elf-pavlik
i use iPad WebEx app today
#
elf-pavlik
agenda page says There is a meeting number: 642 112 960
#
sandro
elf, that code worked for me, although I'm the only person in the meeting
#
csarven
Oh sorry.. yes, "meeting number" is 642 112 960.. I presume that's the one you enter in after you dial.
#
csarven
Which is what I'm about to do.
#
elf-pavlik
ok, seems to work now \o/
#
sandro
I'm having insane computer problems. rebooting to new OS. wont be on IRC.
#
cwebber2
dialing in, one sec
#
tantek
dialing in
#
tantek
present+ tantek
#
cwebber2
present+ cwebber2
#
csarven
present+ csarven
#
csarven
present+ sandro
#
elf-pavlik
present+ elf-pavlik
#
aaronpk
present+ aaronpk
#
tantek
trackbot, start meeting
#
trackbot
is preparing a teleconference.
RRSAgent joined the channel
#
trackbot
RRSAgent, make logs public
#
RRSAgent
I have made the request, trackbot
Zakim joined the channel
#
trackbot
Zakim, this will be SOCL
#
Zakim
I do not see a conference matching that name scheduled within the next hour, trackbot
#
trackbot
Meeting: Social Web Working Group Teleconference
#
trackbot
Date: 08 September 2015
#
tantek
zakim, who is here?
#
Zakim
Present: (no one)
#
Zakim
On IRC I see RRSAgent, csarven, tilgovi, tantek, cwebber2, melvster1, elf-pavlik, the_frey, pdurbin, KevinMarks, oshepherd, dwhly, rhiaro, ben_thatmustbeme, Loqi, slvrbckt,
#
Zakim
... bigbluehat, bret, aaronpk, tommorris_, tessierashpool_, wilkie, tsyesika, raucao, ElijahLynn, sandro, trackbot, wseltzer
#
ben_thatmustbeme
lunch ran late, connecting now
#
tantek
present+ tantek
#
csarven
present+ csarven
#
csarven
present+ sandro
#
elf-pavlik
present+ elf-pavlik
#
tantek
zakim, who is here?
#
Zakim
Present: tantek, csarven, sandro, elf-pavlik
#
Zakim
On IRC I see RRSAgent, csarven, tilgovi, tantek, cwebber2, melvster1, elf-pavlik, the_frey, pdurbin, KevinMarks, oshepherd, dwhly, rhiaro, ben_thatmustbeme, Loqi, slvrbckt,
#
Zakim
... bigbluehat, bret, aaronpk, tommorris_, tessierashpool_, wilkie, tsyesika, raucao, ElijahLynn, sandro, trackbot, wseltzer
#
aaronpk
present+ aaronpk
#
rhiaro
Google Voice is telling me 'correct the number', not sure what I'm doing wrong this time
#
rhiaro
sighs
#
elf-pavlik
rhiaro you use +1-617-324-0000 ?
#
tantek
rhiaro I'm using Google Hangouts to make the call. And that number +1-617-324-0000 is correct.
#
rhiaro
worked this time, just weirdness I guess
#
tantek
rhiaro remember to present+ yourself when you're on the call
#
rhiaro
present+ rhiaro
#
tantek
scribe: rhiaro
#
csarven
whistles
#
rhiaro
scribenick: rhiaro
#
elf-pavlik
rhiaro++
#
Loqi
rhiaro has 155 karma
#
rhiaro
TOPIC: Approval of last weeek's minutes
#
rhiaro
tantek: Resolved, approval of minutes
#
rhiaro
TOPIC: F2F at TPppAC
#
rhiaro
's keyboard has developed a sstutter
#
ben_thatmustbeme
present+ ben_thatmustbeme
#
rhiaro
sorry gonnaa have to restart seriously
#
rhiaro
brb 2 mins
#
ben_thatmustbeme
scribenick: ben_thatmustbeme
#
elf-pavlik
ben_thatmustbeme++
#
Loqi
ben_thatmustbeme has 111 karma
#
ben_thatmustbeme
tantek: we discussed the F2F last meeting and were hoping by today we would know if we had enough participants
#
tsyesika
present+ tsyesika
#
ben_thatmustbeme
... looking at the current participants list, I don't see updates from AnnB, or aaronpk
#
ben_thatmustbeme
... aaronpk do you have any new info?
#
ben_thatmustbeme
aaronpk: its still in progress unfortunately
#
ben_thatmustbeme
tantek: anyone else? right now we only have 4 confirmed and rhiaro and csarven are dependant on
#
ben_thatmustbeme
... unless we have some update by the end of the call we are likely going to have to cancel
#
csarven
Sounds reasonable to me.
#
ben_thatmustbeme
... does anyone else have anything to update, I'm hoping to be corrected but it looks like only option
#
rhiaro
is back
#
rhiaro
scribenick: rhiaro
#
cwebber2
I am more likely able to do that
#
rhiaro
tantek: We had discussed having a separate face to face maybe in the US, where more people can make it
#
rhiaro
... Maybe everyone could start thinking about when and where they could do that
#
cwebber2
I'll probably be in boston near the end of the month but that's too soon for everyone I'm sure :)
#
rhiaro
... We would like participation from chairs and everyone who is editing a document, and everyone who is implmeenting
#
rhiaro
... THese are they key people to have at a meeting
#
rhiaro
sandro: I could send an email or a doodle poll to figure out..
#
rhiaro
tantek: If we have enough information to start a doodle poll, go ahead. I don't feel like I have enough. Otherwise send an email.
#
rhiaro
sandro: What more information?
#
elf-pavlik
location first?
#
rhiaro
tantek: Even a range of dates to choose among?
#
rhiaro
sandro: We're supposed to give 8 weeks notice, so assuming we pick a week from today that starts us week of Nov 10th
#
rhiaro
... Presumably we don't want to hold it thanksgiving. That's two weeks before thanksgiving, a week or so after thanksgiving
#
rhiaro
did everything go quiet or is it just me?
#
ben_thatmustbeme
scribenick: ben_thatmustbeme
#
csarven
rhiaro Audio is still okay fo rme.
#
ben_thatmustbeme
tantek: lets action sandro to narrow down possible date ranges for next F2F
#
ben_thatmustbeme
not sure how to action ATM
#
rhiaro
omg, sorry, great time to have a panic attack, laptop
#
tantek
ACTION: sandro narrow down possible date ranges for next F2F
#
trackbot
is creating a new ACTION.
#
RRSAgent
records action 1
#
trackbot
Created ACTION-73 - Narrow down possible date ranges for next f2f [on Sandro Hawke - due 2015-09-15].
#
ben_thatmustbeme
TOPIC: Activity Streams 2.0
#
tantek
issue 1: "as:Like (an rdfs:Class) or as:like (an rdf:Property)?"
#
trackbot
doesn't understand that ISSUE command.
#
ben_thatmustbeme
tantek: we have a couple of issues raised by elf-pavlik, before we deep dive into these on telconf we should make sure we have people effected by these on the telcon or don't waste time on this telcon
#
Zakim
sees csarven on the speaker queue
#
ben_thatmustbeme
... are there any implementors here impacted by this issue on the telconf?
#
csarven
Sort of..
#
elf-pavlik
melvster1 ?
#
ben_thatmustbeme
... if its only elf-pavlik being effected, not sure its best to discuss here
#
ben_thatmustbeme
... I looked at the information on this issue, but did not see any link to any implementation actually blocked by the issue. I would recommend that you include links to that issue
#
tantek
next issue: "Represent bidirectional connections "
#
ben_thatmustbeme
... moving on to the next issue
#
melvster1
already implemented ... not impacted ...
#
ben_thatmustbeme
... I don't understand, this issue says closed
#
ben_thatmustbeme
... is there a different issue relating to this elf?
#
ben_thatmustbeme
elf-pavlik: no, i don't see this issue as resolved, james just closed the issue
#
melvster1
isnt using AS2.0 for this, using ontologi.es/likes
#
ben_thatmustbeme
tantek: I think that sounds like a different issue should be pointed to or re-opened.
#
ben_thatmustbeme
elf-pavlik: I will propose for next week that we need to figure out workflow for github issues
#
cwebber2
I'm not enough in rdf-land to be sure I'm impacted
#
ben_thatmustbeme
tantek: same question as before applies, who on the call, is impacted by this issue?
#
elf-pavlik
q+ re: implementers on the call
#
Zakim
sees csarven, elf-pavlik on the speaker queue
#
rhiaro
is back, shall I try again ben_thatmustbeme?
#
Zakim
sees csarven, elf-pavlik on the speaker queue
#
tantek
ack csarven
#
Zakim
sees elf-pavlik on the speaker queue
#
ben_thatmustbeme
... I think this should be iterated on asyncronously until there are more implementors on the call
#
ben_thatmustbeme
scribenick rhiaro
#
rhiaro
scarven: first of all, unclear on issues, lots of crossreferencing going on across eamils and github
#
rhiaro
s/scarven/csarven
#
rhiaro
... I think what elf is trying to raise is important for AS2
#
rhiaro
ben_thatmustbeme can you take over
#
rhiaro
my keyboard is freaking out still
#
rhiaro
sorry
#
ben_thatmustbeme
scribenick: ben_thatmustbeme
#
elf-pavlik
i'll create new issue for it on gh!
#
ben_thatmustbeme
tantek: thats why i was asking if there is any implementors on the call, since James is not here, it doesn't really make sense to discuss
#
ben_thatmustbeme
... I think this should be clarified as to what part of the spec actually has an issue, the discussion is more conceptual and less concrete
#
ben_thatmustbeme
elf-pavlik: I will try to clarify for next week and hopefully james will be on the call
#
csarven
More about the model
#
rhiaro
I tried to figure out some of this stuff, but I think definitely better understood by actual implementation. Be good to see examples of options implemented.
#
Zakim
sees elf-pavlik on the speaker queue
#
ben_thatmustbeme
tantek: specifically i'd recommend you try to get much clearer on what specific parts of the spec are effected
#
melvster1
has already implemented likes, AS2.0 and MF2 didnt meet needs, so used ontologi.es
#
ben_thatmustbeme
elf-pavlik: I wanted to clarify the approach of asking for implementors on the call since only james implements a library. I think we can discuss the approach before we implement
csarven joined the channel
#
csarven
present+ csarven
#
ben_thatmustbeme
... specifically this deals with how we model, i don't think we need to have implementors on the call
#
ben_thatmustbeme
tantek: they could be implementING, don't have to have implmentED. so its who feels this would effect them
#
ben_thatmustbeme
topic: Social API
#
tantek
"User Stories -- what are the implications of a story being "accepted"? "
#
Zakim
sees no one on the speaker queue
#
ben_thatmustbeme
tantek: question was raised as to what are the implications of a story being "accepted"
#
ben_thatmustbeme
tantek: amy are you back on to take over as scribe?
#
ben_thatmustbeme
I'm willing to let elf-pavlik introduce
#
melvster1
FYI: there 519 +1 votes -- "will implement"
#
ben_thatmustbeme
elf-pavlik: we have had back and forth on what are the consequences of accepting a user story
#
rhiaro
sorry, changed to phone, should be okay now
#
ben_thatmustbeme
tantek: that should be documented at the social api page
#
rhiaro
scribenick: rhiaro
#
ben_thatmustbeme
thanks rhiaro
#
rhiaro
tantek: We were talking about what should be in the social api. We had research on what proprietary social APIs do, all on the wiki
#
rhiaro
... Evan then proposed a list of social api requirements, based on a union of all those proprietary APIs
#
rhiaro
... The group decided that was far beyond what we needed to do for a v1
#
elf-pavlik
link to minutes?
#
rhiaro
... Instead of using a list of derived reqs from existing sites like that, we wanted to base the requirements on user stories that the group was interested in solving
#
rhiaro
... That led to the proposal of user stories, and voting on them
#
rhiaro
... After that ben_thatmustbeme sorted them by different clusters
#
ben_thatmustbeme
elf-pavlik, i have all the minutes downloaded, i can grep across them for that week to link you to probably
#
ben_thatmustbeme
after the meeting that is
#
elf-pavlik
thanks ben_thatmustbeme
#
rhiaro
... After that, or even before that, we agreed that swat0 was one of our foundational user stories
#
rhiaro
... Then we agreed to accept the user stories that were all +1
#
ben_thatmustbeme
not at this computer
#
rhiaro
... Leaving the rest to the IG to attempt to resolve these issues on
hhalpin joined the channel
#
hhalpin
everyone, just got out of the dentists
#
rhiaro
... The implication there being that the purpose of the user stories is to drive rquireemnts for the API, so the accepted user stories would be used to dtermine those requirements
#
elf-pavlik
hhalpin
#
rhiaro
... Maybe that's the next step, to say given these user stories what does that say about reqs for API
#
rhiaro
... That's how we got to where we are
#
rhiaro
<rhiaro> I tried the reqs from user stories doc
#
hhalpin
I'll join the call but can't speak due to my entire mouth being numb for the next hour or two, but happy to chat via IRC - hope things have been going well!
#
ben_thatmustbeme
agrees that should probably be on the site, or at least linked anywhere there is a list of "approved" user stories
#
rhiaro
sandro: We should avoid being legalistic about it. Anyone designing an api should have in mind the things that everyone seems to want it to do
#
melvster1
sandro++
#
rhiaro
... Not an agreement that we will only consider things that will only meet all of these criteria, and have some kind of formal thing
#
Loqi
sandro has 23 karma
#
ben_thatmustbeme
we should probably be written on the site, or at least linked anywhere there is a list of "approved" user stories
#
rhiaro
... Makes people panic and argue in a way that doesn't reflect reality
#
rhiaro
... We should keep it more descriptive than prescriptive
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro
... But that's my perspective, not always how people want to do things
#
rhiaro
tantek: I think your perspective is accurate
#
Loqi
sandro has 24 karma
#
elf-pavlik
sandro++
#
Loqi
sandro has 25 karma
#
rhiaro
tantek: I think the user stories list and voting was an attempt to narrow absolute list and requirements
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro
... These are good inputs to what a social api SHOULD have rather than MUST have is a good interpretation
#
tantek
ack elf-pavlik
#
Zakim
sees no one on the speaker queue
#
rhiaro
... That's my understanding as to how we got here
#
rhiaro
elf-pavlik: I get frustrated that you and sandro see differently. You said it's to narrow the absolute requirement, and sandro said it's more about getting general idea of what people want, not absolute
#
rhiaro
... So we don't look for this absolute requirement or hard line, but what we can expect others to give attention to, and maybe we should focus furst on things that are of common interest, and not feel discouraged about pursuing things that are less of common interest
#
rhiaro
... We should document this, and why do we have a formal process of accepting and not accepting, seems we have a different understanding
#
rhiaro
tantek: your point about prioritising what seems to be common wants is a good one
#
rhiaro
... Certainly the tone in the group has shifted from the earlier days when we were trying to require all of these things
#
rhiaro
... Now people are implementing it's clear that there's a lot of work to be done
#
rhiaro
... Totally fine to move in that direction. What sandro described makes sense, without trying to compel what goes into a draft
#
rhiaro
... The more we canminimise the MUSTs the better
#
hhalpin
+1 should, be we need interop over a small set of minimal functionality
#
rhiaro
... Makes it easier to write a spec, test suite, go to CR
#
hhalpin
for the CR test-suite
#
rhiaro
elf-pavlike: Maybe we don't need this process for accepting user stories?
#
rhiaro
tantek: We need to know what anyone wants
#
melvster1
people are not implementing ... there were 519 +1s meaning "will implement" ... but only a small fraction of those voters followed through ...
#
rhiaro
sandro: I lean against a formal process. We can base it on observation of votes. People can change their votes if priorities change
#
rhiaro
tantek: Does anyone know what melvin means by 519 +1s?
#
rhiaro
... I don't udnerstand what that's about
#
elf-pavlik
melvster1 on call?
#
melvster1
the user story voting, I counted the +1s
#
rhiaro
ben_thatmustbeme: I'm guessing he jsut counted all the +1s between all the votes?
#
rhiaro
... Because it was originally that +1 was labelled as 'plan to implement'
#
rhiaro
tantek: THat's a misinterpretation
#
rhiaro
... just because someone +1ed doesn't mean they were planning to implement
#
melvster1
ok, it's on the page still
#
rhiaro
... Some people noted they would implement, but +1 doesn't mean that
#
rhiaro
... Going to treat that as misreading documentation
#
aaronpk
melvster1, what are you using to determine whether someone is implementing? I am implementing things and still plan to implement things that I have not started yet, so not really sure what point you're trying to make
#
melvster1
+1 "yes, I need it, will implement, worth doing"
#
rhiaro
tantek: Whether user stories are useful to accept or not, it's to help understand what's common interests
#
rhiaro
... Just because we're moving away from MUST to SHOULD doesn't mean we throw everything out
#
rhiaro
... If you can't describe some api functionality in terms of user story, probably means you shouldn't have it
#
rhiaro
... To stop draft ballooning out of control with every feature request
#
ben_thatmustbeme
melvster1, probably you should read those ,'s as ORs
#
rhiaro
elf-pavlik: Will we continue process of trying to formally +1 and accept? Or keep it around as a reference but no more formalising?
#
rhiaro
tantek: Depends on what desires the different impelentors have?
#
rhiaro
... Are there user stories that people are implementing that go beyond the scope of what is already approved or not?
#
rhiaro
... As I hear, even the user storeis that are accepted are a lot of work, so we don't need more
#
rhiaro
... I strongly suggest that if you're implementing something you focus on what's already been approved, instead of trying to add more work
#
rhiaro
... When someone is willing to declare victory on implementing all the accepted user stories, we can have this discussion again
#
rhiaro
melvster1, I read the ',' in "yes, I need..." as OR rather than AND
#
Zakim
sees no one on the speaker queue
#
rhiaro
tantek: ben, anything to add about implications of user stories?
#
rhiaro
ben_thatmustbeme: I guess not, mostly covered
#
melvster1
I think the implemented user stories should be a strong input : https://github.com/w3c-social/social-ucr
#
rhiaro
... A lot of this came out of people trying to implement those exactly. We need to make it known that people don't need to implement every exact thing. Not specs, just reference for guiding us.
#
rhiaro
tantek: What do people think about that? Implementors should take the user stories as useful functionality, but not a precise step by step requirement
#
Zakim
sees no one on the speaker queue
#
rhiaro
ben_thatmustbeme: exactly
#
rhiaro
sandro: I guess I wonder why that is?
#
elf-pavlik
who makes noise?
#
elf-pavlik
ben_thatmustbeme ?
#
tantek
zakim, who is noisy?
#
Zakim
I am sorry, tantek; I don't have the necessary resources to track talkers right now
#
rhiaro
sandro: If you ahve 3 different implementors demoing user stories, and two do it one way and one is different, that seems like it's going to cause confusion and problems
#
rhiaro
ben_thatmustbeme: The problem is that we didn't read these user stories as exact specifications. If I went back and voted on them that way it woudl be different. We ended up arguing about 'inbox' terminology
#
rhiaro
sandro: Terminology doesn't affect code, so terminology aside, what else?
#
rhiaro
tantek: I don't think we can avoid people misinterpreting a user stories
#
rhiaro
ben_thatmustbeme: I didn't go through these thinking of them as specs. The functionality of being able to like something is different to having a button on a site below a post
#
rhiaro
... If we start reading them as technical documents, you have to follow exactly what they say
#
rhiaro
... It's important to tell people that's not what these are, because they were not gone over that way
#
rhiaro
... We should not say this is approved, this is perfect, you should implement exactly like this
#
rhiaro
... that may not make sense
#
rhiaro
sandro: If we say that these are not to be understood precisely, we've muddied the waters without gving any new guidence
#
rhiaro
tantek: not if that's hwo we all interpret them
#
elf-pavlik
q+ re: IG ambition to 'clarify' those stories and need for it
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro
... If the folks that voted on them initially did not interpret them with thta precision, it does not seem reasonable to assert that precision now
#
hhalpin
I imagine the 'precision' will come out in the test-suite, right?
#
rhiaro
sandro: I agree with that, just trying to find something more useful than handwaving around it
#
rhiaro
... My proposal would be that anyone that thinks this goes back to change their plus ones to clarify this
#
elf-pavlik
ben_thatmustbeme can you please mute when you don't speak?
#
hhalpin
It seems this 'terminology' issue might be making a mountain out of a molehill.
#
rhiaro
... I'm fine with saying terminololy everywhere is not rigid
#
csarven
q+ re: too much confusion over semantics right now. Without implementation , it is hard to tell
#
Zakim
sees elf-pavlik, csarven on the speaker queue
#
rhiaro
... But other things. Seems more useful than just saying don't take any of this stuff literally
#
elf-pavlik
ben_thatmustbeme thx!
#
rhiaro
tantek: Let's at least put that proposal... let the user stories be interpreted as stheir functionality, not their terminology
#
rhiaro
sandro: I'm cool with that
#
rhiaro
tantek: Does that reflect at least part of your concern, ben?
#
rhiaro
ben_thatmustbeme: certainly
#
rhiaro
tantek: any objections?
#
Zakim
sees elf-pavlik, csarven on the speaker queue
#
rhiaro
tantek: if you have objections, -1 in IRC
#
rhiaro
... This is a specific proposal
#
elf-pavlik
rhiaro can you retype it?
#
rhiaro
... Then we'll go to the queue
#
rhiaro
tantek: Let's at least put that proposal... let the user stories be interpreted as stheir functionality, not their terminology
#
elf-pavlik
PROPOSAL
#
cwebber2
seems good
#
rhiaro
PROPOSAL: User stories are interpreted as their functionality, not by terminology
#
rhiaro
sandro: +1
#
rhiaro
RESOLVED: User stories are interpreted as their functionality, not by terminology
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro
tantek: Hopefully thsi will resolve literal interpretation problems in future
#
rhiaro
tantek: Next issue is, inbox user story was overinterpreted
#
rhiaro
... I don't think we can avoid that, people are going to interpret things however they want, people are looking for guidence wherever they can get it
#
rhiaro
... Okay if osmeone wants to literally implement a user story, but not okay to demand others do so
#
rhiaro
... I believe saying the functionality is the focus makes that clear
#
rhiaro
... To avoid these arguements by literal text in the future
#
Zakim
sees elf-pavlik on the speaker queue
#
rhiaro
ben_thatmustbeme: I think that'll take care of it
#
tantek
ack elf-pavlik
#
Zakim
elf-pavlik, you wanted to discuss IG ambition to 'clarify' those stories and need for it
#
Zakim
sees no one on the speaker queue
#
rhiaro
elf-pavlik: I would like to see if we give feedback to the interest group, who I hope will get more active now
#
rhiaro
... They need to know if they should put effort into resolving issues to get them accepted
#
rhiaro
... If we want to continue process of formal approval and have IG put effort into clarifying those stories so they can be formally approved, we still need to write down clear criteria of what acceptance implies
#
rhiaro
... If it's just for understanding each other, we don't need all this strong effort into formal acceptance process, with people putting effort from IG into this
#
rhiaro
tantek: THere have been several times people have stated that it's useful to have a set of user stories that are accepted to prioritise common interests
#
rhiaro
... Many people have indicated why that's useful
#
rhiaro
... As far as trying to provide criteria to the IG, I don't see why that's necessary in terms of what the user stories are used for
#
rhiaro
... The request of the IG is to go through 0s and -1s on user stories and resolve them
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
rhiaro
... That is to contact people objecting or being neutral about a user story, finding out why, seeing if it's possibe to resolve, ideally with original author of user story
#
rhiaro
... It doesn't need anything more than that. Focus on those votes and those people, resolve them one by one.
#
rhiaro
... Anyone here from the IG to take that action?
#
rhiaro
... AnnB is not here
#
rhiaro
... Anyone an active participant in IG to take that action?
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
rhiaro
<rhiaro> When the IG did try to do thsi a while back, WG members didn't respond well
melvster joined the channel
#
rhiaro
tantek: Not hearing anyone step forward to take this action to the IG, so going to postpone. elf, you can try bringing this up again in the future. Unless we get IG participatns in the WG, we're not going to get progress on this
#
rhiaro
... If you want to drive that, you need to drive it in the IG yourself
#
Zakim
sees ben_thatmustbeme on the speaker queue
#
tantek
ack ben_thatmustbeme
#
Zakim
sees no one on the speaker queue
#
rhiaro
ben_thatmustbeme: Going to suggest that maybe the idea of having a formal approve/deny might be easier to do just as once we all agree on it, everyone is +1, then it's implicitly approved
#
elf-pavlik
+1 ben_thatmustbeme
#
rhiaro
... This takes away any work on us to waste conference call time to put forward to proposals to approve
#
rhiaro
... If everyone agrees they see it as useful, it's implicitly accepted
#
rhiaro
tantek: appreciate the optimism. If those vote changes occur based on changes to user stories, I think it's reasonable to have to raise those user stories to everyone else who might have voted, to make sure that their votes don't change
#
rhiaro
... So we're not specifically asking everyone to go vote again, just trying to resolve non +1 votes with edits
#
rhiaro
... With the optimistic assumption that everyone who voted +1 won't change their vote
#
rhiaro
... But we have to challenge that assumption by bringing it up in a telecon to check for objections
#
rhiaro
... Don't want to edit user stories from underneath people without them being notified
#
Zakim
sees no one on the speaker queue
#
rhiaro
TOPIC: Tracking of actions and issues
#
rhiaro
tantek: 0 raised issues
#
rhiaro
... 0 pending review issues
#
rhiaro
... 0 pending review actions either
#
rhiaro
... Next telecon is next week
#
Zakim
sees no one on the speaker queue
#
rhiaro
... 15th, Arnaud chairing
#
rhiaro
... Any other issues that anyone wants to raise in last 2 minutes?
#
Zakim
sees no one on the speaker queue
#
rhiaro
... We're cancelling the face to face at tpac unfortunately as people can't make it
#
rhiaro
... We'll follow up with a doodle poll to figure out when we can meet next
#
elf-pavlik
tantek++
#
rhiaro
... Thanks everyone
#
Loqi
tantek has 237 karma
#
elf-pavlik
thanks rhiaro!!!
#
tantek
rhiaro++ for minuting
#
Loqi
tantek has 238 karma
#
Loqi
rhiaro has 156 karma
#
Loqi
rhiaro has 157 karma
#
rhiaro
RRSAgent, make minutes public
#
RRSAgent
I'm logging. I don't understand 'make minutes public', rhiaro. Try /msg RRSAgent help
#
rhiaro
I swear this thing changes every week.
#
aaronpk
Loqi: tell RRSAgent to make the minutes
#
csarven
"Let my <del>people</del><ins>minutes</ins> go"
#
rhiaro
Zakim, make minutes public
#
Zakim
I don't understand 'make minutes public', rhiaro
#
rhiaro
Anyone, make minutes public??
#
rhiaro
RRSAgent, help
#
RRSAgent
More detailed help is available in http://www.w3.org/2002/03/RRSAgent
#
RRSAgent
Some of the commands I know are:
#
RRSAgent
silence - Stop logging (also: stop, off, ...)
#
RRSAgent
listen - Start logging (also: start, on, ...)
#
RRSAgent
excuse us - Leave the channel (also: bye)
#
rhiaro
oops, sorry
#
RRSAgent
grep [-i] [first-last|max] <perl regex> - Search the logs
#
RRSAgent
e.g. grep foo, grep 5 bar, grep -i things [case independent]
#
RRSAgent
append |mail EMAIL-ADDRESS to email results instead of printing
#
RRSAgent
bookmark - Give the URI of the current log
#
RRSAgent
show action items - give a list of ACTION: entries
#
rhiaro
RRSAgent, shut up
#
RRSAgent
drop action n - remove entry [n] from the list of action items
#
RRSAgent
I respond to 'RRSAgent, command' in public and '/msg RRSAgent command' in private
#
RRSAgent
Logging Policy: All public output is logged if I am listening except for
#
RRSAgent
"action" messages (messages sent with the '/me' command) and
#
RRSAgent
any lines starting [off]. All commands to me are logged.
#
RRSAgent
My public output is logged but these lines are not searchable.
#
RRSAgent
Do RRSAgent, adminhelp for help on administrative commands
#
RRSAgent
is not logging
#
wilkie
RRSAgent, please generate the minutes
#
RRSAgent
I have made the request to generate http://www.w3.org/2015/09/08-social-minutes.html wilkie
#
rhiaro
THANKS wilkie!!!
#
rhiaro
wilkie++
#
Loqi
wilkie has 19 karma
#
rhiaro
the bot whisperer
#
rhiaro
RRSAgent, do it faster
#
RRSAgent
I'm not logging. I don't understand 'do it faster', rhiaro. Try /msg RRSAgent help
#
rhiaro
Thanks, RRSAgent
#
rhiaro
cwebber2, were you on that call?
#
rhiaro
You're not in the 'present', I'll add you, just want to check
#
cwebber2
rhiaro: I was on the call
#
rhiaro
okie dokie
#
ben_thatmustbeme
elf-pavlik: a quick search turned up "stories" first getting talked about on 2015-02-03
#
ben_thatmustbeme
at least in any significant amount
#
ben_thatmustbeme
SWAT0 was first mentioned 2014-09-23-minutes
#
cwebber2
SQL AST mapped to RDF?
#
cwebber2
I bet elf-pavlik either finds it interesting or knows more about this ;)
Arnaud joined the channel
#
Zakim
excuses himself; his presence no longer seems to be needed
#
RRSAgent
excuses himself; his presence no longer seems to be needed
#
tantek
FYI I've updated https://www.w3.org/wiki/Socialwg#sched with guesses / explicit notes of "unknown" per the ACTION item assigned to me as part of our Charter Update https://www.w3.org/wiki/Socialwg#sched
#
tantek
(oops didn't mean to paste the link twice)
#
tantek
continues to edit our home page wiki and notice other things out of date
#
tantek
is anyone in touch with Erik Wilde? according to our home page, he runs https://twitter.com/SocialWebWG - but he left the WG two months ago.
jasnell and the_frey joined the channel
the_frey joined the channel