Attendees:
· Kaitlin, Jayanthy, Bikram, Sohaib, Amber (Scholars Portal)
· Gustavo, Michael, Phil (Harvard)
· Philipp (Norway)
· Juan (Spain)
Agenda:
Dataverse Language Packs repository - https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs
· Need to develop a workflow for updating from latest Harvard branch
· Discussion about synchronizing between repositories:
o First we need to be able to easily separate out all language files from the code in Harvard core
o Jayanthy to create a new issue to remove french and Chinese from Harvard core, and to move all English files into an en_US folder, etc.
o Then we can develop a workflow using Jenkins (hosted by SP) to automatically check for new Harvard release (or updates to develop branch, start with this first)
· ( Possible ) Jenkins workflow:
1. Automatically check for new releases and changes to the develop branch in Harvard
2. Whenever there is a change, update in Language Packs repository
3. Need to figure out if we can notify people in this workflow that there is something to translate (else, Harvard team might be able to create issues about changes to code indicating the line # and what changed)
4. If can’t automate the translators notifications, will investigate what can be done when changes are made to the code manually (creating issues)
· Could investigate using Github submodules as a means to coordinate this work as well
Documentation
· Improve README file in github to include list of languages, versions, and primary organization responsible w/ contact info
· Also include documentation on how to use these language files, (how to load them in Dataverse using new API call Jayanthy is developing)
· Cross-reference this documentation in the Harvard Guides (for installers), and on the Global Consortium page
Hosting and multilingual Dataverse
· Would be great to have a demo/test instance up with all the languages available to see / preview what a language would look like in the UI (helpful for promotion mostly, but possibly testing if maintained well enough)
· This could be just the latest code, deployed automatically (if it breaks it breaks) but new translations would need to be deployed manually by super admins.
Sustainability
· Need to consider who will be maintaining all of this, the repository, workflows, and translator – language responsibility, code developments, etc.
· Discussion to happen at Community Meeting in June with others about what resources could be dedicated to this
To dos:
· Jayanthy to create issue in Harvard core about bundling English files and removing other languages
· Bikram to investigate setting up Jenkins workflow for auto-syncing between the Harvard Dataverse repository and the Globus Language Packs repository
· Amber to talk to Slava about moving the DataverseEU languages over into this new language packs repository
· Jayanthy to review the Spanish translation and merge into latest branch for release
· Group to continue to investigate tools (perhaps ones that integrate with Github) to do comparisons, else, continue to discuss with Harvard about making issues that identify line items that have changed in the code for translators
· Amber to submit a talk about all of this for the Community Meeting
--
You received this message because you are subscribed to the Google Groups "Dataverse Internationalization Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-internationa...@googlegroups.com.
To post to this group, send email to dataverse-intern...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-internationalization-wg/d6ad29da-b327-4e52-aa23-541386676e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-internationalization-wg+unsub...@googlegroups.com.
To post to this group, send email to dataverse-internationalization-wg@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-internationalization-wg/d6ad29da-b327-4e52-aa23-541386676e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-internationa...@googlegroups.com.
To post to this group, send email to dataverse-intern...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-internationalization-wg/d6ad29da-b327-4e52-aa23-541386676e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Internationalization Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-internationa...@googlegroups.com.
To post to this group, send email to dataverse-intern...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-internationalization-wg/e594da75-f40f-4dcf-8589-a2b0f1a5dabf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.