All past event summaries are here https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Summaries.

Blog post is here https://docs.google.com/document/d/1vBHDeXW-OHQudJwzPGtMwIubjQInMuncgWqMe0GtjO8/edit. @srodlund When you get a chance, could you start reviewing this post please? It is ready from my side :) When Birgit returns from vacation, I will run this by her and incorporate any needed changes.

@srishakatux Acknowledged! I will take a look at this in the next couple of days!

@srishakatux Hey hey, I took a first pass at this. Please take a look and accept or reject the changes, and I'll do an other pass after!

@srishakatux let me know when you and @Bmueller finish up your final edits, and I will schedule this for posting.

@srishakatux and @Bmueller do you want to be listed as coauthors or just one author?

@srishakatux This is ready for publication (except for the author issue).

@srodlund You can keep me as the author of the post and give copy-editing credits to Birgit and yourself :)

This is published but still needs to be announced on Twitter. https://techblog.wikimedia.org/2020/09/29/one-year-of-small-wiki-toolkits-initiative-and-more-to-come/

@srishakatux will check to see if it can be published on Diff.

In T249769#6502987, @Aklapper wrote:

@Nintendofan885: Please do not close tasks if there is still work left to do but leave it to the assignee. Thanks.

Oh, it was just because I saw it had been posted on the tech blog and didn't see the bit about Diff

@Nintendofan885 it's a good practice to let the folks who are working on a ticket decide whether it is resolved or not.

It's fine to check in with people if you notice a ticket has been sitting unresolved for a while (Note: as a part of his role, @Aklapper is already keeping an eye out for these and checking in with people periodically to make sure they are progressing on tickets).

With technical blog posts there may be some extra cleanup at the end of the post. Sometimes, we need to make corrections (style, grammar, or substance) to the published post even after it is announced. Sometimes there is some sort of follow up. For instance, today I had a number of competing priorities and could not send the tweet out right away. @srishakatux is also following up with another venue regarding posting there. Therefore, we are not ready to close the ticket.

A good rule of thumb is to check with folks before doing things like reassigning or resolving. And just as a matter of common courtesy it's also nice to let folks who have been working on a ticket resolve it. I personally like the satisfaction of closing tickets I am working on and feel a little cheated when someone who has not been involved resolves it before I get the chance. :-)

I have noticed that you are showing an interest in the technical blog and tickets related to it. Can I ask what draws you to the project and how you would like to contribute to it? It is possible there are some specific tasks you may be interested I can point you to?

Hi all-I've submitted the post on Diff as well for review. Hopefully, we will get it published there in a day or so and we can then close this task.