Adding new people to Lokalise using the web-based interface as requested (1 or 2 a month)
Ensuring there are no errors in translations that prevent language files from merging; there is a web-based interface for this (2-3 times a week)
Merging language files from Lokalise back into GitHub. This is currently done with a Python script—other alternatives may be possible...it is just how I've done it (2-3 times a week)
Configuring new GitHub repositories in Lokalise with the corresponding changes to a GitHub repository settings (1 or 2 a month)
Skills needed:
Scripting language...Python is used at the moment. Knowledge of GitHub webhooks is a bonus if the script needs to be rewritten.
Knowledge of internationalization formats (I've learned on the job)
He is being pulled in other directions and has asked for the community to identify a replacement. We are seeking volunteers. Peter reports that this takes roughly 2 hours per week. A call will go out to the councils and community (#folio-general).
Mike proposes pushing request out to community (PC, TC, other slack channels).
We want to take account for both the situation of an independent contractor or someone associated with an institution. In the latter case we need to account for institutional overhead which varies (Cornell is 37%, Stanford is 30-32%)
Mike Gorrell to refine the budget request and seek approval via Slack.
Architectural evolution will focus on Applications in FOLIO first. (Platform and authn/z will follow.) TC launching RFC process for app changes described at WOLFcon. TC subgroup to document non-technical requirements & implications for discussion in community. CC liaisons to effort to work with TC volunteers and PC liaisons on bringing this convo to fruition.