Skip to content

Instantly share code, notes, and snippets.

@zeke

zeke/Node.js i18n Working Group Meeting 2018.05.15.md

Created May 15, 2018 16:03
Show Gist options
  • Save zeke/6ab3b52bb1a1e1f45e7707cfc5a5753e to your computer and use it in GitHub Desktop.
Save zeke/6ab3b52bb1a1e1f45e7707cfc5a5753e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Node.js i18n Working Group Meeting 2018.05.15.md

Node.js i18n Working Group Meeting

2018.05.15

Planning board: https://github.com/nodejs/i18n/projects/1

Attendees

  • @zeke (GitHub on the Electron team, deals with i18n)
  • @obensource (InVision Dev Advocate, CommComm)
  • @RichardLitt (low resource language researcher)
  • @Vanessayuenn (Also on electron, i18n)
  • Andriy (CrowdIn)
  • Mikhailo (CrowdIn)
  • Tiago Danin
  • Dhruv Jain (Member of Website Redesign and i18n)
  • Tierney (DevAdvocate at Node Source, chair of CommComm)

Notes

Introductions

  • No notes really taken, some small notes put above

Agenda

  • continuous integration #58

  • Translation languages #70

  • Versions to Translate #71

  • website content to be translated #72

  • Set up the Crowdin-GitHub integration together, and record it #77

  • New project board #82

  • @Zeke: Let's get CrowdIn to a state where we can start translating NodeDocs

    • There are some blockers. We could do a high-level look at this...but maybe I should just dive in

  • CrowdIn: A localization management tool

    • Mikhailo and Andriy are both at Crowdin, here to talk about it
    • Project starts with project creation on the profile page, and you can set up integrations after

  • Collect latest major versions of node #83

    • @Zeke made a PR to use major versions instead of smaller versions, to make dedupelication earlier
    • node 9 is also EOL
    • soon we'll have node 11 and it will be active for a time, but will not have LTS
    • @zeke: anyone mind if we pull node 9? everyone: no.
    • Might be a good idea to push for node 11 as having translations (launch date: 10/31/2018)
    • For now, 6, 8, and 10 are good. We can turn on odd versions as needed
    • Odd versions never have an LTS, and run on a 6-month timecycle.
      • Might be a good idea to include this information in the README for new translators

< There was a 15 minute gap in documenting this meeting >

  • @dhruv: I will set up an issue for optimizing getting documentation, as I get time.

@dhruv: Could we move the docs to another repository to make it easier? @zeke: I'm not sure. Node has always had the docs in the same repo, and that has been essential to the success of the project, as any code will be in the same repo as the docs which need to be updated. I know this is hard for content collection, and any processes which could update this would be welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment