W3C

– DRAFT –
WoT Marketing

02 May 2024

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Kaz_Ashimura, Luca_Barbato
Regrets
-
Chair
-
Scribe
cris

Meeting minutes

schedule

Ege: this is the new slot
… there will be some cancellations
… please refer to the wiki

<kaz> main wiki - Cancellaitons section

updates

Ege: we used to have an analytics webpage
… but system admin did change the configuration and we are not get the right numbers now
… they are evaluating cloudflare

merged PRs

Ege: we added an article by Michael Lagally
… also we updated the times and updated the Siemens TDD links

<Ege> PR 481 - Add oracle article

<Ege> PR 484 - IG Charter extended till 30 June 2024

<Ege> PR 485 - fix: DST changes - use use summer time

<Ege> PR 487 - Replacing Siemens TDD with Eclipse Thingweb TDD

issues

Ege: we have a pending action point about updating the readmes
… we created a template to be used in different repositories

Ege: I can assign the task to different people

<kaz> Issue 461 - Changes after getting a Mastodon account

PR

PR 489

<Ege> PR 489 - refactor: move Marketing to Thursday

Ege: small update about the schedule
… we put the right timing for the marketing call
… thinking about it we can remove WoT Discovery and WoT Security calls
… they are paused right now
… anyhow we can update it later
… can we merge this PR?

Kaz: no objection but I'm wondering if it makes sense to keep maintaining

Ege: yeah I don't like to keep this in sync
… I'm working on something that renders it automatically
… I'd not remove it but as far as I know there are some users

Kaz: the page is useful but it takes time to keep it in sync

Ege: there is a problem in 489 we merge it afterwards

minutes review

<kaz> Feb-6

Ege: let's review them together
… we discussed the repository template
… the template should be moved into the root wot repository
… any remarks about the minutes?
… ok minutes approved

overall plan

Ege: documentation page is outdated
… and we have a couple of open issues
… should we prioritize some work?

Cristiano: people read documentation page that's at least what we know from our old web analytics
… we should prioritize work aim to improve that page

Ege: agree

Kaz: as before the problem here is to understand how much work it will take to make that page perfect
… maybe we should plan even more in the future about our effort in the marketing task force

Ege: right we should prioritize specification work
… on the other hand marketing pages are good for community building
… we can just keep the developers (implementers) updated

Kaz: an idea is to understand which pages need regular updates and understand how much we can do with the number of people that we have

Ege: we can understand better asking in the main call

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).