Re: SWICG 2023 July meeting time

Hey, everyone! So, we had some coordination problems with the meeting today, and weren’t able to hold a formal meeting of the group. However, we had a good discussion between the people present. Here are my notes:

1. Extensions Process Note. The general consensus was that the extensions process note was beneficial and should be continued. The major concern was about versioning of the context document for those implementers that require an extra level of vocabulary stability. We agreed to continue feedback through GitHub issues. https://w3c.github.io/activitystreams/draft-extensions-policy.html 

2. Test suite. The need for a test suite for ActivityPub was brought up. The original test suite is now off line. There is discussion of work on a test suite on the AP group @activitypubtestsuite@venera.social <mailto:activitypubtestsuite@venera.social> . We agreed that test suites require a lot of effort and decided to orient any work on test suites towards the group.

3. Chairs. Dmitri has been doing great work as the chair for the SocialCG, but we feel like having more active chairs as backup for his work would be healthy for the group, and we think that holding co-chair election (or selection) in the near future would be helpful.

Thanks to everyone who came, and if I missed anything in these notes, please correct them! I’m looking forward to the next meeting.

Evan

> On Jun 24, 2023, at 11:54 AM, Evan Prodromou <evan@prodromou.name> wrote:
> 
> I’d like to propose four items for the meeting agenda:
> 
> 1. Extensions process and criteria. I propose a new note that outlines a light process for including extension vocabularies in the main AS2 context document. Draft is here: https://w3c.github.io/activitystreams/draft-extensions-policy.html 
> 2. GitHub issue #440 <https://github.com/w3c/activitystreams/issues/440>, “Tombstone ‘formerType’ Property Range Needs Clarification” proposes a backwards-compatible change to the AS2 JSON-LD context document.
> 3. GitHub issue #441 <https://github.com/w3c/activitystreams/issues/441>, “Example 60 Missing @context Property” proposes an addition to the ERRATA document and an update to the example JSON file for testing.
> 4. GitHub issue #443 <https://github.com/w3c/activitystreams/issues/443>, “Spec does not clarify non-functional natural language values when mapped”, proposes an addition to the ERRATA.
> 
> The first one is probably the most urgent, but I’d like us to get in the habit of discussing solutions to issues during the calls, too.
> 
> Evan
> 
>> On Jun 16, 2023, at 4:10 PM, Dmitri Zagidulin <dzagidulin@gmail.com> wrote:
>> 
>> Hi everyone,
>> 
>> Thank you for filling out the poll! The next call will be on Saturday, June 24 at 1pm Eastern / 10am Pacific / 7pm CET 
>> at https://meet.jit.si/social-web-cg
>> 
>> Talk to you soon.
>> 
>> 
>> On Thu, Jun 1, 2023 at 11:53 AM Dmitri Zagidulin <dzagidulin@gmail.com <mailto:dzagidulin@gmail.com>> wrote:
>>> Hi everyone,
>>> On previous call and on various discussion forums, there was preference stated that we alternate monthly meetings between weekday (say, Fri morning) and weekends. 
>>> 
>>> Here's the Doodle poll for the upcoming July monthly call, with weekend options for 2-3 weeks from now:
>>> 
>>> https://doodle.com/meeting/participate/id/eXr1Wkgb
>>> 
>>> Please let us know your preferences, and we'll do our best.
>>> 
>