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/tasks (["As a rule of thumb, limit High priority task assignments for a single person to three, five in exceptional times."](https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities)
b) quality issues due to lack of "safety net" built in human and technical sanity checks
c) waste of time/energy due to lack of real milestones e.g. get GLAM engagement or external feedback
A simple way of adressing all of the above at the same time is to re-work how we use Phabricator for [agile](https://en.wikipedia.org/wiki/Iterative_and_incremental_development#/media/File:Agile_Project_Management_by_Planbox.png) [iterative development](https://en.wikipedia.org/wiki/Iterative_and_incremental_development):
[ ] Use subprojects/milestones with tag release for an iteration (e.g. get mapping tables, example images etc to users) to de-clutter?
[ ] Decide on form for code review (Github/Diffusion?) to avoid solo-work and ad hoc, stressful feedback e.g. tag patch-for-review?
[ ] Have regular sprint/iteration meetings to decide on closing of possible never-ending tasks such as maintanence for old batchuploads
[ ] Daily standup meetings? Who should participate?
Another simple way of doing this is to create one wikipage on Commons "introduction to batch uploads for beginners" 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 (license, folders, metadata as wik-formatted infotexts.json-file etc)
[ ] 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 use of Phabricator (see [mediawiki phabricator help](https://www.mediawiki.org/wiki/Phabricator/Help) and [phabricator project management](https://www.mediawiki.org/wiki/Phabricator/Project_management))
[ ] 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.