Meeting minutes
/invite rrsagent #wot-marketing
Meeting Tool
kaz: let's not name it special and normal
dape: we can use core and full team
kaz: we can say first of the month and other
RESOLUTION: The Marketing TF will use Microsoft Teams for the marketing calls that are not the first one of the month
ek: I hear no objections
Minute Taking
ek: we have said that each meeting we do a review and note the changes in the minutes, every month we ask Kaz to incorporate them.
dp: We can also use another minute taking tool since we cannot change the minutes ourselves
kaz: only the first of the month meeting have attendance of the Team Contact and the Chairs, you can manage the other meeting minutes yourself
ca: we can also not take minutes and write action items
ek: I would be ok to note action items in github issues and pull requests
RESOLUTION: For meetings that are not the first of the month, the task force will not take minutes but record the action items in GitHub Issues and Pull Requests
Policy for WoT Marketing page maintenance
<Ege> s/ topic: Rules and Policy of the Meetings that are not on the first of the month / topic: Rules and Policy of the Meetings that are not the first of the month
kaz: we should discuss the agenda and the tasks of the marketing task force. the more important is not how but what to discuss during the WoT Marketing calls.
ek: let's discuss this topic and then come back to the tasks overall
kaz: we can also start on the hour but finish in 30 minutes
mm: other 2 members have conflicts to start on the hour
dp: I would be 15 minutes mostly
kaz: if, that is difficult it is fine
ek: we can test and find a solution if the time is not enough
Proposal1: For the WoT Webpage related topics: We work only with PRs. The changes that do not need a special meeting are: link updates, typo corrections, adding a single item to a list (devtools, TFs, events). Adding or removing pages, adding or removing paragraphs or changing significant part of paragraphs need a special meeting.
Proposal2: For WoT Webpage related topics: The PRs should have the corresponding labels: needs-WG-review, time-critical (for bringing to main call), minor (editorial, technical and trivial changes). If the type of PR needed is clear from the issue, these labels can be also used in an issue
<kaz> kaz: this is the policy for the WoT Marketing page maintenance. right?
<kaz> ek: yes
kaz: You can change the title in the agenda as well
RESOLUTION: For the WoT Webpage related topics: We work only with PRs. The changes that do not need a special meeting are: link updates, typo corrections, adding a single item to a list (devtools, TFs, events). Adding or removing pages, adding or removing paragraphs or changing significant part of paragraphs need a special meeting.
RESOLUTION: For WoT Webpage related topics: The PRs should have the corresponding labels: needs-WG-review, time-critical (for bringing to main call), minor (editorial, technical and trivial changes). If the type of PR needed is clear from the issue, these labels can be also used in an issue
ek: aob?
<kaz> none
<kaz> [adjourned]