Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Multisite Agenda Post Boilerplate
Post Title:
Multisite Agenda for the week of {F jS (month + day)}
-----------------------------
Post Content:
<h2>Office Hours Agenda</h2>
This is the agenda for the weekly office hours meeting on [time relative]Tuesday 16:00 UTC[/time] in <a href="https://wordpress.slack.com/archives/core-multisite">#core-multisite</a>.
<ul>
<li>Discussion/Goal Item 1. [See #12345. (ticket number if applicable)]</li>
<li>Discussion/Goal Item 2. [See #12345. (ticket number if applicable)]</li>
</ul>
<h2>Ticket Scrub Agenda</h2>
This is the agenda for the weekly ticket scrub meeting on [time relative]Monday 17:00 UTC[/time] in <a href="https://wordpress.slack.com/archives/core-multisite">#core-multisite</a>.
<ul>
<li>Discussion/Goal Item 1. [See #12345. (ticket number if applicable)]</li>
<li>Discussion/Goal Item 2. [See #12345. (ticket number if applicable)]</li>
</ul>
Please join the chat if you're interested in one of the topics. In case you cannot make the respective meeting, {@username} will be working on publishing a recap post afterwards. If you have some thoughts beforehand or would like something related to be part of the agenda, feel free to share your ideas in the comments for this post. See you in the chat!
-----------------------------
Post Category:
Meetings
-----------------------------
Post Tags:
multisite, networks-sites, agenda, {4.9 (WordPress version number)}
@desrosj
Copy link

desrosj commented Jun 23, 2017

I think we should flip the ticket scrub and agenda mainly to be in chronological order. But the ticket scrub should be short.

Maybe the ticket scrub is "There will be a ticket scrub on xxxx lead by xxxxx focusing on tickets that are xxxxx (linked to the list in trac)" instead of a list. We could use the list if there are multiple ticket lists.

@felixarntz
Copy link
Author

felixarntz commented Jun 23, 2017

I had the chronological order first, but I think it makes more sense for it to have the office hours first, as they are more significant (also the length of the sections doesn't matter as much then). I don't think it would make sense to switch the order around in case we have to adjust meeting times at some point.

I agree that the ticket scrub section should be shorter than the office hours one, but I'm not sure we can always use a predefined sentence like you're proposing above, as we might have cases where we actually need to discuss a particular smaller bug in more detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment