[6:00pm] GaborHojtsy: Sutharsan: wow, what computer meltdown
[6:01pm] GaborHojtsy: HI EVERYONE!
[6:01pm] YesCT: Hi
[6:01pm] das-peter: Hi
[6:01pm] Druplicon: sup
[6:01pm] Druplicon: ni hao
[6:02pm] aturetta: Hi
[6:02pm] Druplicon: eh oh
[6:02pm] plach: hey
[6:02pm] Druplicon: Hi! Did you clear your cache?
[6:02pm] andypost_ is now known as andypost.
[6:02pm] andypost joined the chat room.
[6:02pm] aturetta: druplicon LOL
[6:02pm] GaborHojtsy: LOL
[6:02pm] YesCT: Love that one.
[6:02pm] das-peter: LOL
[6:02pm] Sutharsan: GaborHojtsy: I enabled disk encryption and after that it did not boot again.
[6:03pm] GaborHojtsy: #1 so thanks everyone for working so hard, we need to keep ti up
[6:03pm] GaborHojtsy: Sutharsan: whups
[6:03pm] Sutharsan: GaborHojtsy: to I had an un-voluntary recovery test
[6:03pm] GaborHojtsy: Sutharsan: wow, glad it worked after all
[6:03pm] GaborHojtsy: so thanks reyero for working hard on the locale backend
[6:03pm] Sutharsan: GaborHojtsy: yep me too
[6:04pm] GaborHojtsy: thanks das-peter for hard work on the node property stuff
[6:04pm] GaborHojtsy: plach: for reviewing and the entity translation UI
[6:04pm] GaborHojtsy: YesCT: for all her detailed reviews
[6:04pm] GaborHojtsy: Sutharsan: for keeping up with the l10n_update stuff
[6:04pm] GaborHojtsy: attiks for detailed reviews and pushing for commits
[6:05pm] YesCT: People are rocking
[6:05pm] GaborHojtsy: vasi1186 for getting back to solutions
[6:05pm] GaborHojtsy: great work all around
[6:05pm] GaborHojtsy: #2 we have a freaking 7.5 weeks left, that was not a mistake, 7.5 weeks!
[6:06pm] GaborHojtsy: so keep it up and keep moving as fast as possible
[6:06pm] GaborHojtsy:
[6:06pm] GaborHojtsy: we have lots of features to get in and then we can/should continue refining them, but we need to have them in a state to be committable first
[6:07pm] GaborHojtsy: so that's it for the speech, in short you rock, keep rockin!!!!!
[6:07pm] plach:
[6:07pm] Sutharsan: Hurray!
[6:07pm] Druplicon: Woohoo!
[6:07pm] plach: I think I'll spleep for a week afte december 1st
[6:07pm] GaborHojtsy: any concrete topics people want to talk about?
[6:08pm] GaborHojtsy: plach: good plan
[6:08pm] plach: well, bojhan wanted to talk about the ET UI
[6:08pm] GaborHojtsy: plach: Bojhan not yet here
[6:08pm] plach: I can ping him
[6:08pm] GaborHojtsy:
[6:08pm] plach: he should be in #drupal-contribute
[6:08pm] YesCT: plach: Thanks for being patient with all my posts to the et ui
[6:08pm] aturetta: any news about #1746946
[6:08pm] plach: but let's keep that for later
[6:09pm] plach: YesCT: you're great!
[6:09pm] aturetta: I mean [#1746946]
[6:09pm] reyero: hi
[6:09pm] aturetta: [1746946]
[6:09pm] YesCT: plach: You too, you respond fast.
[6:10pm] andypost: 1746946
[6:10pm] Druplicon: http://drupal.org/node/1746946 => Write documentation on how localize.drupal.org works => Localize.drupal.org, Documentation, normal, active, 4 comments, 2 IRC mentions
[6:10pm] aturetta: ah ah ah
[6:10pm] plach: YesCT: just one small remark: if you could use blockquote when quoting people your reviews would be really really awesome
[6:10pm] YesCT: aturetta: Do it with just the num
[6:10pm] GaborHojtsy: aturetta: 1746946 is not related to this meeting, we are meeting on D8 multilingual issues
[6:10pm] GaborHojtsy: aturetta: sorry
[6:11pm] aturetta: ok, thank you
[6:11pm] YesCT: plach: Sure, I'll preface with their name too, so hard to keep track.
[6:11pm] das-peter: I'd like if we could try to figure out a "general" language logic I could apply to the queries in http://drupal.org/node/1498674 Just want to make sure not to do double work
[6:11pm] Druplicon: http://drupal.org/node/1498674 => Refactor node properties to multilingual => Drupal core, node system, major, needs work, 46 comments, 17 IRC mentions
[6:11pm] plach: well, if nobody has a better plan I'd like to speak of what we need th commit the ET UI stuff
[6:12pm] reyero: GaborHojtsy: I have some interest in talking about why the exception handling is not locale-safe (uses t in several places)
[6:13pm] GaborHojtsy: ok, so let's talk about reyero's topic then das-peter and if Bojhan shows up then plach's
[6:13pm] GaborHojtsy: reyero: I think its simply because in many cases exceptions might go to the screen, but they are not very predictably do so
[6:13pm] reyero: GaborHojtsy: and also about some standards for Exceptions because I see many of them are 'localized'
[6:13pm] fubhy joined the chat room.
[6:14pm] GaborHojtsy: reyero: so t() on exceptions is a question not whether it goes to the screen or not
[6:14pm] GaborHojtsy: reyero: since they should be generally general
[6:14pm] GaborHojtsy: reyero: they should theoretically not be t()-ed at all and the message should be t()-ed later
[6:14pm] reyero: But if the exception handling uses 't', then the installer / update / anywhere can trigger it
[6:14pm] GaborHojtsy: reyero: but then how does the rest pick up the exception text
[6:14pm] GaborHojtsy: reyero: andypost pinged me earlier about the same question in the date patch
[6:15pm] GaborHojtsy: reyero: and the answer was remove t() from exceptions because its a general API and they don't know where does the message go
[6:15pm] GaborHojtsy: reyero: if it goes to the watchdog/syslog, it should NOT be t()ed
[6:15pm] GaborHojtsy: reyero: because its stored in original form and t()ed later if possible
[6:16pm] GaborHojtsy: reyero: of course exceptions will not provide the kind of metadata level with replacement strings as watchdog would love to have so t()-ing them later might not be possible or litter the translatable strings with processed data
[6:16pm] GaborHojtsy: reyero: its messy because exceptions try to be general and then localisation needs to be so specific
[6:16pm] andypost: reyero: this about http://drupal.org/node/1802278#comment-6577330
[6:16pm] Druplicon: http://drupal.org/node/1802278 => Add a Date component to core => Drupal core, system.module, normal, needs review, 47 comments, 5 IRC mentions
[6:17pm] alexpott left the chat room. (Quit: alexpott)
[6:17pm] reyero: GaborHojtsy: The problem I'm seeing lately is one unrelated exception triggering in turn one locale exception because the locale system is just not loaded... so if we've got 'st' for a reason, I think we should insist on *all* exceptions being not localized
[6:17pm] mzgadzaj left the chat room. (Ping timeout: 252 seconds)
[6:17pm] andypost: reyero++
[6:17pm] reyero: It's really painful to debug and test the locale system
[6:17pm] andypost: reyero: but there's a big trouble with exceptions that comes from php
[6:18pm] attiks: why do you want t() te be used in exceptions, exceptions aren't meant to be displayed as is?
[6:18pm] GaborHojtsy: reyero: yeah, exceptions not being localised is probably the best approach
[6:18pm] andypost: reyero: they are depends on server's lcoale
[6:18pm] GaborHojtsy: andypost: that is not really possible to solve in Drupal though
[6:18pm] reyero: attiks: I *don't* want t() to be used on exceptions
[6:18pm] andypost: exactly
[6:19pm] andypost: so if there's consensus let's file an issue
[6:19pm] attiks: reyero++
[6:19pm] attiks: i got a review for breakpoint with the same remark: don't use t() inside exceptions, use format_string
[6:19pm] attiks: src http://drupal.org/node/1734642#comment-6569486
[6:19pm] Druplicon: http://drupal.org/node/1734642 => Move breakpoint module into core => Drupal core, other, normal, needs review, 120 comments, 9 IRC mentions
[6:19pm] reyero: Also I am seeing (testing) errors that shouldn't be there like An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=3&op=do_nojs&op=do StatusText: Internal Server Error ResponseText: A fatal error occurred: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'drupal8.simpletest575223locales_source' doesn't exist:
[6:20pm] andypost: also we could implement some special context for exceptions
[6:20pm] reyero: (that is a call to 't' which calls 'locale' when locale module is not installed but that may be a different issue
[6:20pm] GaborHojtsy: reyero: yeah, I think removing them is safer and most logical
[6:21pm] GaborHojtsy: on to das-peter's topic!
[6:21pm] GaborHojtsy: (checking time :D)
[6:21pm] das-peter: That was fast
[6:21pm] GaborHojtsy: das-peter: what kind of general logic do you need?
[6:21pm] reyero: so the point in summary: if exceptions can be thrown from the installer, they cannot be localized with 't' (And ideally no exception should be localized unless we have some kind of EndUserException)
[6:21pm] • attiks i got to go, dinner time
[6:21pm] GaborHojtsy: (well, we are into 1/3 of our meeting time and we'Ll likely have more topics as we go)
[6:21pm] das-peter: I wasn't able to write down a full summary in the meantime. But give me a second
[6:21pm] GaborHojtsy: reyero: right!
[6:22pm] reyero: So well, I will create an issue then, just wanted to know if anyone could tell me a good reason for the opposite
[6:22pm] q0rban is now known as qrbn.
[6:23pm] GaborHojtsy: reyero: no good reason
[6:23pm] rvilar left the chat room.
[6:23pm] das-peter: That's what I've so far: http://pastebin.com/2XKSXnVt
[6:24pm] Bojhan joined the chat room.
[6:24pm] GaborHojtsy: das-peter: I think plach would be the best to answer that
[6:24pm] GaborHojtsy: das-peter: the summary looks spot on yup
[6:25pm] • plach looks
[6:25pm] • Bojhan is here
[6:25pm] das-peter: If I have this information I'll make the changes so plach can review it later and has his mind free for other stuff in the meantime
[6:25pm] GaborHojtsy: Bojhan: we are in a topic right now and next up is the ET UI, will ping you, so feel free to zone out for a few minutes  hope you'll still be around then
[6:26pm] Bojhan: sure, just ping
[6:27pm] das-peter: plach: I can post this summary, if it's complete enough, into the issue, so we can work on that there and move on here.
[6:27pm] plach: das-peter: sorry, Ion the phone for 1 minute
[6:30pm] andypost: Also I'd like to open a question about translations for config entities
[6:30pm] andypost: currently in core we have config_test which looks like working with translations
[6:30pm] plach: das-peter: I think it depends on the use-cases
[6:31pm] plach: we need some examples to define a ruleset
[6:31pm] andypost: shold we postpone it till ETUI in core?
[6:31pm] plach: for instsnace ount queries can use a distinct clause
[6:31pm] plach: also queries selecting nids, probably most of the time can use a distinct
[6:32pm] plach: admi listings can probanly go with the default langauge (or the current content language?)
[6:32pm] andypost: actually I'd like to see contact categories commited to make real testing of entity translation
[6:32pm] GaborHojtsy: andypost: I don't think translatable config UI in core is feasible in Drupal 8, your help would be welcome in the other 3 outstanding issues that are in fact core blockers and not possible in contrib
[6:32pm] andypost: GaborHojtsy: which ines?
[6:33pm] plach: reyero: GaborHojtsy: what do you think about admin listings?
[6:33pm] plach: should they use the current content language or the default langauge?
[6:33pm] GaborHojtsy: plach: das-peter: yeah, admin listings would take the original language version first and foremost and if they provide a UI to filter for other languages, then it would take other languages
[6:33pm] andypost: GaborHojtsy: which 3 issues?
[6:33pm] plach: makes sense
[6:34pm] plach: I Have to go a bit eralier today
[6:34pm] plach: can we talk about the UI with Bojhan?
[6:34pm] GaborHojtsy: andypost: http://hojtsy.hu/d8mi/focus stuff marked with config langugae
[6:34pm] das-peter: plach: Could you write down these rules into the issue? I'll take care of implementing them then asap.
[6:35pm] reyero: plach: for i18n in admin listings we were disabling the language filter, but that's just an option
[6:35pm] GaborHojtsy: das-peter: looks like a copy-paste from here is your best bet
[6:35pm] reyero: plach: as long as you can see all the content - i.e. with a filter - that should work too
[6:36pm] GaborHojtsy: reyero: plach: yeah, if the UI has a filter, that would be best
[6:36pm] reyero: plach: but that would mean adding a language filter to *every* admin page
[6:36pm] GaborHojtsy: reyero: which might happen with views
[6:36pm] GaborHojtsy: all in all, many of these admin pages will hopefully be redone with views, so they will not be a concern, but they are not there yet
[6:37pm] GaborHojtsy: views committed sooner then our stuff causes problems because then we need to implement the node property handling in views
[6:37pm] GaborHojtsy: committed later makes us needing to adapt all those things
[6:37pm] GaborHojtsy: plach: Bojhan: let's talk ET UI then!
[6:37pm] • Bojhan shows hands
[6:38pm] • plach pasted stuff for das-peter
[6:38pm] das-peter: plach++
[6:38pm] plach: reyero: maybe using the value of the filter if there's one and fallback to the content language otherwise
[6:38pm] plach: ?
[6:39pm] plach: GaborHojtsy: exactly
[6:39pm] alexpott joined the chat room.
[6:40pm] plach: Bojhan: ok, so you are suggesting we should rework the workflow to enable multilingual support/translation to entity bundles, right?
[6:40pm] plach: for background, here is what D7 ET implements:
[6:40pm] Bojhan: plach: I am not suggesting we do that before comitting this
[6:41pm] plach: http://drupal.org/node/1188388#comment-6577880
[6:41pm] Druplicon: http://drupal.org/node/1188388 => Entity translation UI in core => Drupal core, entity system, critical, needs work, 109 comments, 15 IRC mentions
[6:41pm] plach: Bojhan: sure
[6:41pm] Bojhan: plach: But yes
[6:41pm] plach: but we have an issue open to generalize mutlitlingual settings for any entity
[6:41pm] YesCT: Bojhan: I was wondering about the ui gate in relation to feature freeze
[6:41pm] Bojhan: plach: I do not see it reasonable, that people go over all the different entities and find the magic checkbox to click
[6:41pm] plach: http://drupal.org/node/1739928
[6:41pm] Druplicon: http://drupal.org/node/1739928 => Generalize language configuration on content types to apply to terms and other entities => Drupal core, language system, normal, needs review, 125 comments, 50 IRC mentions
[6:41pm] Bojhan: YesCT: It does not exist basically, I have removed all quality control parts from the gate.
[6:42pm] plach: it might be good to know if we can take into account your feedback there or at least pave the way
[6:42pm] alexpott left the chat room. (Client Quit)
[6:42pm] Bojhan: hmm
[6:43pm] plach: Bojhan: so your point would be that most important use case is that one wishes to set-up stuff per-task (i.e. enable translation on my site) and not per-entity/bundle (i.e. configure my content type)
[6:43pm] Bojhan: plach: I already RTBC'd that.
[6:43pm] Bojhan: plach: Yhea,
[6:44pm] Bojhan: plach: Well they want to do both  But not in a disconnected workflow
[6:45pm] plach: Bojhan: that one basically goes on the way of making the per-bundle approach offical
[6:45pm] plach: Bojhan: which differences you envision wrt the screenshots i linked above?
[6:45pm] Haza` is now known as Haza`Aw.
[6:46pm] Bojhan: plach: Well, I think the contrib img you posted matchews what I thought
[6:46pm] andypost: plach, are you talking about 1739928?
[6:46pm] plach: andypost: yes
[6:47pm] plach: andypost: noope, sorry, http://drupal.org/node/1188388#comment-6577880
[6:47pm] Druplicon: http://drupal.org/node/1188388 => Entity translation UI in core => Drupal core, entity system, critical, needs work, 109 comments, 16 IRC mentions
[6:47pm] GaborHojtsy: Bojhan: yeah, so we should make it possible on a per entity level and then think about making it possible on a per task level later then?
[6:48pm] GaborHojtsy: Bojhan: almost all entity level things are now done on per entity, and I agree translations could use more of an overview settings screen
[6:48pm] GaborHojtsy: Bojhan: but configuring it per entity sounds like would be the first step (like comment settings or whatnot)
[6:48pm] Bojhan: GaborHojtsy: So basically I thought, the strategy was to do it perbundle. I am suprised to know plach is interested in providing a global workflow.
[6:48pm] Bojhan: GaborHojtsy: But yes, the logical flow would be to allow per/bundle, and then work on a global workflow solution
[6:48pm] andypost: plach: I scare that it would be hard task to disaplay all avaliable entities here
[6:49pm] tarzis left the chat room. (Ping timeout: 276 seconds)
[6:49pm] plach: Bojhan: well, it's not my top priority, but since that's the UI we have in D7, people might expect to find it also in D8
[6:49pm] andypost: plach:I'd prefere to something within entity configuration/listing
[6:50pm] plach: let me clarify that I just wish to follow Bojhan's directions, it's not something I totally wat to be done
[6:51pm] Bojhan: I dont´t know, its just my only concern. That we are making all this great stuff, but no one will know how to set it up. It´s been basically my concern with the overall goals.  incompatible encoding
[6:51pm] plach: well, it's abit diffcult to summarize a UI in one sentence, what about creating a follw-up of http://drupal.org/node/1739928 and post some screenshots/mockups there?
[6:51pm] Druplicon: http://drupal.org/node/1739928 => Generalize language configuration on content types to apply to terms and other entities => Drupal core, language system, normal, needs review, 125 comments, 51 IRC mentions
[6:51pm] plach: andypost: ^^
[6:51pm] plach: not sure what you mean
[6:51pm] Bojhan: It´s probally more viable to fix it in contrib, but that doesn´t mean its not a core problem. incompatible encoding
[6:52pm] andypost: plach: sure
[6:52pm] plach: Bojhan: if that's somehitng that can happen after December 1st, I think we can totally work on that
[6:52pm] plach: before it's a bit diffcult
[6:52pm] Bojhan: plach: I dunno, I have no idea what feature freeze really mean. But we can totally just say its a bug ±D incompatible encoding
[6:53pm] Bojhan:
[6:53pm] plach: might work
[6:53pm] andypost: core will be shipped with more then 10 different entities, some of them are content some config
[6:53pm] plach: sorry, guys, I really have to go now I'm ALREADY LATE+
[6:53pm] plach: i'LL READ THE LOG
[6:53pm] plach: ON GDO
[6:53pm] plach: BYE!
[6:53pm] Druplicon: I'll miss you!!
[6:53pm] plach left the chat room. (Quit: ChatZilla 0.9.89 [Firefox 15.0.1/20120905151427])
[6:54pm] YesCT:
[6:55pm] GaborHojtsy: Bojhan: as for my maintained understanding of feature freeze, we can refine the UIs and connect interactions, add relatively minor screens (eg. not a big new UI piece but some improvements to workflow, etc.) up until April 1st
[6:55pm] Bojhan: GaborHojtsy: yhea, but critical/major bugs are just solvable even if its big new ui. As far I know, thats the same as d7
[6:56pm] GaborHojtsy: Bojhan: so what we are trying to focus on now is to have all the features in with a sane UI and then come dec 1st, we return to the UI and will hopefully get people to sit down and try to use it and figure out the gaps with the existing features, and at that point we cannot really say there will be those 2 other features that are not there yet, we'll need to fix the holes
[6:56pm] Bojhan: GaborHojtsy: I am pretty sure if we do one test, we will find setupability of this is major-critical
[6:56pm] GaborHojtsy: Bojhan: cool
[6:56pm] GaborHojtsy: Bojhan: I definitely want to make it so there are tests of this as early as possible after Dec 1st
[6:56pm] Bojhan: GaborHojtsy: Yhea, I think I make it clear in my reviews. This stuff can go as is. We need appropiate followups, of which this is one
[6:57pm] GaborHojtsy: Bojhan: to refine and smooth the UIs of new and old things
[6:57pm] andypost: I can take a part in testing
[6:57pm] GaborHojtsy: Bojhan: cool
[6:58pm] GaborHojtsy: Bojhan: thanks for your support, and you should know we'll be even more in UX land come after dec 1st
[6:58pm] andypost: GaborHojtsy: also having current UI commited we get more reviews before 1dec
[6:58pm] GaborHojtsy: Bojhan: we are already probably the #1 UI changers in this release (so far)
[6:58pm] Bojhan: GaborHojtsy: hah, thats not very hard
[6:59pm] GaborHojtsy:
[6:59pm] Bojhan: I got pretty much 0 patches in for d8, hah
[6:59pm] GaborHojtsy: Bojhan: well, its not like the mobile or design or layout initiatives were not set up to bring in new and improved UIs
[6:59pm] YesCT: Bojhan: I can concur that your feedback has been helpful and clear that it is not blocking
[7:00pm] Bojhan: YesCT++
[7:00pm] Bojhan: YesCT: Thanks for your awesome reviews!
[7:00pm] GaborHojtsy:
[7:00pm] GaborHojtsy: ok, any other topics for today?
[7:01pm] alexpott joined the chat room.
[7:01pm] Sutharsan: dinner  bye all
[7:01pm] Sutharsan left the chat room. (Quit: Sutharsan)
[7:01pm] andypost: GaborHojtsy: translatable metadata yaml
[7:01pm] teknico left the chat room. (Remote host closed the connection)
[7:01pm] andypost: as I see it looks still as bikeshed
[7:02pm] GaborHojtsy: andypost: ah, great stuff, reyero would love reviews (not bike shed  on the topic
[7:02pm] andypost: but what kind of feedback
[7:03pm] das-peter: GaborHojtsy: I think I just found an issue with the path language prefix  - but that's a bug not a new feature. So it can wait, right?
[7:06pm] hairqles left the chat room. (Quit: hairqles)
[7:07pm] GaborHojtsy: andypost: well, whether it would work as a general solution (which is why we tried to pick views developer minds)
[7:07pm] andypost: GaborHojtsy: can you summarise the focus for translation of entities? what should be done first and what's last
[7:07pm] andypost: there's a lot of different issues - I think they should be reordered
[7:07pm] GaborHojtsy: andypost: we need the metadata to identify strings for l.d.o so when D8 ships, the shipped views, etc. can be translated
[7:07pm] GaborHojtsy: andypost: so is why http://drupal.org/node/1648930 is needed to mark data
[7:07pm] Druplicon: http://drupal.org/node/1648930 => Add metadata for configuration in YML files => Drupal core, configuration system, critical, needs work, 105 comments, 37 IRC mentions
[7:08pm] andypost: but this requires a fully functional pproperty api
[7:08pm] GaborHojtsy: andypost: and http://drupal.org/node/1777070 is needed for actually applying the translation
[7:08pm] Druplicon: http://drupal.org/node/1777070 => Translation workflow for configuration strings => Drupal core, configuration system, major, needs review, 9 comments, 11 IRC mentions
[7:08pm] andypost: which requires entityng
[7:08pm] andypost: which requires convertion patches for core entities...
[7:09pm] paulmarc joined the chat room.
[7:09pm] GaborHojtsy: andypost: no, conversions can happen after dec 1st
[7:09pm] GaborHojtsy: andypost: introducing these new features cannot
[7:09pm] GaborHojtsy: andypost: it would be great to have more entity conversions for test data, yup
[7:09pm] GaborHojtsy: andypost: but conversions have MONTHS, while we have 7.5 weeks for these features
[7:10pm] andypost: yes,
[7:10pm] GaborHojtsy: andypost: so those two issues for l.d.o / community translation integration are needed
[7:10pm] GaborHojtsy: andypost: and then we have no API right now to access specific language versions
[7:10pm] GaborHojtsy: andypost: so http://drupal.org/node/1763640 is needed
[7:10pm] Druplicon: http://drupal.org/node/1763640 => Add contextual data into Configuration Factory for localization, administration, etc... => Drupal core, configuration system, major, needs review, 9 comments, 4 IRC mentions
[7:10pm] GaborHojtsy: andypost: which gets the least traffic
[7:10pm] GaborHojtsy: andypost: so from the POV of D8MI-CMI we consider these the missing (and hopefully feasible implementable) features for D8
[7:11pm] andypost: last one makes more sense
[7:11pm] GaborHojtsy: andypost: a UI is totally out of question because it would need LOTS of more rework that is not possible in 7.5 weeks especially these 3 issues lingering
[7:11pm] andypost: actually we stll have no context all over core
[7:11pm] GaborHojtsy: andypost: yeah, we are not trying to resolve everything here for core either
[7:12pm] andypost: so it looks like a real plan
[7:12pm] GaborHojtsy: das-peter: make sure to file the bug, tag it D8MI
[7:12pm] GaborHojtsy: andypost: yeah, so these are the 3 issues we need and we have 7.5 weeks
[7:12pm] GaborHojtsy: andypost: we are not aiming at a UI at all in core because that would need a lot more stuff
[7:13pm] paulmarc left the chat room. (Client Quit)
[7:14pm] GaborHojtsy: UI as in config translation UI in core
[7:14pm] andypost: GaborHojtsy: thanx a lot! for me order should be - 1763640 1777070 1648930
[7:14pm] GaborHojtsy: it would need individual identification of what is translatable / multilingual of the values, so you would not edit your image resolutions for your image transforms, only the label of it
[7:15pm] GaborHojtsy: andypost: ok, so any review feedback in this order or any other order would be welcome
[7:15pm] GaborHojtsy: andypost: thanks!
[7:15pm] GaborHojtsy: I think this concludes our meeting
[7:15pm] GaborHojtsy: I need to go at least
[7:15pm] GaborHojtsy: feel free to chat around anyway, but I'll save this log and post it now