... Work item groups, try to define items that can be given to a relative newcomer, technical or not-technical
... e.g. Kim takes a documentation task sometimes, as a way to understand
... Keep in mind it will be an iterative process
... Re: Non-technical contributions, aprticularly in the context of work items
... what are the things that can engage a broader group?
... esp with DIDs, which are addressing a large scale beyond technologists
Jonathan Holt: Manu -- as long as you teach me to crank out issues, PR like a steely eyed missile man ✪
Error: (IRC nickname 'justin_r' not recognized)[2019-05-07T16:38:17.388Z] <Justin_R> @manu -- Can't commit to that at the moment. But: you know I'm in favor of things like did:http and vanity DIDs, right? :)
Heather Vescent: I ran a session at IIW about non-technical participation in Standards, that was very productive and I plan to share those notes. I have also made suggestions in a Twitter thread/response to Chaz that was very specific. ✪
... Re: Constructive Collab
... Joe @ IIW began a re-framing conversation. Is it decentralized enough?
... what are the characteristics that we are interested in? Move away from 'religious' tone, stay away from 'sniping'
... Everyone in this group is committed to a particular vision of decentralization
... e.g. we agree we don't want something that can be taken over by FB
... this debate could tear the group apart
... keep in mind, differences of opinion may just be around approach, or definitions of terms
... Re: Code of Conduct. Feels a bit out of date. More udpated guidance is in use at RWoT
Moses Ma: I'd like to talk about doing an NVC communication training for the group ✪
Error: (IRC nickname 'justin_r' not recognized)[2019-05-07T16:42:17.975Z] <Justin_R> @manu -- I'm going to define did:jricher:manu as anyone but you, sorry. It'll be the world's first negative-did. Anyway -- please don't put me down yet, let's cycle back in a couple months when there's something more on the plate and we can see my availability then. Thanks!
Heather Vescent: Respect All participants should strive to treat each other with dignity and respect. Diverse perspectives are critical to our success When listening to input and comments of others, start by assuming the most benign interpretation and the best intention of the speaker. If comment is phrased in a way that might be misinterpreted, ask for clarification of the statement or intent. If the comment is discomforting (or hostile), please reach out [CUT] ✪
... [email of guidelines being read]
Heather Vescent: Collaborate Be open to new ideas and learning from others In moments of strong disagreement, we ask participants to “agree to disagree,” stay focused on the goals of the session or discussion and move on to address shared needs and shared opportunities. ✪
Heather Vescent: Include Follow the “Rule of 1” and the “Rule of n”: When you speak, make 1 point and then let others speak, and when in a group of “n” people, speak “1/nth” of the time. ✪
... To preserve momentum on this work, there's not just a check-off, needs touchpoints
... have the chairs considered a check-in schedule, not every week, but some course correction check-ins
Kim Hamilton Duffy: Chairs intend on-going work, open to some ideas on a check-in. Perhaps at start do it more often. ✪
... add a category to the ongoing agenda items.
... "Does anyone have anything that they wanted to offer?"
Heather Vescent: +1 Kim, for highlighting in the agenda. I think if this is a brief, but weekly reminder will help us integrate this process... but I do not want this to take away from the work we are accomplishing here. ✪
Manu Sporny: +1 To everyting Kim said. Happy this discussion is happening. Approach that the chairs put together is exactly the right way to tackle some of these really difficult issues. ✪
... I think this group is in the forefront at least within W3C, most other W3C focuses only on the technical
... Given our topic we need to focus on these things