Meeting minutes
Introductions
kaefer3000: I'm Tobias, I'm at Karlsruhe
… i'm part of the SoLid symposium steering committe
uvdsl: I'm Christoph
… I'm a student of Tobias
timbl: I'm Tim Berners-Lee
… working on making the Web R/W
… day job is with Inrupt but spend lots of time in open source world, e.g. SoLid OS
Meeting cadence
acoburn: last week we talked about the meeting cadence.
… The charter says "every 2 weeks", but we have a lot to do in 2 years.
<acoburn> Proposed: The lws working group will meet weekly rather than every other week.
acoburn: We have an initial vote on the proposal above last week, but didn't conclude that vote.
<timbl> Yes i think that is good idea to meet everyweek
pchampin: reading last minutes, i saw the possibility of changing the time to aid folks in other timezones
… perhaps we can have an Asia-Pacific-friendly meetring every now and then
csarven: +1 to pchampin's suggestion, that address my concerns.
… +1 also to a weekly meeting.
… Processwise, it would be good to make an announcement to the participants to ask if they want another time.
… If only the people in the meeting are making the decisions, this may not be representative.
jacoscaz: +1 to what csarven said.
… In my case, I should be able to join most meeting, but I can't guarantee that I can attend them all.
… It would be good to give people who can't attend an additional week to comment on decisions.
acoburn: as a matter of principle, when big decisions are taken, there need to be a provision for async participants as well.
… We need to strike a balance between being reactive and giving time for sufficient feedback.
<acoburn> Proposed: The lws working group will meet weekly rather than every other week, with one meeting per month to accommodate different timezones
acoburn: I think there are 2 parts to the proposal, let me revise it.
… the proposal is to meet weekly, with a monthly slot, TBD, to accomodate other timezones
<pchampin> +1
<cpn> +1
<uvdsl> +1
<jacoscaz> +1
<AZ> +1
<jeswr> +1
<kaefer3000> +1
<eBremer> +1
<ericP> +1
<TallTed> +1
<ryey> +1
acoburn: could someone send a message to the group to ask for input on an alternative timezone?
… meetings would still be on monday.
jacoscaz: hesitating because this is my 1st WG, but I'm happy to do it.
RESOLUTION: The lws working group will meet weekly rather than every other week, with one meeting per month to accommodate different timezones
ACTION: jacoscaz to send email to lws list asking about alternative times
pchampin: re managment of actions, we could invite another bot which records actions as GH issues.
… we're using it in RDF-star
… currenlty, the only recording of actions is in the minutes
<TallTed> +1 create github issues for each action (for tracking)
acoburn: right now we are not doing a lot of work in github, but I can see more value in that later.
… let's defer this decision.
Use cases template
<acoburn> Use Cases Template
acoburn: Laurens has created a use-case template, there were a few comments.
… csarven has a review as well, but he had to leave already. Other comments?
timbl: I have a general question. Is there only one level when we are talking about use-cases?
… Some use-cases are "you should be able to use the protocol for medical data", very high level.
… Other use-cases involved scenarios, persona... Different characteristics.
<Zakim> ericP, you wanted to talk about LDP Use Cases
timbl: What level are those use-cases expected to be?
ericP: I wanted to bring up the Linked Data Platform use-cases.
… because a) they are also about a protocol, and b) they provide a base.
… They contain a high level business case, then a more technical part from which requirements can be extracted.
timbl: can a business case be any level? Or you start high level, then get into details.
acoburn: TallTed, thanks also for your comments.
… We are not going to get this merged today, but I would like people to look at this.
… We don't need this template to be perfect, but as use-cases come on, I would like them to have some kind of consistent structure.
… Imposing some kind of structure would improve the quality of use-cases.
<Zakim> ericP, you wanted to propose drafting a couple examples
ericP: rather than looking at the template, it might be easier to use it to encode some of the TPAC use-cases,
… then let the editors of the UC document adjust the template.
… And let them approve the PR when they feel it is good.
acoburn: please write a proposal.
PROPOSAL: let Hadrian Z approve pr#5 and/or modify the Use Case template as he (or other editors) see fit
<acoburn> +1
<pchampin> +1
<ericP> +1
<eBremer> +1
<jacoscaz> +1
<TallTed> +1
<hadrian> +1
<AZ> +1
<cpn> +1
<jeswr> +1
<kaefer3000> +1
<uvdsl> +1
<timbl> +1
<ryey> +1
RESOLUTION: let Hadrian Z approve pr#5 and/or modify the Use Case template as he (or other editors) see fit
acoburn: that does it for what we have on the agenda; with a weekly cadence, our next meeting would be next monday.
… Please note that the US is out of DST, so the meeting time will remain consistent from one week to the other now (unlikes last week).
… Any closing remarks?
[crickets]
… Then we can adjourn early. Thanks everyone for joining.