To avoid outdated Banner code on meta and to work with our developer tools we need a software to synchronize the GitHub banner code repository with the JS pages on meta.
Requirements/Constraints:
- We don't want a special user on meta,- Editing banners on meta has heavy security constrains, allowing an automated user to deploy code would have to have the same permission scruity for all banner authors that members of the CN group have, Since this is a major process, the MVP is to automate repetitive steps of banner creation and deployment. cChanges mustes to banners and campaigns will then be "edit"ed" by each developer with his own credentials
- We only want to change files on meta that have changed during a commit.
A possible workflow could look like this:
# When code is commited to GitHub, a webhook is called.
# The WebHook sends a notification to the WMDE Fun team with a specially crafted link that will deploy these changes.
# When a member of the WMDE Fun team clicks on the link, it sees a list of files that will be uploaded and form fields for username and password on metaNotes for the estimation and viability:
# When the form is submitted,Creating a campaign and 2 banners takes about 5 minutes for an experienced developer. Add 2 more minutes for revising the banners (copying the code for the new banner version) after the first feedback loop. At ~50 campaigns during campaign season this makes for ~6 hours of banner update time during campaign season. theSetting up/developing software uses the credentials to post the changed files to metafor banner deployment should not take longer than those 6 hours.