Given we have other priorities in migrating the Space blog, I'm changing the status to low.

As we've used WordPress over the last six months the practical use of the blog has been that most folks are more comfortable with just uploading images via WordPress and writing their own attribution. It's also proven to be less complicated than explaining how to use a non-default block.

Well, investigating this isn't important now. As we close down Discourse we'll not need to fix this problem! We'll be using WordPress comments in the new blog.

The task with the developer is still open, months later. I don't think it's a priority for them at the moment. As we transition to a new community blog from Space I think this feature is rather low priority. Perhaps we can revisit in the future, but for now declining.

I have reached out to the developer and asked for this feature to be investigated. They have not responded. Unless we wish to expend development time for this feature, which I don't think we should prioritize at the moment, I'm going to decline.

The categories are documented on Meta: https://meta.wikimedia.org/wiki/Wikimedia_Space/Editorial_guidelines#Content_categories_and_tags

I'm going to resolve this task for now. We keep an etherpad with notes from each meeting and any user can login to the bog and see all drafts in progress and their scheduled publication dates (if they exist). If folks can't join our Zoom meeting, they can still keep up and stay in contact with editors as news is published.

I love all the thoughts and energy that have gone into this task. As you may have heard Wikimedia Space is closing down the Discuss side of the project. The community blog will continue in a new form. I'm removing the Space project tag as it will lo longer be something we seek as of the end of March. Others may wish to continue this work to be used elsewhere in the movement.

I did some research into what this would entail. The difficulty is that writing something would duplicate existing documentation on Meta, require more translation, and be a fairly unintuitive interface editors would have to work around (deleting a bunch of text that's suppose to be instructions for return authors as an example). I think the KISS principle applies here. ;)

The Discuss side of Space is winding down. The result is that the event calendar will no longer exist. This means we won't have a feed of upcoming events. Declining until a future point where a central calendar exists.

Even with the Space blog migrating to a new home, we still have a need for an editorial board with community membership. I renamed this task as we continue this work.

The discuss side of Wikimedia Space is closing. The blog side is continuing, but not using Discourse. Declining in favor of creating a new task for integrating WordPress notifications with Echo.

@DNdubane_WMF do you need more help from us on this deployment? We published the blog post but I can't remember if we discussed anything beyond that.

Yes, sorry for the delay. Blog post was published on 19 December.

@DNdubane_WMF I'm working on this now and will have a draft to share today.

Hey @DNdubane_WMF I'd be happy to get the draft into Wikimedia Space and help publish it. However, I can't seem to be able to copy/paste from the doc. :)

Heya @NSaad just following up. Do we need to chat about this at all?

I started a rough draft, @elappen-WMF please edit!

I suppose it would inform the community better on our progress than here in this phab task. @elappen-WMF could I borrow your "Building a multilingual Space" headline and write up a part two?

Since we launched the Space prototype in June we've been manually adding links to other language version of blog posts. This is clunky and cumbersome.

we don't hear very often from you.

@Bmueller I can be a scribe for the People and Processes - Magnolia session.

Something that I'm missing here honestly, is the dedication to educate and teach new developers/team members as a core principle, before tossing them into the deep end... This is honestly more of an internal WMF thing to decide on, but work in that area can easily benefit any contributor and I think WMF is rather bad at this area (possibly because of their history of people who 'grew up with the codebase'..

This feature has been added and documented!

Documentation is in a good enough draft for human consumption (and feedback!)

I will let @CKoerner_WMF handle https://space.wmflabs.org (WordPress).

We've been using the plugin for a while now. It works great with the Classic editor, but in the new block editor (Gutenberg) there seems to be a few hiccups.

To help illustrate, the settings are located underneath this circle icon next to the "+ New Topic" navigation.

Hey @Samwilson and others. I've been working on creating a more better description for this task. Something we could workshop and discuss and eventually provide guidance to a contract MediaWiki developer. I hope I'm not stepping on toes and happy to discuss!

I've made an attempt to better describe the requirements for this task.

This is what I see on my iPhone using Safari. Tapping outside the modal doesn't seem to make it close and in landscape its rather large. :)

Resolving as I'm under the impression that we're done. The feature is deployed and feedback has been mostly positive and addressed when possible.