What about polishing this task as a goal and making it a team goal for the next quarter?

About the description. This is the "backbone" goal that we discussed, correct? If it is, I think these tasks are key:

• Agree on the vision for this documentation. I realize that after talking so much about ity, we might not even have the same idea in mind. I'm thinking of a manual with an index maintained in one public wiki, with an appendix for WMF internal documentation located in office.wiki.
• Define the scope of the documentation we maintain. What falls in, what falls out.
• Define an index for this documentation, to be initially located at the "Working_with_communities" page. By index I mean a classical index. I think our inspiration should be Wikibooks. In comparison, "Map of the English Wikipedia's help pages" looks like a documentation dystopia? :)
• Decide a location of this documentation that makes sense. Anything not WMF internal should be probably public and be in one wiki. Internal WMF documentation should link to public pages, not overlap / duplicate them.

I'm not sure how sequential or parallel you expect this process to be, but I suggested to start with stakeholders and vision.

About scope, one task to challenge our assumptions:

Find, gather and centralize documentation about best practices concerning replying to newcomers on Help Desks.

Would this piece of documentation be within scope or not, and why?

In T202929#4658008, @Qgil wrote:

About scope, one task to challenge our assumptions:

Find, gather and centralize documentation about best practices concerning replying to newcomers on Help Desks.

Would this piece of documentation be within scope or not, and why?

Researching the existing documentation that each community had produced for the benefit of WMF work, yes that is within our Team's remit. Writing instructions for the communities, no. Suggesting changes to communities own documentation based on what we find, maybe.

• I have finished making all existing pages on MetaWiki translatable, including the last weekly updates.
• I completed the French translation for most of them (there remain a few pages partly translated but without difficulty related to the links or embedded "tvars" so they are not difficult to translate (in some cases I added some hints in the doc part of the translate interface for things that may be added or things that should be kept unchanged and better not translated).
• I wikified a few pages that were using long boring text: the newsletters are less boring, and they now all feature at top the {{Abstract Wikipedia}} template that link to the existing communication channels (this small bar is now floatting to the correct side at top of pages, just below the languages navbar and included a small link to translate the description of its icons visible when you hover them). Note that this template is in a "noinclude" section, just like the "languages" nav bar and categories, leaving only the main content which is deliverable to other users of they which to subscribe these news with MassMessage for their user pages on other wikis or for other community portals.
• I completed the test for Bidi support. I also arranged the few templates used so they are all translatable and with a correct layout with Bidi.
• I completed the categories to avoid mixing all languages, they are still navigatable across languages with an easy return to the English version for missing pages still not translated.
• All links use the internal "Special:MyLanguage/" prefix for link targets (hidden inside tvars, so translators don't have to bother on them).
• For existing translations, I made the necessary fixes needed after minor changes.
• I made sure that all translation units are short (splitting long paragraphs into separate units for long paragraphs, this allows easier work in the translate interface, while still not creating a "patchwork" (where sentences are broken in the middle and would not order correctly in other languages according to their grammatical syntax).

If there are things missing or not working I can help fix them, e.g.

• Missing {{GENDER:||}} if some messages are adressing directly to the reading user;
• A desired change in the subcategories when the number of pages will increase and new needs for subtopics (I think there will be an "/Archive" subcategory, still not existing for now)
• Fix quirks with some languages if they are still difficult to translate as is with the current layout.
• Future changes that may be needed next year when the new wiki of functions will be launched, to prepare their possible move from Meta-Wiki.

Things still not done:

• translating the embedded images and importing them in Commons.
• indexing other documents (notably PDFs and research articles, e.g. announced in Twitter or other channels).
• possibly setup other open/free social networks and communication channels (like Mastodon, RSS feeds, PeerTube, etc.); one of them is ready in the template, but hidden in HTML comments. How many channels do we want to support and keep active? This would probably require the involvement of other interested users to maintain them and relay the information, or the possible development and maintenance of import bots for announcements made on a primary channel (maintained by the WMF itself but accessible to all non-technical users, so probably not this Phabricator instance).

@Verdy_p: Please don't post off-topic comments in random unrelated places. Thanks.

@Quiddity: Is this still a task that you plan to work on, or should this be declined?
(Asking as tasks shouldn't be "stalled" forever and it is unclear what this task is exactly stalled on.)