Re: Avoiding DID-landia at RWoT8

Agreed. Speaking as a producer and facilitator of RWOT, we'll almost certainly establish some sort of limit on group size and work with teams to break up into smaller, more responsive teams.

So, think about what smaller issues you might be able to tackle, as Manu suggests. During ideation and selection, we'll tease out which have good support for separate issues. Also, I think we can invest more time in clarification & feedback at the end of the day, rather than just a report-out. This will let other DID supporters contribute, not just get an update.

I'll bring these issues up on the agenda planning meeting we have today.

-j

On Wed, Feb 20, 2019, at 8:16 AM, Manu Sporny wrote:
> Hi all,
> 
> A large chunk of us are going to be at Rebooting the Web of Trust 8 in
> Barcelona next week. During RWoT in Boston, a lot of us ended up
> gravitating toward the DID spec discussions which ended up being a very
> large group of 18+ people.
> 
> Large groups mean that people don't get to speak and collaborate as much
> as they should, and different work products don't get moved forward (or
> don't happen at all)... because, who wants to miss the fireworks! :P
> 
> So, instead of DID-landia, I suggest we focus on small pockets of people
> working on DID-related things. Here's a proposal for the sorts of groups
> we could create:
> 
> * DID Use Cases, where the focus is on not adding new use cases, but
>  rapidly refining the excellent work that Joe has put into the
>  current DID Use Cases document to prepare it for a DID Working Group.
> 
> * DID Editorial Issues that make the spec difficult to read/understand.
>  This is the group that would most likely consist of the current
>  Editors making editorial changes to clean the flow of the spec up.
> 
> * DID Document Features (current/new ones) that need use cases, debate,
>  and spec text hammering before a PR can be created. This would be ABNF
>  changes for services, DID namespaces, etc.
> 
> Other DID-related things:
> 
> * DID Resolver -- making headway on that spec?
> 
> * DID Auth -- what's new? MikeJ's paper on OIDC+DIDs seemed interesting
>  and would fit in a group like this.
> 
> * Two-factor integration? FIDO? BOPS? etc.?
> 
> We may want to set aside 2-3 hours in the last day for a report out from
> all the groups that did DID-related stuff so we can at least sync so
> that folks don't feel like they missed out on stuff or didn't have their
> concerns heard.
> 
> Thoughts?
> 
> -- manu
> 
> -- 
> Manu Sporny (skype: msporny, twitter: manusporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Veres One Decentralized Identifier Blockchain Launches
> https://tinyurl.com/veres-one-launches
> 
> 

--
Joe Andrieu, PMP
joe@joeandrieu.com
+1(805)705-8651
http://blog.joeandrieu.com

--a04691f18d4c4a36a8701878b5ab6c91
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Agreed. Speaking as a producer and facilitator of RWOT, we=
'll almost certainly establish some sort of limit on group size and work=
 with teams to break up into smaller, more responsive teams.<br></div><d=
iv style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Aria=
l;">So, think about what smaller issues you might be able to tackle, as =
Manu suggests. During ideation and selection, we'll tease out which have=
 good support for separate issues. Also, I think we can invest more time=
 in clarification &amp; feedback at the end of the day, rather than just=
 a report-out. This will let other DID supporters contribute, not just g=
et an update.<br></div><div style=3D"font-family:Arial;"><br></div><div =
style=3D"font-family:Arial;">I'll bring these issues up on the agenda pl=
anning meeting we have today.<br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;">-j</div><div style=3D"font-=
family:Arial;"><br></div><div style=3D"font-family:Arial;">On Wed, Feb 2=
0, 2019, at 8:16 AM, Manu Sporny wrote:<br></div><blockquote type=3D"cit=
e" id=3D"fastmail-quoted"><div style=3D"font-family:Arial;">Hi all,<br><=
/div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fami=
ly:Arial;">A large chunk of us are going to be at Rebooting the Web of T=
rust 8 in<br></div><div style=3D"font-family:Arial;">Barcelona next week=
. During RWoT in Boston, a lot of us ended up<br></div><div style=3D"fon=
t-family:Arial;">gravitating toward the DID spec discussions which ended=
 up being a very<br></div><div style=3D"font-family:Arial;">large group =
of 18+ people.<br></div><div style=3D"font-family:Arial;"><br></div><div=
 style=3D"font-family:Arial;">Large groups mean that people don't get to=
 speak and collaborate as much<br></div><div style=3D"font-family:Arial;=
">as they should, and different work products don't get moved forward (o=
r<br></div><div style=3D"font-family:Arial;">don't happen at all)... bec=
ause, who wants to miss the fireworks! :P<br></div><div style=3D"font-fa=
mily:Arial;"><br></div><div style=3D"font-family:Arial;">So, instead of =
DID-landia, I suggest we focus on small pockets of people<br></div><div =
style=3D"font-family:Arial;">working on DID-related things. Here's a pro=
posal for the sorts of groups<br></div><div style=3D"font-family:Arial;"=
>we could create:<br></div><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">* DID Use Cases, where the focus is on =
not adding new use cases, but<br></div><div style=3D"font-family:Arial;"=
>&nbsp; rapidly refining the excellent work that Joe has put into the<br=
></div><div style=3D"font-family:Arial;">&nbsp; current DID Use Cases do=
cument to prepare it for a DID Working Group.<br></div><div style=3D"fon=
t-family:Arial;"><br></div><div style=3D"font-family:Arial;">* DID Edito=
rial Issues that make the spec difficult to read/understand.<br></div><d=
iv style=3D"font-family:Arial;">&nbsp; This is the group that would most=
 likely consist of the current<br></div><div style=3D"font-family:Arial;=
">&nbsp; Editors making editorial changes to clean the flow of the spec =
up.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"f=
ont-family:Arial;">* DID Document Features (current/new ones) that need =
use cases, debate,<br></div><div style=3D"font-family:Arial;">&nbsp; and=
 spec text hammering before a PR can be created. This would be ABNF<br><=
/div><div style=3D"font-family:Arial;">&nbsp; changes for services, DID =
namespaces, etc.<br></div><div style=3D"font-family:Arial;"><br></div><d=
iv style=3D"font-family:Arial;">Other DID-related things:<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>* DID Resolver -- making headway on that spec?<br></div><div style=3D"f=
ont-family:Arial;"><br></div><div style=3D"font-family:Arial;">* DID Aut=
h -- what's new? MikeJ's paper on OIDC+DIDs seemed interesting<br></div>=
<div style=3D"font-family:Arial;">&nbsp; and would fit in a group like t=
his.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"=
font-family:Arial;">* Two-factor integration? FIDO? BOPS? etc.?<br></div=
><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:A=
rial;">We may want to set aside 2-3 hours in the last day for a report o=
ut from<br></div><div style=3D"font-family:Arial;">all the groups that d=
id DID-related stuff so we can at least sync so<br></div><div style=3D"f=
ont-family:Arial;">that folks don't feel like they missed out on stuff o=
r didn't have their<br></div><div style=3D"font-family:Arial;">concerns =
heard.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">Thoughts?<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">-- manu<br></div><div styl=
e=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">--&=
nbsp;<br></div><div style=3D"font-family:Arial;">Manu Sporny (skype: msp=
orny, twitter: manusporny)<br></div><div style=3D"font-family:Arial;">Fo=
under/CEO - Digital Bazaar, Inc.<br></div><div style=3D"font-family:Aria=
l;">blog: Veres One Decentralized Identifier Blockchain Launches<br></di=
v><div style=3D"font-family:Arial;">https://tinyurl.com/veres-one-launch=
es<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"fo=
nt-family:Arial;"><br></div></blockquote><div style=3D"font-family:Arial=
;"><br></div><div id=3D"sig49380817"><div class=3D"signature">--<br></di=
v><div class=3D"signature">Joe Andrieu, PMP<br></div><div class=3D"signa=
ture"><a href=3D"mailto:joe@joeandrieu.com">joe@joeandrieu.com</a><br></=
div><div class=3D"signature">+1(805)705-8651<br></div><div class=3D"sign=
ature">http://blog.joeandrieu.com<br></div></div><div style=3D"font-fami=
ly:Arial;"><br></div></body></html>
--a04691f18d4c4a36a8701878b5ab6c91--

Received on Wednesday, 20 February 2019 16:46:16 UTC