Meeting minutes
Minutes Review
<kaz> Dec-5
Ege: Did not see any issues with the issues
… main thing was the collaboration with the CG
… otherwise, I've shown this PR that was presented in the main call
… seems that that was it
… if the initials are fixed, then we are fine
… can you do that, Kaz?
Kaz: Sure, fixed
Ege: Then the minutes are approved
Merged PRs
Ege: We did not have any non-minor PRs that have been merged since the last meeting
Updates
Ege: Our mastodon is now active, we have a number of related PRs
New PRs
PR 463
<Ege> PR 463 - Add Mastodon verification link to website header
Ege: This is an important PR by Jan, which adds a link to our website that will show that our account is verified, like the main W3C account
… minor PR, if there are no concerns, then we could merge it
Cristiano: Where does this link go?
Ege: It's added to the default page and it is a domain ownership check
… similar what Google does, simple ownership check
… (adds a comment to the PR and merges it)
… I will check later that the verification works
PR 462
<kaz> PR 462 - Add mastodon badge to readme
Ege: This PR adds a Mastodon badge to the README file of the marketing repository
… (shows a preview of the changes)
Cristiano: Looks good to me
Ege: I will also propagate the changes to the other repos
… also by the way, we got a lot of followers really quickly
… seem to mostly be technical people
… I was kind of surprised, we have a kind of similar reach as on Twitter before
Kaz: What did you mean by "copying the changes over to the other repos"?
Ege: I meant adding the Mastodon link to the READMEs of the other repositories
Kaz: Not sure if we need this, also: Is this approved by the whole group?
Ege: I think Michael McCool added the badges initially
… I think he put it in one repo and then we simply propagated
Kaz: Adding the links is technically possible, but the technical repositories should rather focus on technical aspects and marketing should happen in the area of the Marketing taskforce
Ege: It is just one line, furthermore this is part of marketing
Kaz: Do we want people to start at the repository and then go to our marketing channels?
Ege: Some people start at the specifications and go to the repository, and then maybe visit the social media channels this way
Kaz: I still think it's a bit odd to have links for SNSs on spec repos directly. I'll raise an issue again during the main call. That is probably a better place to discuss this matter
PR 466
<kaz> PR 466 - Mastodon Integration
Ege: This PR adds an iframe with the latest Mastodon posts to the website
… an annyoing aspect is that the background is always dark
… and there is no native way to change that
… would need to use a third-party tool or a manual API call
Cristiano: I don't think I have a good solution here, not the best solution style-wise, but good enough for the time being
Jan: Also not aware of a better solution at the moment
Ege: (adds a comment and merges the PR)
… I will open an issue for following-up on this topic
… (opens issue 467 as a follow-up)
Mastodon Account
Ege: Currently the Mastodon is tied to my own email, which we should probably change
… we also need to discuss who should have access to the account in the main call, currently only I have access from the WoT IG, at least chairs should also have access in my opinion
… then there is the question who we should follow back
… as we got so many followers, I am not sure who to follow back at the moment
… do you have some opinion here? I followed the @w3ces@w3c.social account, for example
… we should have a policy to be transparent here
Kaz: Let's have some discussion during the main call
Ege: Yes, let's discuss it in the main call, let me know in the mean time if you have any opinions on who to follow
<kaz> [adjourned]