Meeting minutes
Guests
Sebastian: we do have a new
member from UPM, Salvador Gonzales Gerpe
… unfortunately not here today
Minutes
Sebastian: minutes from April
5
… has a resolution for proceeding with the new
draft charter
… talked a bit about the detail document and
further planning
McCool: note that I have not touched anything in the "details" doc, we still need to work on that
Sebastian: ok. any comments
on the minutes, any objection to publish?
… hearing no objections, we will publish
these.
Quick updates
Sebastian: cancellations, any
news?
… Week of April 17 is Hannover fair, many people
will be unavailable
McCool: propose we cancel the Security call April 17, but Discovery WILL be held - Dev meeting
Sebastian: guess we don't know about Profile and Arch?
Kaz: discussed in Profile call, assume will be held, also Arch next week
Sebastian: next, need to
submit TPAC questionnaire
… how many people, will we have a meeting, what
dates and times, etc.
… also need to plan joint meetings and look for
conflicts
… and do we want a pre- or post-
meeting?
… plugfest before? vF2F before?
… deadline is not until May 8
… McCool created a wiki page, see link in
agenda
Kaz: deadline for this qs is May 8; what is important is what day we will have meetings
Kaz: this however is a hybrid meeting, so some people can be remote, so we need to identify how many people would be there in person based on the agenda and the schedule.
<kaz> TPAC 2023 page
McCool: note that only
Thursday and Friday are conflict-free at present
… up to 16 hours if we use all slots, but need to
worry about remote participants
… so probably can only use afternoons
Ege: so topics are one
thing, physical presence
… I do plan to go
Sebastian: I also plan to go
McCool: I am not sure
yet
… let's add a section to the wiki to track
this
<kaz> WoT TPAC 2023 wiki
Sebastian: (edits wiki to add link to qs, etc)
Sebastian: also need to
clarify plugfest
… personally think demo table was very good, but
need prep time
McCool: propose we take the
weekend before for a demo-development plugfest, and then also
schedule a demo breakout
… however this qs does not ask about breakouts -
that will come later
Kaz: please remember
breakout sessions will be handled separately, will come later
… having demos and plugfest like in Lyon would be
useful but situation is still a hybrid meeting
… will have to organize carefully, agree, can
support remote demos as well
McCool: but can organize later
AOB
Sebastian: any other topics?
Ege: marketing task force resolutions
<Ege>
https://
1. Collecting articles about WoT from the Web with a strict selection policy: As you can see in the Pull Request [1] and its rendering [2], we are adding a new page with list of articles from the Web. The policy to select them can be also seen at [3]. If you do not have any objections, we would like to merge the Pull Request. 2. Social Media Management: We have decided [4] that the social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can promote WoT content created by other entities. We have detailed the policy in a comment at [5]. After a group resolution, we will change the current policy [6] to reflect this.
Ege: good to look at
related PRs and policy documents; for example, review policy for
listing articles
… only links, not rehosting
McCool: need actual resolution for this...
<Ege> proposal: we agree to merge PR 357 of the marketing repository to have an articles page on our web page
<Ege> proposal: we
agree to merge PR 357 of the marketing repository to have an
articles page on our web page. See PR: https://
Kaz: also good to link email
<kaz>
https://
McCool: to confirm, this covers only item 1, right?
<kaz> 1. articles about WoT from the Web with a strict selection policy: As you can see in the Pull Request [1] and its rendering [2], we are adding a new page with list of articles from the Web. The policy to select them can be also seen at [3]. If you do not have any objections, we would like to merge the Pull Request.
Ege: right
RESOLUTION: we
agree to merge PR 357 of the marketing repository to have an
articles page on our web page. See PR: https://
Sebastian: any objections?
Sebastian: then there is the second request
<kaz> 2. Social Media Management: We have decided [4] that the social media accounts owned by the IG/WG such as our Twitter account, or others in the future, can promote WoT content created by other entities. We have detailed the policy in a comment at [5]. After a group resolution, we will change the current policy [6] to reflect this.
Ege: this is about
twitter, but also social media in general
… whether we can post content on the WoT twitter
account, which belongs to the WG, can come from other
groups
McCool: as the policy is stated, feel a little uncomfortable allowing groups outside WoT (JP) CG to post
Sebastian: so this is a policy it that we will share the twitter account, correct?
Ege: right, as long as the group posting is identified
Sebastian: ok with this approach, would rather not have a separate social media account, too messy
Sebastian: generally agree
Kaz: what we discussed
in the marketing call was having separate accounts for each group,
can do their own posts about their own properties.
… so would then *retweet* on the main WoT WG
twitter account
Ege: that is correct;
we didn't say that other groups would have own account, can be any
resource, but retweeting is easiest way
… general idea however is to only reference
content, not duplicate it
McCool: sounds good to me
<Ege> proposal: We have
decided [4] that the social media accounts owned by the IG/WG such
as our Twitter account, or others in the future, can promote WoT
content created by other entities. We have detailed the policy in a
comment at
https://
<Ege> proposal: The
social media accounts owned by the IG/WG such as our Twitter
account, or others in the future, can promote WoT content created
by other entities. Detailed policy is available in a comment at
https://
Kaz: if our intention
is to do what is discussed in this call, but is dangerous to mix
things up do much
… mechanism is that anyone can refer to any
resources
… this proposed policy is still a bit
vague
McCool: want to modify the resolution or the policy doc?
Kaz: should be more explicit about using only references, not copies, of content
<Ege> proposal: The
social media accounts owned by the IG/WG such as our Twitter
account, or others in the future, can refer to WoT content created
and owned by other entities. Detailed policy is available in a
comment at
https://
Kaz: someone may wrongly understand if they only see this resolution
Sebastian: anyone objecting to current proposal?
RESOLUTION: The
social media accounts owned by the IG/WG such as our Twitter
account, or others in the future, can refer to WoT content created
and owned by other entities. Detailed policy is available in a
comment at
https://
New WG Charter
<kaz> Proposed Charter
Sebastian: have draft, have
submitted for horizontal review
… still fresh, so no reviews yet
Kaz: created strategy pipeline, first horizontal review, then W3M review, and then AC review
Sebastian: next, need resolution to publish minutes for charter discussion
Charter meeting minutes
<kaz> Charter meeting page including the links for the draft minutes
McCool: I have done a full review, sent a list of corrections
Kaz: have corrected all the ones McCool mentioned
Sebastian: any other corrections?
proposal: publish corrected charter
discussion minutes at https://
RESOLUTION: publish
corrected charter discussion minutes at https://
Testimonials
McCool: suggest we push to
testing call, but in general need to contact AC rep, so may take
time
… if have questions, please email me
Societal Qs
Sebastian: still need to review, but McCool has updated
Dev meetings
<kaz> slides info (Member-only)
Sebastian: have been planning
Dev meetings
… note that Arch Dev meeting will be
tomorrow
McCool: have updated at-risk items in both of these. we should make sure external developers will join the events.
ek: will invite them
McCool: would also like to
send email to CG to invite; I will do IG/WG
… also, I will chair Arch Dev mtg if
necessary
Kaz: Mizushima will be working on JP Dev meetings; still to be scheduled
Testfests
<kaz> Testfest page
Sebastian: please be aware week of April 24, three days, 1h each day
McCool: this is our last
testfest this charter, and last chance to resolve at-risk
items
… note date for finalizing test results really May
10
McCool: also, scope is all deliverables, not just profiles
Kaz: so I asked the Profile TF to think about the Teftfest prep during the Profile call right before this main call today.
Binding Meetup
Sebastian: any news?
Mizushima: no new news
Kaz: we need to wait a bit to see feedback from other dev mtgs and testfest first
Detailed Work Items
<kaz> remaining PRs
<kaz> details doc
McCool: propose we do this only after testing is done
Sebastian: also think it is ok for TFs to merge items
McCool: for their own work items, sure, that is fine
AOB?
Sebastian: many cancellations due to Easter, so don't expect many TF reports
Sebastian: adjourn, thanks
<kaz> [adjourned]