Several tasks based on the experience from GAR, DecArch and SMVK-Mexiko uploads.
The idea is to have defined a set of *reasonable defaults* for a newcomer to help out with scripting of batch uploads to avoid
a) cognitive overload due to all options
b) quality issues due to lack of "safety net" built in human and technical sanity checks
c) waste of time due to lack of real milestones e.g. get GLAM engagement or external feedback
One simple way of doing this is to create one wikipage on Commons "introduction to batch uploads for beginner developers" with e.g:
[ ] Suggested developer setup: Pywikibot, Github account, phabricator account, Botaccount on Commons (with links to setups below)
[ ] Suggested setup of pywikibot (user-config.py in ~/.pywikibot with botaccount credentials
[ ] Suggested layout of a batch upload repo (dev-files, metadata as wik-formatted infotexts.json-file
[ ] Useful scripts for pywikibot based on suggested layout of batch upload repo
[ ] Suggested use of BatchUploadTools (pip install, the three most useful methods with code examples)
[ ] Suggested setup of a Phabricator project with projects, milestones, standard-tasks (that leaves room and place for non-standard events)
[ ] Suggested team collaboration sign-off to ensure the developer doesn't work alone and waste time/prioritize wrongly
[ ] Example workflow with handling maintanence tasks from mail, over Phabricator to review in Pull request, to reporting back to GLAM.