07:01:02 <eumel8> #startmeeting OpenStack I18n Meeting
07:01:03 <openstack> Meeting started Thu Mar 22 07:01:02 2018 UTC and is due to finish in 60 minutes.  The chair is eumel8. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:01:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:01:06 <openstack> The meeting name has been set to 'openstack_i18n_meeting'
07:08:52 <ianychoi> hi
07:11:26 <eumel8> hello :)
07:11:31 <ianychoi> :)
07:11:40 <eumel8> one attendee
07:11:52 <ianychoi> Me and you - two :)
07:11:54 <eumel8> welcome
07:12:21 <eumel8> tea? coffee?
07:12:45 <ianychoi> I like both, but now prefer to coffee since evening is coming
07:13:39 <eumel8> ah, true
07:13:56 <ianychoi> how about u? :)
07:14:03 <eumel8> I forgot it ;)
07:14:17 <eumel8> it's very early
07:14:27 <eumel8> and still snowing
07:14:31 <ianychoi> Wow..
07:14:49 <ianychoi> Seems strange March
07:15:00 <ianychoi> Yesterday there were snow here
07:15:24 <eumel8> I heard some rumors about Spring but nothing happen
07:16:24 <ianychoi> Haha
07:16:32 <eumel8> and I hate the new S release name ;)
07:16:40 <ianychoi> Hmm, Solar?
07:17:29 <eumel8> yes, it's the name of a bar
07:17:37 <eumel8> a little bit ... pixilated
07:17:50 <eumel8> http://www.solarberlin.com/
07:17:51 <ianychoi> Yep.. the next step is to consider legal issues, but I have no idea on that
07:19:02 <eumel8> Oracle has copyrights in the name because of the old operating system Solaris. Hopefully that will help to kill them.
07:19:14 <ianychoi> Haha :)
07:19:22 <ianychoi> By the way, is there agenda today?
07:19:37 <eumel8> ok, second name is Stein - also not better
07:19:47 <ianychoi> I don't like Stein
07:20:00 <eumel8> sure, as already we have an agenda, but you will hate it too ;)
07:20:14 <eumel8> #topic Project Doc translation
07:20:31 <ianychoi> Hmm,
07:21:08 <ianychoi> I have been still trying to contact with mordred but unfortunately I have failed.
07:21:37 <ianychoi> From my understanding, he implemented PTI (Project Testing Interface) and some doc build scripts
07:22:12 <eumel8> #link https://review.openstack.org/#/c/545377/
07:22:27 <eumel8> mhmm, okay
07:23:26 <ianychoi> IMO still it is worth merging this, but I think AJaeger wants to see more specific plans - how pot & po files will be associated with translated project doc build.
07:24:13 <ianychoi> Since eumel8 is also co-author on this, I would like to ask you to share your opinion on this.
07:25:00 <eumel8> I thought we were just about to finish. But it's true, we haven't the full picture yet
07:26:19 <ianychoi> Net spilts..
07:27:08 <eumel8> btw: a nice comment from clarkb in https://review.openstack.org/#/c/550814/
07:27:44 <eumel8> we should keep that in mind to move logical things out in project repos
07:28:06 <eumel8> it would be more de-centralized
07:28:59 <ianychoi> "should changes like this start going into repo specific config?"
07:29:08 <eumel8> yes
07:29:22 <ianychoi> eumel8, would you tell more on that? Seems that there are too many changes on projects.yaml file?
07:30:19 <eumel8> it was stable branch for tripleo-ui translation
07:32:05 <eumel8> as you can see in https://review.openstack.org/#/q/topic:translation-jobs-queens+(status:open+OR+status:merged) we had some proposals for new queens branches. Most of them are time critical for release. infra team can't support this anytime, so the idea would be the project team self is responsible for that.
07:32:29 <ianychoi> Aha..
07:32:43 <ianychoi> For that background, in my opinion, this kind of style: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-data
07:32:53 <ianychoi> - that might be what we need.
07:33:20 <eumel8> could be
07:33:23 <ianychoi> For example, creating project-data directory and enumerates the target of syncing projects in openstack/i18n repository
07:33:44 <ianychoi> Any kind of other idea on this?
07:34:45 <eumel8> ah, you mean openstack-manuals itself? interesting, because it's documentation and the targets for publishing are already there
07:36:21 <eumel8> My first thought was all of them are in project repos. But then we have many duplicate code in different versions
07:36:34 <ianychoi> What I meant is to migrate like all "translate-sync-queens" parts on projects from project-config/zuul.d/projects.yaml to like openstack/i18n/sync-target/projects.yaml
07:37:47 <eumel8> ah, got it. and where are the 3 shell scripts located for sync?
07:38:38 <ianychoi> For Documentation team, to make doc structure and doc content is for project teams, doc build scripts are in PTI (Python Testing Interface) by Infra & governance, and the visibility of docs.openstack.org is managed by Docs team.
07:39:05 <ianychoi> Somewhere in openstack-infra/project-config
07:40:01 <ianychoi> eumel8, what are "3" shell scripts?
07:40:06 <eumel8> it's in roles
07:41:42 <eumel8> https://docs.openstack.org/i18n/latest/infra.html#translation-infrastructure-tasks-and-scripts
07:42:08 <eumel8> I think the infra team is also not so happe with the current solution
07:42:20 <eumel8> if you read the comments in the playbooks ;)
07:42:40 <ianychoi> *.sh files in http://git.openstack.org/cgit/openstack-infra/project-config/tree/roles/prep-zanata/files ?
07:43:33 <ianychoi> I think staying the scripts in project-config is fine, but "defining translation targets - adding/removing" is managed mainly by I18n PTL.
07:43:52 <eumel8> yes, what we try to extend for project doc translation
07:44:22 <ianychoi> So now I think it would be nice if such defining can be accomplished in different repos and you + some core I18n members can have authority on the repo
07:44:59 <ianychoi> But.. doc builds are accomplished through just one script
07:46:18 <eumel8> yes, I think we have to think about that what are the best options. Will you answer the last comment from Andreas in https://review.openstack.org/#/c/545377/ ?
07:47:04 <ianychoi> "If you all find the existing name better, go for it..." ->this?
07:47:42 <ianychoi> My Workflow -1 is because of this part: "Please discuss with Monty about this, this might change how we build docs in a fundamental way and I like to see a written plan for this before we merge the first step."
07:48:21 <eumel8> ah, ok, have overseen that
07:49:25 <ianychoi> It would be so nice if you share your thoughts on the review.. :)
07:49:50 <eumel8> so think about the plan, make our own plan and then enter the infra team meeting could be an option.
07:50:15 <eumel8> my thoughts are not clear enough for the written context
07:50:25 <eumel8> ok, it's in the meeting protocol...
07:50:36 <eumel8> 10 min left, let's move on
07:50:39 <ianychoi> Yep
07:50:50 <eumel8> #topic Zanata upgrade status
07:51:10 <eumel8> so, we have the new Zanata in place since few weeks
07:51:26 <ianychoi> Great :)
07:51:34 <eumel8> I couldn't found any issues without the dangerous button in the user settings
07:51:54 <ianychoi> I might have been worried about this too much..
07:52:06 <ianychoi> But if there would be some issues, it might be out of control
07:52:10 <eumel8> it has a good performance and it works quiet well
07:52:28 <ianychoi> :)
07:52:30 <eumel8> sure, your request was valid
07:52:50 <ianychoi> Then what can we do much nice things after Zanata upgrade?
07:53:09 <eumel8> for the next upgrade we need to merge #link https://review.openstack.org/#/c/531809/
07:53:45 <eumel8> there are no zip files anymore to download and I understood the zanata guys wrong because I removed all that code in the past
07:54:34 <ianychoi> I will look at this review :)
07:54:43 <eumel8> but at the moment I think we are fine with that version
07:54:46 <ianychoi> (although I cannot give detail comments)
07:55:17 <eumel8> new feature would be API access to branch changes (set read-only) but I didn't test it yet
07:55:45 <ianychoi> Aha.. it would be nice if it works well :)
07:55:52 <eumel8> so, I have still one topic
07:55:55 <eumel8> #topic Open Discussion
07:56:02 <ianychoi> Yep..
07:56:59 <eumel8> ianychoi: what about your Vancouver trip? Question was if we can write your name on the speaker list for the Onboarding session :)
07:57:22 <ianychoi> eumel8, it would be so nice if you would put my name first :)
07:57:49 <eumel8> alright, sir!
07:58:05 <ianychoi> pkovar will attend? Or still not sure?
07:58:14 <eumel8> ianychoi: and you need additional support like a ticket code?
07:58:22 <eumel8> pkovar is still unsure
07:58:33 <ianychoi> eumel8, oh kind of full support?
07:58:38 <ianychoi> eumel8, thanks a lot!
07:59:03 <eumel8> as a speaker? I think so
07:59:10 <ianychoi> +1 :)
07:59:16 <eumel8> alright
07:59:24 <eumel8> thx
07:59:27 <eumel8> #endmeeting