Mobile usability would definitely be nice. However, I don't think the tool currently has any users except for me.

Info on the REUSE project for future reference: https://reuse.software/

For the license headers issue - it looks like there's a project called REUSE from free software foundation europe. Which provides a tool to validate that license data is configured correctly on a project.

Fixed in this commit, closing: https://gitlab.wikimedia.org/toolforge-repos/wd-act/-/commit/79e7873685b1dbe597bb28b1a2fd2a9ae9a803d7

TODO list:

• Add license headers to all files (or all relevant files? unsure)
• Include useful links - see here: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Developing_successful_tools#Include_useful_links_on_a_tool's_public_webpage

I tested this a few days ago and at the time, from memory, it didn't work. I wasn't able to call the toolforge API without authentication.

This is done now.

Updated the docs in this commit: https://gitlab.wikimedia.org/toolforge-repos/wd-act/-/commit/d0c31d76424e57d637dbc849d45bf0fefd5bc17c

For the production configuration:
According to this page, toolforge environment variables are stored as k8s Secrets: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Envvars_Service

Docs updated here: https://wikitech.wikimedia.org/wiki/Tool:WikiDataAuthorityControlTool#Configure

Added a script setup to work easily on local dev machines. Still need to update dev documentation and make sure the production config is ok.

I've got a WIP branch here to do this: https://gitlab.wikimedia.org/toolforge-repos/wd-act/-/tree/T431042

The production OAuth consumer is setup here: https://meta.wikimedia.org/wiki/Special:OAuthListConsumers/view/1ef316396fb537bfdd76a0c1051d2e98
The code for this is in this commit: https://gitlab.wikimedia.org/toolforge-repos/wd-act/-/commit/572ed9d065cba64ebfde0cc885bc795d86df421c

On third thought:
Running this web app inside of kubernetes complicates things, because my image won't have access to the shared storage locations out of the box.

https://wikitech.wikimedia.org/wiki/Help:Shared_storage#/data/scratch

On second thought, the scratch directory isn't a good idea. According to the below page, it's shared across all instances in all projects.

Based on the below guide, I think the best/most standard way to store the API credentials for the application, would be inside a file in the project's data directory.
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Managing_and_sharing_files

This is done. Toolforge supports using Cloud Native Buildpacks, which automatically generate a Docker image for the project. So in other words, we don't have to manually build/maintain a Docker image. When we initiate a build in Toolforge, a Docker image is automatically created for us using buildpacks - and so this issue isn't really relevant now.

This is done. The framework used by Toolforge to deliver this application as a web service - Cloud Native Buildpacks - includes gunicorn.

I forgot to post the link - here's the page about GitLab CI in wikimedia: https://www.mediawiki.org/wiki/GitLab/Workflows/CI

Knocked this out in this merge request: https://gitlab.wikimedia.org/toolforge-repos/wd-act/-/merge_requests/1

After the scripts are written and checked in, I have to figure out how to copy them onto the toolforge build server so I can actually use them.

This section needs some serious review - there's a lot to go through in the terms of use: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Quickstart#Read_and_agree_to_terms_of_use

Working on this now

Done. Everything's fleshed out and lookin' good. Closing.

This list is mentioned here - may need to update something when I work on this ticket: https://wikitech.wikimedia.org/wiki/Tool:WikiDataAuthorityControlTool#Technical_implementation

Knocked this out a minute ago.

Wiki is now migrated over to the Tool's wiki page here: https://wikitech.wikimedia.org/wiki/Tool:WikiDataAuthorityControlTool.
There was only 1 page to migrate over for now, so not much to do.

Git repo is pushed up to GitLab now: https://gitlab.wikimedia.org/toolforge-repos/wd-act

For the Wiki migration, I should work it into a larger developer documentation section of the tools docs. See here for their guidelines on Tool docs: https://www.mediawiki.org/wiki/Documentation/Tool_docs

Issues have all been moved over. Still need to move Wiki and code hosting.

Thank you for tagging this task with good first task for Wikimedia newcomers!