[6:00pm] GaborHojtsy: WELCOME everyone to the D8MI meeting! who is here for the meeting?
[6:00pm] ricardoamaro: me
[6:01pm] plach: me
[6:02pm] GaborHojtsy: reyero: YesCT, andypost ?
[6:02pm] YesCT: GaborHojtsy: here!
[6:02pm] YesCT: plach: hi.
[6:02pm] plach: hi
[6:02pm] YesCT:
[6:02pm] GaborHojtsy: cool
[6:02pm] GaborHojtsy: so I only have a few things
[6:03pm] GaborHojtsy: first off HUGE CONGRATS to reyero for having the locale-schema integration patch in
[6:03pm] tanarurkerem_ joined the chat room.
[6:03pm] plach: reyero: ++
[6:03pm] • andypost here
[6:03pm] ricardoamaro: clap clap
[6:03pm] vijaycs85 joined the chat room.
[6:03pm] andypost: reyero++
[6:03pm] York is now known as york.
[6:03pm] GaborHojtsy: its the whole reason we had the schema system fought into Drupal 8, the config event subscribers and overrides… so its 3 new systems we (and I mean reyero) integrated with locale (the 4th system)
[6:03pm] GaborHojtsy: reyero++
[6:03pm] GaborHojtsy: reyero++
[6:04pm] GaborHojtsy: so finally it all makes sense
[6:04pm] plach: GaborHojtsy++
[6:04pm] mzgadzaj left the chat room. (Remote host closed the connection)
[6:04pm] ricardoamaro: reyero++
[6:04pm] vijaycs85: .
[6:04pm] GaborHojtsy: also huge congrats to vijaycs85 for working through most of the schema stuff, we have field module related stuff right now but almost everything is covered
[6:04pm] andypost: just need to finish http://drupal.org/node/1818574
[6:04pm] GaborHojtsy: vijaycs85++
[6:04pm] Druplicon: http://drupal.org/node/1818574 => #1818574: Convert config entities to the new Entity Field API => Drupal core, configuration system, major, needs review, 26 comments, 19 IRC mentions
[6:05pm] YesCT: GaborHojtsy++
[6:05pm] YesCT: reyero++
[6:05pm] YesCT: vijaycs85++
[6:05pm] vijaycs85:
[6:05pm] plach: vijaycs85++
[6:05pm] ricardoamaro: vijaycs85++
[6:05pm] ricardoamaro: GaborHojtsy++
[6:05pm] GaborHojtsy: so while we are working on the schemas and more locale stuff, the real big elephant in the room are all the content (lacking NG level state) and properties
[6:05pm] ricardoamaro: so much karma flowing
[6:06pm] GaborHojtsy: we have a board about that at http://www.drupal8multilingual.org/issues/content-property
[6:06pm] GaborHojtsy: if I did not properly identify issues for that, please help with tagging
[6:06pm] tanarurkerem left the chat room. (Ping timeout: 256 seconds)
[6:06pm] GaborHojtsy: I used the D8MI + language-content-property tag combo for this board
[6:06pm] YesCT: vijaycs85: is doing core mentoring office hours right now too
[6:06pm] GaborHojtsy: vijaycs85
[6:07pm] GaborHojtsy: so andypost I think http://www.drupal8multilingual.org/issues/content-property should give you a fuller picture as to what are in our plans for more content language support
[6:07pm] andypost: GaborHojtsy, about comment drupal.org/node/731724 fighting with last test failures
[6:07pm] tanarurkerem_ left the chat room. (Ping timeout: 248 seconds)
[6:07pm] GaborHojtsy: that is where menu label translation, node title translation, taxonomy term translation, etc. lies
[6:08pm] plach: hope to be donw with the node issue in the next days
[6:08pm] GaborHojtsy: andypost: ok
[6:08pm] plach: * done
[6:08pm] vijaycs85: GaborHojtsy: YesCT   yeah... I have initiated few mail threads on COH at my office (around 30+ drupalers)
[6:08pm] GaborHojtsy: plach:      #jumpingaround
[6:08pm] GaborHojtsy: vijaycs85: woot
[6:08pm] andypost: plach, hwo much this depends on NG ?
[6:08pm] GaborHojtsy: I've also seen reyero found some partners in crime for the DiC issues which is amazing
[6:08pm] plach: I think we need to fix queries to support ML properties and then we should ready to go
[6:09pm] andypost: plach, entity_query you mean?
[6:09pm] vijaycs85: GaborHojtsy: yeah, its getting better day by day.. got a code sprint sponsored by d.o. association this weekend.. 12 signed up already
[6:10pm] plach: andypost: since we have the BC decorator in place NG is not a hard requirement in most cases, although having NG completed and http://drupal.org/node/1810370 done will be requisites to have full node translation working
[6:10pm] Druplicon: http://drupal.org/node/1810370 => #1810370: Entity Translation API improvements => Drupal core, entity system, major, postponed, 41 comments, 4 IRC mentions
[6:10pm] GaborHojtsy: YesCT: vijaycs85: https://drupal.org/node/1813762#comment-7335894 needs a code style review pass, if you can find someone for that, it would be fabulous
[6:10pm] Druplicon: https://drupal.org/node/1813762 => #1813762: Introduce unified interfaces, use dependency injection for interface translation => Drupal core, locale.module, normal, needs review, 81 comments, 19 IRC mentions
[6:10pm] vijaycs85: GaborHojtsy: will have to check with YesCT on defect list  for it
[6:10pm] plach: andypost: nope, just make them work with ML properties
[6:10pm] plach: efq2 stuff will be a follow-up, so that we can benchamr them separately
[6:10pm] plach: * benchmark
[6:11pm] GaborHojtsy: plach: good plan on that
[6:11pm] andypost: plach, so maybe just describe langcode properties to allow handle 'em as native?
[6:11pm] plach: GaborHojtsy: I'd love to have a look to that one, but I feel confined to ml nodes
[6:12pm] GaborHojtsy: plach: yeah, we can find someone else
[6:12pm] GaborHojtsy: I also pinged it to catch for any architecture issues
[6:12pm] GaborHojtsy: and then the final announcement I wanted to make is the Portland sprints (again
[6:12pm] GaborHojtsy: http://groups.drupal.org/node/281033
[6:12pm] Druplicon: http://groups.drupal.org/node/281033 => Extended sprints around DrupalCon Portland => 4 comments, 14 IRC mentions
[6:13pm] GaborHojtsy: those who have details there, please review and see if it changed in the meantime (yes/no)
[6:13pm] GaborHojtsy: we are attempting to ensure we have enough space, and that looks ok for now
[6:13pm] plach: GaborHojtsy: yep, I did too, I got an answer: https://twitter.com/catch56/status/326706765326602242
[6:13pm] GaborHojtsy: also if you are sprinting remote, please do like vijaycs85 and put in when you likely be available as remote
[6:13pm] GaborHojtsy: so we can loop you in on discussions, schedule hangouts if that is helpful or whatnot
[6:13pm] GaborHojtsy: if you know remote availability times
[6:13pm] jcisio is now known as jcisio|aw.
[6:13pm] plach: andypost: not sure I get what you mean, all node properties are already descibed as fields
[6:14pm] GaborHojtsy: reyero: plach: especially you ^^^^^^
[6:14pm] YesCT: vijaycs85: I'm up for looking at code style.
[6:14pm] GaborHojtsy: plach: I agree with catch on type I imagined we can use the data table only for multilingual scenarios, we can avoid extra joins
[6:15pm] GaborHojtsy: all right, so those were my agenda items
[6:16pm] GaborHojtsy: anybody has items to discuss, so we can line them up for discussion (just mention what you want to discuss and then we can go through)  ?
[6:16pm] plach: GaborHojtsy: my secret plan is being able to make the storage controller engine able to switch between monolingual and multilingual schema, but not sure I will be able to accomplish it
[6:17pm] GaborHojtsy: plach: yeah we have 2 months only
[6:17pm] plach: GaborHojtsy: yeah, will have to make choices
[6:17pm] ricardoamaro: i would like to grab some work that you guys find useful and do it
[6:17pm] amateescu left the chat room. (Quit: Leaving)
[6:17pm] plach: ricardoamaro: cool
[6:18pm] plach: ricardoamaro: what would you ike to work on?
[6:18pm] GaborHojtsy: I think we want to prioritise terms and menus (users, comments and other thingies not having translatable properties we can kind of live with I guess if we need to)
[6:18pm] GaborHojtsy: of course if we have time….
[6:18pm] ricardoamaro: is there something that is pending some love from the current tasks?
[6:18pm] plach: GaborHojtsy: I'd like to lay out a plan for those conversions
[6:19pm] YesCT: ricardoamaro: the sprint tag gives us the focus issues.
[6:19pm] YesCT: http://www.drupal8multilingual.org/issues/focus
[6:19pm] GaborHojtsy: plach: I'm kind of concerned in this area because of the "slow" progress with the NG conversions and because it is frankly just hard  likely the rest of the entities are not as hard as nodes
[6:19pm] GaborHojtsy: plach: also performance
[6:19pm] ricardoamaro: thanks YesCT
[6:20pm] plach: GaborHojtsy: I agree, but the node issue won't just serve as a pilot
[6:20pm] GaborHojtsy: plach: hum?
[6:20pm] plach: GaborHojtsy: it actually fixed stuff in the node controller
[6:20pm] GaborHojtsy: ricardoamaro: I'm not sure about the complexity of the issues you are looking for
[6:20pm] YesCT: ricardoamaro: those are our "hurry!" issues.
[6:20pm] plach: sorry, in the storage controller
[6:20pm] YesCT: ricardoamaro: and they each have different tasks for just about any skill set.
[6:20pm] plach: GaborHojtsy: that was one of the trickie issues
[6:20pm] GaborHojtsy: ricardoamaro: we have some relatively simpler ones that we found recently if you want to start slower
[6:20pm] Haza` is now known as Haza`Aw.
[6:20pm] ricardoamaro: GaborHojtsy: neither do i
[6:20pm] YesCT: some need manual testing, some need code style review, some need a new patch
[6:21pm] plach: the rest of the conversion issues should be more straightforwards
[6:21pm] ricardoamaro: but at least i can see the crits
[6:21pm] plach: GaborHojtsy: ^^
[6:21pm] ricardoamaro: GaborHojtsy: yes
[6:21pm] ricardoamaro: agreed
[6:21pm] GaborHojtsy: plach: ok, if this worked out the issues
[6:21pm] andypost: I think we should finalize solution for http://drupal.org/node/1977784
[6:21pm] Druplicon: http://drupal.org/node/1977784 => #1977784: Content language settings configuration page needs to determine what entities and bundles to include => Drupal core, translation_entity.module, normal, needs work, 31 comments, 4 IRC mentions
[6:21pm] GaborHojtsy: andypost: I think we have a plan in my last comment
[6:21pm] YesCT: ricardoamaro: and on the front page of the multilingual site, there are other classifications to help find some things to do: http://screencast.com/t/8IVrzj45g
[6:21pm] plach: GaborHojtsy: hopefully yes
[6:22pm] GaborHojtsy: hopefully we can achieve this quick and then move on to adding language support on menus
[6:22pm] GaborHojtsy: ricardoamaro: eg. http://drupal.org/node/1974040 is a simple one from the "medium" board
[6:22pm] Druplicon: http://drupal.org/node/1974040 => #1974040: When choosing Arabic in the installer, the installer is not RTL => Drupal core, install system, normal, active, 0 comments, 4 IRC mentions
[6:22pm] plach: GaborHojtsy: one thing that I had no time to post on that issue is that also the old properties should appear there
[6:23pm] ricardoamaro: GaborHojtsy: got it
[6:23pm] GaborHojtsy: plach: well, eventually
[6:23pm] andypost: GaborHojtsy, I still dont get why we need translatable key in entity
[6:23pm] ricardoamaro: YesCT: will watch
[6:23pm] plach: yes, once the NG migration is over fieldability will no longer be a criterium to filter stuff out
[6:24pm] n3or joined the chat room.
[6:24pm] aries_mwz joined the chat room.
[6:24pm] YesCT: GaborHojtsy: did the one about theming the language selector get fixed?
[6:24pm] plach: GaborHojtsy: anyway, if you think we should have separate properties for langauge support and translation that's fine with me, I'm not feeling strong on this, I just had the impression that the current state was being misunderstood
[6:25pm] plach: GaborHojtsy: I already wanted to rename the translatable key with the field ones
[6:25pm] plach: to something more prper
[6:26pm] andypost: plach, your plan about storage controller - to swap it or implement additional?
[6:26pm] andypost: plach, have you seen chx sandbox to refactor entity-attach to events?
[6:27pm] GaborHojtsy: YesCT: no (theming)
[6:27pm] YesCT: ricardoamaro: here it is. http://drupal.org/node/1498880
[6:27pm] plach: andypost: not yet, but I know the plan in http://drupal.org/node/1497374 is to provide a separate SQL storage helper class
[6:27pm] Druplicon: http://drupal.org/node/1498880 => #1498880: Theme language switcher for seven theme => Drupal core, language.module, normal, needs work, 33 comments, 13 IRC mentions
[6:27pm] Druplicon: http://drupal.org/node/1497374 => #1497374: Switch from Field-based storage to Entity-based storage => Drupal core, entity system, major, active, 53 comments, 25 IRC mentions
[6:27pm] • ricardoamaro reads
[6:27pm] n3or left the chat room. (Client Quit)
[6:27pm] YesCT: ricardoamaro: so you should have your pick.
[6:27pm] GaborHojtsy: plach: I think its kind of a mess we need to make sense of either way
[6:27pm] ricardoamaro: ok
[6:27pm] plach: andypost: I'd like to provde different implementation of the SQL storage helper based on the base/rev/mul/mulrev scenarios and implement some  migration code among them
[6:27pm] ricardoamaro: this enough to get started there
[6:27pm] YesCT: ricardoamaro: make a comment on the one that looks like you want to work on it, and we'll keep an eye on it to make sure any questions you have get answered.
[6:28pm] andypost: plach, so maybe join forces on it and implement mono/lingual switch on it
[6:28pm] webflo1 joined the chat room.
[6:28pm] ricardoamaro: thanks YesCT, GaborHojtsy
[6:28pm] GaborHojtsy: plach: there are files, which have a langcode on them, but really take their language from the node they get attached to I think (or they should), not globally set up like our language defaults… so not sure if they should show up in this UI
[6:28pm] webflo left the chat room. (Read error: Operation timed out)
[6:28pm] andypost: plach, so I very pedantic about translatable as annotation
[6:28pm] plach: andypost: I totally wanted to, but I need to complete ml nodes first
[6:28pm] GaborHojtsy: plach: then I don't think files would need any properties translated, their labels and alt text is with the field not the file entity
[6:28pm] GaborHojtsy: at least as long as there are no fields
[6:29pm] plach: GaborHojtsy:  in D7 we use file entity translation to translate title and alt fields
[6:29pm] andypost: GaborHojtsy, this properties could use translation
[6:29pm] GaborHojtsy: plach: yeah but file entities don't have those things
[6:29pm] plach: ah ok, missing the last line
[6:30pm] ricardoamaro: YesCT++
[6:30pm] rteijeiro left the chat room. (Remote host closed the connection)
[6:30pm] plach: GaborHojtsy: I'm ok with having files out of the content language settings in core, D8 file entity can alter the entity keys and make them transltable
[6:30pm] GaborHojtsy: files have fid, uuid, uid, filename, uri, langcode, filemime, filesize, status, timestamp
[6:30pm] andypost: GaborHojtsy, plach from the pov entity field api there's no difference between field and property
[6:30pm] plach: or langauge-aware
[6:30pm] GaborHojtsy: that is no textual output that would be different by human language
[6:31pm] andypost: GaborHojtsy, timestamp depends on locale
[6:32pm] GaborHojtsy: file FIELDS have a description and then image fields have a title and an alt text
[6:32pm] plach: GaborHojtsy: yes, if we exclude the possibility of having stuff like uri or status vary by language, there is no point of support ml files in core
[6:32pm] andypost: * for output at least
[6:32pm] GaborHojtsy: andypost: that does not make storage require language variance
[6:32pm] plach: but I think we should allow for contrib to enhance them as File entity is doing in D7
[6:32pm] GaborHojtsy: plach: yeah, ok, but we want to make it possible to track language of files
[6:32pm] GaborHojtsy: plach: so that sounds like a core example where the entity has language support but is neither multilingual neither translatable
[6:33pm] GaborHojtsy: it is at max multilingual if you take a group of them, not any one of them
[6:33pm] GaborHojtsy: plach: yeah, contrib, yeah
[6:33pm] GaborHojtsy: plach: what I'm saying is the default core behaviour is they have language support but no multilingual
[6:33pm] GaborHojtsy: plach: so in your definition there is no way to express this, right?
[6:34pm] GaborHojtsy: in fact you want to avoid this so the transition is seamless if someone ever wants to move from one to the other
[6:35pm] GaborHojtsy: so I think files are tricky, because they don't really have a place to be uploaded individually
[6:35pm] GaborHojtsy: without them coming from another entity
[6:35pm] andypost: GaborHojtsy, so anyway file entity needs default language definition
[6:35pm] GaborHojtsy: andypost: yeah my point
[6:35pm] plach: GaborHojtsy: yep, that sounds as a good use case for separate entity keys
[6:35pm] andypost: and once other fields are added they should have translatable definition
[6:36pm] GaborHojtsy: plach: yeah I can also imagine a contrib entity with similar characteristics
[6:36pm] plach: GaborHojtsy: although translation depends also on the ability to attach a UI and if files have no UI then you cannot translate them anyway
[6:36pm] GaborHojtsy: plach: yeah not right now, right
[6:36pm] andypost: plach, there's feeds & migrate too
[6:36pm] GaborHojtsy: plach: which gets us to my other dilemma
[6:36pm] GaborHojtsy: we can include them in this content config table
[6:37pm] GaborHojtsy: but whatever is configured there will not make sense
[6:37pm] GaborHojtsy: even for default language
[6:37pm] GaborHojtsy: because files always get created via another entity, and they get that language (I assume/hope)
[6:37pm] GaborHojtsy: so files are a goddam bad edge case
[6:37pm] plach: GaborHojtsy: what about adding a filter checking if there is an edit operation available once we have an entity operation API?
[6:38pm] andypost: GaborHojtsy, also they get default language when bulk imported
[6:38pm] GaborHojtsy: plach: yeah that makes sense
[6:38pm] • andypost thoughts bout REST import
[6:38pm] GaborHojtsy: andypost: yup
[6:38pm] aries_mwz left the chat room. (Quit: Leaving.)
[6:38pm] Sutharsan left the chat room. (Quit: Sutharsan)
[6:38pm] enzolutions left the chat room. (Remote host closed the connection)
[6:39pm] plach: GaborHojtsy: that would probably make separate keys unnecessary
[6:39pm] andypost: plach, I dont think operations api would be ready for jl1
[6:39pm] GaborHojtsy: LOL
[6:39pm] plach: GaborHojtsy: but I won't insist on this
[6:39pm] GaborHojtsy: plach: yeah which is why I said we can use this key for now although its name is a lie
[6:39pm] plach: andypost: we need something, even very basci
[6:39pm] plach: * basic
[6:40pm] plach: but we cannot simply ship with the current mess
[6:40pm] GaborHojtsy: people were surprised on the menu bundle issue that we put in a translatable key even there is nothing translatable
[6:40pm] jibran left the chat room. (Ping timeout: 252 seconds)
[6:40pm] plach: I'll file a critical bug report about that if there is no other way to get those changes in
[6:40pm] andypost: plach, we can operate on form controllers for entitties
[6:40pm] GaborHojtsy: I don't want to overtake this issue for renaming the property from translatable though
[6:41pm] plach: GaborHojtsy: title link?
[6:41pm] plach: sorry: menu link title?
[6:41pm] GaborHojtsy: yeah once it becomes a multilingual property
[6:41pm] plach: andypost: for hthis particular use case might work, but in general there is very messy stuff around
[6:42pm] GaborHojtsy: so I think for now "translatable" is fine condition to filter for which entity types appear in the content table, and we check for field ability AND the presence of fields for the translation checkbox
[6:42pm] GaborHojtsy: like I said not he issue
[6:42pm] GaborHojtsy: on the issue
[6:42pm] GaborHojtsy: so if an entity type is translatable but not field able OR has no fields, it gets language setup support but no translation setup support
[6:42pm] plach: GaborHojtsy: I'm wondering whether it would make sense to focus on http://drupal.org/node/1497374 as andypost  was suggesting
[6:42pm] Druplicon: http://drupal.org/node/1497374 => #1497374: Switch from Field-based storage to Entity-based storage => Drupal core, entity system, major, active, 53 comments, 26 IRC mentions
[6:42pm] plach: after ML properties are done
[6:43pm] plach: if we get that one in soon, it might be way easier to complete the other conversions for all content entities
[6:43pm] andypost: GaborHojtsy, yes for now, but for final we need sane way to decide on multilingual/translatability
[6:43pm] jibran joined the chat room.
[6:43pm] GaborHojtsy: plach: yeah I don't know… I don't want us to fall between two chairs on the floor
[6:44pm] andypost: 1.1) entity have langcode definition - multilingual
[6:44pm] GaborHojtsy: andypost: well, theoretically most entities will have translatable properties so they can be multilingual
[6:44pm] plach: GaborHojtsy: I know there is this risk but I think it's worth
[6:44pm] andypost: 1.2) no langcode so check translation handlers
[6:44pm] GaborHojtsy: andypost: the translatable property would be to say "this entity type has bundles that CAN BE multilingual if configured that way"
[6:44pm] plach: if we get that one right we'll have ML support for free for every content entity out there
[6:45pm] andypost: GaborHojtsy, i'd like to get rid of bundle-way to localization
[6:45pm] rvilar left the chat room. (Remote host closed the connection)
[6:45pm] GaborHojtsy: plach: it would need serious community support
[6:45pm] andypost: plach, agreed exactly
[6:45pm] GaborHojtsy: plach: it does not have a patch newer than 13 months old
[6:46pm] plach: GaborHojtsy: chx is working on it and I'd like to do it too, once I'm done with nodes
[6:46pm] GaborHojtsy: andypost: I think its a good feature that I can make a menu translatable while not another; same for node types, etc.
[6:46pm] andypost: once we get attach_language event or something on entity level that changes a picture
[6:47pm] andypost: this allows to inject whole-configurable languge_element all over core
[6:47pm] floretan left the chat room. (Remote host closed the connection)
[6:48pm] plach: I think a final disclaimer for an entity type to *appear* in the settings page is "it is language-aware (entity key) and has a create/edit operation"
[6:49pm] plach: for translation the additional conditions would be the presence of a data table (automatic if we get the storage issue done)
[6:49pm] GaborHojtsy: plach: yeah we can adapt there
[6:49pm] plach: and perhaps a specific transltable entity key
[6:49pm] andypost: plach, is not it enough to check that entity have create() and save() method? why "operations"
[6:50pm] plach: well, actually the default language setting apply even if the entity type has no UI...
[6:51pm] plach: so perhaps the UI disclaimer should be applied onlt to the language-selector setting
[6:51pm] plach: (hde/show)
[6:51pm] andypost: sure
[6:51pm] plach: I'm thinking to hook_entity_create() and Language module integration issue
[6:52pm] plach: http://drupal.org/node/1966436
[6:52pm] Druplicon: http://drupal.org/node/1966436 => #1966436: Language module should use hook_entity_create() to set default language => Drupal core, language.module, normal, needs work, 11 comments, 1 IRC mention
[6:52pm] plach: GaborHojtsy: so perhaps file *should* appear in the settongs page after all
[6:52pm] andypost: plach, some cleanup could be possible after july but I think form controller injection should be enough
[6:53pm] GaborHojtsy: plach: yeah it would be interesting that some entities don't have a show/hide checkbox, others have that but no translation checkbox
[6:53pm] plach: andypost: do you mean enough to determine whether a UI is available?
[6:53pm] GaborHojtsy: looks very appropriate and at the same time confusing
[6:53pm] andypost: plach, yep
[6:53pm] plach: andypost: yep, probably
[6:54pm] andypost: there's some tiny issues sometimes but solvable
[6:54pm] plach: GaborHojtsy: well,I find confusing that we have nothing in core like file entity and media, but that's not our fault
[6:54pm] plach: maybe contrib will help ensuring consistency
[6:54pm] GaborHojtsy: plach: yeah that is true
[6:55pm] plach: GaborHojtsy: anyway I'm totally open to any solution that is deemed more appropriate here, no strong feeling
[6:55pm] andypost: form controller is exactly the place where entities created or edited. also delete-confirm conversion mostly over
[6:56pm] andypost: and d8mi mostly have controllable way to detect delete
[6:57pm] YesCT: I'll need a recap once it seems you have a plan.
[6:57pm] YesCT: in the meantime... http://drupal.org/node/1977784#comment-7339564
[6:57pm] Druplicon: http://drupal.org/node/1977784 => #1977784: Content language settings configuration page needs to determine what entities and bundles to include => Drupal core, translation_entity.module, normal, needs review, 32 comments, 5 IRC mentions
[6:58pm] andypost: not sure wssci complete all-to-controllers conversion so we only have form-controller as sane way to inject language selector
[6:58pm] GaborHojtsy: YesCT: yeah I think the plan I outlined is fine (a) use translatable to filter for what appears in the table (b) use field able and has field (check runtime per bundle) to show the checkbox for translatability
[6:59pm] YesCT: I still checked fieldable at the entity level. I dont know if that should be at the bundle.
[7:00pm] andypost: for now translatable is enough, but we should bake it dynamic to get rid of in favour of translation controllers
[7:00pm] GaborHojtsy: YesCT: yeah the "has field" would need to be per bundle
[7:00pm] andypost: * make
[7:03pm] YesCT: GaborHojtsy: right has field per bundle.
[7:03pm] GaborHojtsy: YesCT: I'll definitely help you with the sorting stuff tomorrow my morning
[7:03pm] rteijeiro joined the chat room.
[7:03pm] ricardoamaro left the chat room. (Quit: Leaving.)
[7:03pm] YesCT: GaborHojtsy: cools.
[7:03pm] GaborHojtsy: I need to wrap up for today
[7:03pm] YesCT: I'll leave sorting till then.
[7:03pm] ricardoamaro joined the chat room.
[7:03pm] GaborHojtsy: thanks everyone for attending!  hope such active meetings going on
[7:03pm] ricardoamaro1 joined the chat room.
[7:03pm] YesCT: And try and do the has_fields in the mean time.
[7:03pm] plach: YesCT: calling field_info_instances() on the bundle should be anough
[7:04pm] YesCT: plach: thanks!
[7:04pm] plach: it will tell you whch instances are defined for that bundle
[7:04pm] ricardoamaro1: thanks guys!
[7:04pm] YesCT: ricardoamaro1++
[7:04pm] YesCT: plach++
[7:04pm] plach: Have to go guys
[7:04pm] YesCT: GaborHojtsy++
[7:04pm] ricardoamaro1: youall++
[7:04pm] YesCT: reyero++
[7:04pm] GaborHojtsy: we have one more meeting before the big Portland sprint
[7:04pm] YesCT: andypost++
[7:04pm] GaborHojtsy: see you everyone in two weeks (and in the meantime every day lol :D)
[7:04pm] YesCT: vijaycs85++
[7:05pm] GaborHojtsy: :) :)