#social 2015-01-29

2015-01-29 UTC
jasnell, tantek, KevinMarks, bblfish, bblfish_, jaywink, elf-pavlik, the_frey, shepazu, danbri, the_frey_, elf-pavlik_, jasnell_, jasnell__, jasnel___, jasne____, AnnB and harry joined the channel
#
aaronpk
just booked my flights to the F2F meeting!
#
tantek
aaronpk++ yeah!
#
Loqi
aaronpk has 676 karma
#
tantek
reminder all: please add yourself to https://www.w3.org/wiki/Socialwg/2015-03-17#Participation if you plan on participating in the March f2f
jasnell, the_frey, jasnell__, melvster, shepazu and harry joined the channel
#
AnnB
I'd appreciate it if someone would give me guidance per my mail http://lists.w3.org/Archives/Public/public-socialweb/2015Jan/0083.html
#
AnnB
(sorry it comes through plain text so garbled)
#
AnnB
see attachment
#
AnnB
also, in meeting Tuesday, I asked what should the IG focus be, right now ...
#
AnnB
someone (Evan?) said, make a 'use case check list' .. put our requirements in list format
#
AnnB
I need to better understand that
shepazu joined the channel
#
tantek
AnnB - yes Evan said that as a summary request for each use-case. I disagreed strongly.
#
tantek
I don't think checklists are useful when doing research like that - because checklists tend to be more theoretical - unbound to specific needs.
#
tantek
Better (as discussed on the call) is to provide tweetable summary user-stories
#
AnnB
I guess I need to re-read the IRC log
#
tantek
similar to the what SWAT0 has at the very top
#
AnnB
right, I remember that bit
#
tantek
and very easily / quickly readable *brief* summary of *specific* steps taken by people
#
tantek
that's the key
#
tantek
a use-case summary needs all of those: short/brief, *ordered* series of *specific* *actions* taken by *users* in the use-case.
#
AnnB
I thought I understood that whole discussion, but now, to put it into practice, I found myself unclear
#
tantek
hence the specific *good* example of the SWAT0 summary at the top of its page
#
tantek
every other use-case summary should be measured against that
shepazu and melvster joined the channel
#
AnnB
which part of that do you describe as "tweetable" short? the top steps 1-6?
#
tantek
note the linked post from the top of that summary
#
tantek
slightly longer than tweetable originally: https://twitter.com/t/status/18872957522
#
Loqi
@t :: we (@daveman692 @evanpro + I) just came up with a #fsws Social Web Acid Test (SWAT) v0 draft. full description, ... http://ttk.me/t46o3
#
tantek
let me see if I can shorten it even further
#
tantek
got it
the_frey joined the channel
#
Loqi
@t :: SWAT0 A posts+tags mobile photo of B B photo notified C(follows A) sees it; replies A&B comment notified Prev: http://tantek.com/2015/029/t1/swat0-posts-tags-mobile-photo-comment
#
AnnB
very succinct, Tantek
#
AnnB
verging on inscrutable
#
AnnB
but, OK
#
tantek
AnnB - and that's the point, if a use-case isn't distillable down to a summary of steps that's tweetable, it's too complex a use-case, pursue simpler use-cases first
#
AnnB
yer the bees knees, T
#
AnnB
(I had to go look up origins of that phrase .. similar to "cat's meow" or "cat's pajamas" ... hehe)
#
tantek
AnnB - feel free to challeng the IG with both that statement "it's too complex a use-case, pursue simpler use-cases first" and "a use-case summary needs all of those: short/brief, *ordered* series of *specific* *actions* taken by *users* in the use-case."
#
AnnB
my plan is to take one of the existing use cases / scenario -- and try to "tweet-ify" it myself
#
AnnB
then, use that experience as example
#
AnnB
was just going to SocIG profile scenarios page .. but might actually have to go for fast walk in sun first!
#
tantek
AnnB I suggest attempting with what you think is the *simplest* use-case that the IG has documented so far.
#
AnnB
ok
caseorganic, danbri and AnnB joined the channel