This tool lets users create Wikidata lexemes with pre-populated forms, such as the declensions of a noun or the conjugations of a verb.
On Wikimedia Toolforge, this tool runs under the lexeme-forms tool name.
Source code resides in ~/www/python/src/,
a virtual environment is set up in ~/www/python/venv/,
logs end up in ~/uwsgi.log.
The uwsgi.ini configuration file in the source code repository
is symlinked into ~/www/python/uwsgi.ini.
To update the tool, assuming there were no changes in the Python environment:
git fetch
git log -p @..@{u} # inspect changes
git rebase
kubectl rollout restart deployment lexeme-forms
If there were new changes in the Python environment (e.g. new dependencies),
add the following steps after the git rebase:
webservice shell
source ~/www/python/venv/bin/activate
pip-sync ~/www/python/src/requirements.txt
If you’re fully restarting the webservice,
also update the Kubernetes deployment created by the webservice command afterwards:
webservice stop
# do whatever you need to do (new Python version -> new venv?)
webservice start
kubectl patch deployment lexeme-forms -p "$(<~/www/python/src/patch-add-startup-probe.yml)"
You can also run the tool locally, which is much more convenient for development
(for example, Flask will automatically reload the application any time you save a file).
Note that a local setup will not actually perform edits unless you create a config.yaml file.
git clone https://phabricator.wikimedia.org/source/tool-lexeme-forms.git
cd tool-lexeme-forms
pip3 install -r requirements.txt
FLASK_APP=app.py FLASK_ENV=development flask run --extra-files i18n/en.json
If you want, you can do this inside some virtualenv too.
Yay contributions! <3
To propose new templates for the tool, please head to its page on Wikidata and follow the instructions there.
To send a patch, you can use any of the following methods:
- Submit a pull request on GitHub.
- Use
git send-email. (Send the patch(es) to the email address from the Git commit history.) - Upload the changes to a repository of your own and use
git request-pull(same email address). - Upload a diff on GitHub Gist and send the link to the tool’s maintainer(s) via email, Twitter, on-wiki message, or whatever.
- Create a Diff on Phabricator. Make sure to add @LucasWerkmeister as subscriber.
They’re listed in the maintainer(s)’ order of preference, from most to least preferred, but feel free to use any of these methods as it best suits you. It’s best to reach out to the maintainer(s) in advance, though, to see if the contribution is likely to be accepted or not.
Additions or changes to the templates or translations should always be made on-wiki (see above), not sent as patches.
The code in this repository is released under the AGPL v3, the translations and templates under CC BY-SA 3.0. See the LICENSE file for details.