Re: Let's meet. Was: Re: Should the specs be forked and maintained elsewhere?

I don't like the part where people have to show video, even for a short while. If the reason is identity verification, I'm not sure why a proof of identity is an issue. Forced microphone is also a potential issue - just let people acknowledge themselves at the start of the meeting in whatever form they like.

We will know people by their work as time goes on. No one is likely to impersonate a member of this list just to volunteer on activitypub and, if so, video won't solve that.

For name, preferred or given name is much better than a handle/nickname, IMO. Attribution in W3C docs is not by handle. Also, I think encouraging nicknames in this context will get messy and not align well with email collaboration.

I assume item #6 is a joke? 

Live transcription is very difficult to get right in my experience running online events, without hiring a professional. The plugins for OBS etc. are terrible. Open AI improves this dramatically, but I don't know if folks want their conversations fed into a data set for a language learning model.

Meeting minutes should probably suffice, with video+audio recording made available for a limited time.

Thanks,
- Sean





On March 24, 2023 11:41:24 AM UTC, Melvin Carvalho <melvincarvalho@gmail.com> wrote:
>pá 24. 3. 2023 v 10:42 odesílatel Marcus Rohrmoser <me+swicg@mro.name>
>napsal:
>
>> On 23 Mar 2023, at 22:34, Johannes Ernst wrote:
>>
>> > Can I see a show of hands who is planning to show up next Wednesday
>> > 10am pacific aka 17:00 UTC? Just trying to get a sense whether it’s
>> > 2 or 200 :-)
>> >
>> > Also, would it make sense for people who have a strong opinion on what
>> > should and should not be done to write up their core points in a
>> > (extremely brief) bullet list and post those here?
>>
>> I will attend and have put together a short intro below to set
>> expectations if you like.
>>
>> regards,
>> Marcus
>>
>>
>>
>> # Intro
>>
>> to the swicg meeting[1] on Wednesday, March 29, 10-11am pacific daylight
>> savings time. (17:00 - 18:00 UTC) at
>> https://meet.privacysafe.io/ActivityPub.
>>
>> swicg stands for 'Social Web Incubator Community Group'[2].
>> To live up the term , let's be social ourselves in the first place.
>>
>> 1. be kind, treat all others with dignity,
>> 2. assume benevolence, even if it doesn't sound like,
>> 3. let's dedicate 10% of the time addressing societal impact as e.g.
>> safety, protection of minorities, human well-being, resource
>> consumption, etc.,
>> 4. everything said and written is public and may be recorded,
>> 5. try your video setup 15 minutes prior the meeting, prefer browsers
>> from the Chromium family,
>> 6. wash your hands,
>> 7. pick a unique nick easy to pronounce and write for most,
>> latin+numerals work fine,
>> 8. if you intend to remain silent, prefix your nick with 's ', e.g. 's
>> Marcus',
>> 9. please join the meeting muted but with video, you may switch that off
>> later,
>> 10. the moderator should say hello to each participant and the
>> participant should respond,
>> 11. the moderator may use the lobby and deny access without argument,
>> 12. after you raise hand, the moderator may put you on the speaker list
>> (i.e. write your nick to the chat),
>> 13. let's stick to the time, i.e. close record[3] and meeting sharp.
>> Discussions may continue elsewhere, however,
>> 14. the record can emerge here[3] and be sent in plain text form to the
>> mailing list plus be mirrored elsewhere (put the links into the record).
>>
>
>I appreciate the thought that has gone into this list, however I think
>there is potential to draw from standard W3C meeting structure.
>
>I think the fourth item is especially noteworthy, and I suggest offering to
>scribe and produce a transcript of the conversation as this could be
>valuable for those who were unable to attend.
>
>>
>>
>>
>>
>> [1] https://lists.w3.org/Archives/Public/public-swicg/2023Mar/0124.html
>> [2] https://www.w3.org/wiki/SocialCG
>> [3] https://hebdo.framapad.org/p/activitypub-swicg-a008?lang=en
>>
>> That said, we have the
>>
>> # Agenda
>>
>> about 15" each:
>>
>> 0. Welcome
>> 1. Collect views on the future of ActivityPub (and related)
>> standardization
>> 2. Emerge with some sense of common direction (or be more clear about
>> where disagreements may lie)
>> 3. A couple of next steps
>>
>> ## Backlog
>>
>> - schedule next meeting
>> - i18n
>> - canonical urls for discussion, drafting, publication (mitigate link
>> rot)
>>
>>