This is still relevant but await CRM-decision before pursuing it further

Two follow up tasks:

• Documentation described in T351223#9637152
• mediawiki/services/wikispeechis called (repos/)mediawiki/services/speechoidon GitLab which needs to be considered in the migration - T360758

As part of this README-merge-from-github-upstream.md should probably be updated

This doesn't seem to have been an issue in the last couple of years so closing this

No longer relevant

In T353158#9653070, @Sebastian_Berlin-WMSE wrote:

Done. T360606: Define a list of roles per Google Workspace group came up during this run.

ping @Eric_Luth_WMSE @Jenny_Brandt_WMSE @Jopparn It would be good to be able to close the Gallring 2023 before the AGM 2024

@Jopparn
Looking at the list from 2019 there seems to be a bunch of e-mail conversations which should probably be added to the diarium (Wikimania). Unsure who had those conversations though.

@Sebastian_Berlin-WMSE Would this work? docs-link

@Sebastian_Berlin-WMSE Can you rebase the PR to make it clearer which changes are happening outside of wiki.py

It needs a category but otherwise it looks Good

@Sebastian_Berlin-WMSE is there a sub-task for doing a re-run with Project data for the 2024-projects [Since this is in done-column]

In T356864#9576631, @Sebastian_Berlin-WMSE wrote:

@Lokal_Profil, do you think we need to do anything more at the moment concerning this or can this task be closed?

In T356624#9541185, @Sebastian_Berlin-WMSE wrote:

Functionality added using regex to match URLs, e.g. if you set allowed_url_pattern to https://se.wikimedia.org/wiki/.* in the config, only URLs from out wiki can be used. If not an error message is displayed.

I added the pattern above to the WMSE-config, but haven't deployed anything yet. This would mean that anything anyone puts on our wiki could be used in the preview. I think this should be restrictive enough. @Lokal_Profil, do you have any thoughts?

This should be moved to Content partners 2024 once that is set up

If GM not added then it is too late now

If GM not added then it is too late

IF GM not added then it is too late

@Jopparn A ping about publishing this document.

@Jopparn Closing this as too much time has passed. I'll recycle the Q3 task for Q4/end of year

Final bit of this handled by purging the physical copy of the consent of the guardian of a minor member who is now of age.

We are keeping the 1 year retention time for now since a routine is in place

This was cancelled

In T319787#9462161, @dcaro wrote:

As far as I can see it's jstop/jsub of that other job.

I would recommend joining both jobs into the same one, k8s jobs will not overlap each other (@taavi correct me if I'm wrong, looking at https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/blob/main/tjf/job.py?ref_type=heads#L376), so you can be sure that there's only one instance running:

## all_in_one.sh
# simplified here, use whichever arguments you need, you can remove the jsub/jstop commands from the scripts too
./update_monuments.sh
./categorize_images.sh

This might run less often that you want, if it takes longer to run than the scheduled period, but maybe that's ok.

Now on wiki
https://se.wikimedia.org/w/index.php?title=Scrive&diff=114961&oldid=113099

After discussions the conclusion is that jäv-intyg (approx. Conflict of interest statements) should be archived in the diarium. The reason being that there is a public interest in verifying that such a statement has been required. Should someone request the info one would however have to ensure what PII can be shared.

All candidates were purged

Apologies! Seems to have been bad internal communication on our end. It's activated, just that the config hadn't been set up.

This one is still relevant for 2024. Nationalmuseum is probably a good test case. The alternative is to fold this into the A network of places project.

We should probably put together an e-mail to SHM about this. Even for the example given in the task description the image-source link is currently broken. It's unclear how many of the links are broken though. Not exactly sure how to go about figuring that out since the resulting page gives a 200 (page exists) result even as the resulting page is the 404-error page.

Good place to collect them =)

@Sebastian_Berlin-WMSE
Do we want anything around this on wiki?

Superseded by later meetings

In T352429#9402705, @Sebastian_Berlin-WMSE wrote:

PR: https://github.com/Wikimedia-Sverige/project-start/pull/49.

This is partially blocked by checking that parallelisation now works. In turn requiring T351223