[5:59pm] plach joined the chat room. [6:00pm] GaborHojtsy: hey, happy new year! [6:00pm] Druplicon: GaborHojtsy: 1 week 4 days ago druplicon tell gaborhojtsy hope you dont have a problem with me drawing a line in the sand http://drupal.org/node/1648930?page=1#comment-6869232 [6:00pm] Druplicon: GaborHojtsy: 1 week 4 days ago tell gaborhojtsy http://sprunge.us/ZICh there is progress [6:00pm] Druplicon: GaborHojtsy: 1 week 8 hours ago tell GaborHojtsy I'd like to discuss adding links and/or focus board like things for novice, medium, challenging. should have enough issues to populate them now. [6:00pm] Druplicon: GaborHojtsy: 6 days 19 hours ago tell GaborHojtsy sometimes I cannot get the new site focus board to load. http://www.drupal8multilingual.org/ [6:00pm] Druplicon: GaborHojtsy: 5 days 17 hours ago tell GaborHojtsy please have a look at https://drupal.org/node/1763640#comment-6879334 [6:00pm] GaborHojtsy: anybody here for the D8MI meeting? [6:01pm] GaborHojtsy: plach: hi! [6:01pm] GaborHojtsy: [6:02pm] Sutharsan: GaborHojtsy: hi [6:02pm] GaborHojtsy: Sutharsan: hey [6:02pm] GaborHojtsy: how were the holidays? [6:02pm] plach: hello! happy new year everybody! [6:02pm] plach: GaborHojtsy: I'm here for the meeting [6:03pm] Sutharsan: GaborHojtsy: my holidays were good. [6:03pm] GaborHojtsy: great, I took a 1.5 week computer break (mostly only responding to *very* urgent email :), so therefore the msgs above [6:04pm] GaborHojtsy: so looks like we should be good to go into a renewed push in 2013 [6:04pm] mzgadzaj left the chat room. (Ping timeout: 244 seconds) [6:04pm] plach: I've tried and help with getting thresholds back in control meanwhile [6:05pm] GaborHojtsy: plach: oh, great [6:05pm] GaborHojtsy: plach: I've seen YesCT|afk tried to keep the part 2 ET UI patch passing / applying [6:05pm] plach: GaborHojtsy: I have some concern about the three feature-freeze bound features in the ET queu [6:06pm] GaborHojtsy: plach: ok, which ones? [6:06pm] plach: http://drupal.org/project/issues/search/drupal?status[]=Open&version[]=8.x&component[]=translation_entity.module&issue_tags=feature+freeze [6:06pm] plach: GaborHojtsy: it seems I cannot get reviews or even directions [6:07pm] plach: GaborHojtsy: they should be mostly ready IMO [6:07pm] GaborHojtsy: plach: ok, http://drupal.org/node/1807776 I did not have the required time to analyse, it is not a simple topic [6:07pm] Druplicon: http://drupal.org/node/1807776 => Support both simple and editorial workflows for translating entities => Drupal core, translation_entity.module, major, needs review, 59 comments, 10 IRC mentions [6:07pm] plach: but the only one that was RTBC has been pushed back to NR by catch, without any solid reason IMO [6:08pm] GaborHojtsy: plach: I agree http://drupal.org/node/1807800 is tricky, well, implementing meta-status and author info only on the translation level is a bit hackish, right? [6:08pm] Druplicon: http://drupal.org/node/1807800 => Add status and authoring information as generic entity translation metatdata => Drupal core, translation_entity.module, normal, needs review, 33 comments, 6 IRC mentions [6:09pm] GaborHojtsy: plach: tried to get catch follow up with a comment just now [6:09pm] GDrupal left the chat room. (Quit: GDrupal) [6:11pm] • GaborHojtsy tweeting about the column synching patch [6:11pm] plach: GaborHojtsy: do you think it would be better to focus on providing those metadata regardless of translation? [6:11pm] plach: GaborHojtsy: and which module would be responsible for doing that? [6:12pm] plach: GaborHojtsy: do you have any idea about the current media initiative status? I wasn't able to find anything [6:12pm] GaborHojtsy: plach: I think it would be a LOT more cleaner if terms would have status and authors [6:13pm] GaborHojtsy: plach: that is the only affected entity isn't it? [6:13pm] GaborHojtsy: plach: I don't think there is anything media related going on now [6:13pm] GaborHojtsy: plach: (my understanding) [6:13pm] plach: GaborHojtsy: [media] that was related to the sync patch [6:13pm] GaborHojtsy: plach: ah! [6:13pm] GaborHojtsy: plach: who would be good to review that? [6:14pm] GaborHojtsy: yched, davereid and? [6:14pm] plach: GaborHojtsy: well, the main use case behind that patch is being able to translate alt and titles which are provided by the core image widget [6:15pm] GaborHojtsy: plach: yeah, so I assumed a cross of field and image people [6:15pm] plach: GaborHojtsy: if media or anything like that is going into core, thus providing a media browser widget or stuff like that we might not need it, at least for images [6:16pm] GaborHojtsy: plach: uhm? [6:16pm] GaborHojtsy: plach: I think at best we can have a view that lists media like the admin/content list lists nodes [6:16pm] GaborHojtsy: plach: not sure how that removes the need for content sharing for translation [6:17pm] plach: GaborHojtsy: however, column sync might be useful with other widgets [6:17pm] YesCT|afk: I'm here [6:17pm] YesCT|afk is now known as YesCT. [6:17pm] plach: GaborHojtsy: in D7 ET integrates with the media widget and allows for having untransltable image fields with translatable alt and titles attached [6:18pm] GaborHojtsy: plach: https://twitter.com/d8mi/status/286521695924269056 [6:18pm] plach: GaborHojtsy: instead if you are using the core image widget you need a translatable image field and sync the fid column [6:18pm] GaborHojtsy: plach: yeah, well, that sounds like a workaround [6:18pm] GaborHojtsy: YesCT: hey, happy new year to you too! [6:18pm] GaborHojtsy: penyaskito: hey [6:19pm] GaborHojtsy: YesCT: thanks for keeping many issues alive over the holidays! [6:19pm] YesCT: Happy new year all! [6:19pm] YesCT: [6:19pm] plach: YesCT: hi! [6:20pm] YesCT: plach: hi. [6:20pm] plach: ok, enough for this [6:20pm] plach: GaborHojtsy: ca we get back to the metadata issue? [6:20pm] GaborHojtsy: Druplicon: tell catch happy new year! http://drupal.org/node/1831530 is RTBC and it has your name on it, so I'd have an impossible time to get any other commiter take a look - if you can it would be fabulous [6:20pm] Druplicon: http://drupal.org/node/1831530 => Entity translation UI in core (part 2) => Drupal core, translation_entity.module, normal, reviewed & tested by the community, 47 comments, 11 IRC mentions [6:20pm] Druplicon: GaborHojtsy: I'll pass that on when catch is around. [6:20pm] GaborHojtsy: plach: lol, sure [6:21pm] GaborHojtsy: plach: so I think only terms are affected?! [6:21pm] plach: GaborHojtsy: regarding status, yes [6:21pm] GaborHojtsy: plach: files have status and author(?) and vocabularies are not content entities anymore [6:21pm] plach: GaborHojtsy: but that's hardly generalizing the status property [6:22pm] plach: we'd need mor support at Entity API level [6:22pm] plach: at very least an EntityInterface::status() method [6:22pm] plach: or similar [6:22pm] GaborHojtsy: plach: yeah I think it would be a better approach to try to offer status and author at the entity level with an opt-out and just say those entities that opt out will not have translation workflows possible [6:23pm] GaborHojtsy: plach: implementing it only for the translation looks like a grand hack and I don't think we would have any easy time to get it into core [6:23pm] plach: GaborHojtsy: ok, this might work and we could get the API in and work on conversions after feature freeze [6:23pm] GaborHojtsy: plach: I think author, time and status tracking would be fabulous on terms for other uses as well eg. moderation in general [6:24pm] plach: GaborHojtsy: not on users I'd say [6:24pm] GaborHojtsy: plach: [6:24pm] plach: (author/time) [6:24pm] plach: maybe just time? [6:25pm] Sutharsan: GaborHojtsy: I have been working on cron update of interface translations (no issue yet). But I ran into problems, need your advise. [6:25pm] Sutharsan: GaborHojtsy: Apperenly batch function should not be used with cron, queue() should be used. But the current locale-batch functions make heavy use of the batch facility of $context. No such thing is not available for queue and should be created in an new class. I expect this to be a lot of work. Would it be acceptable to move the cron update of translations to contrib? I'd rather work on the improvement of the existing code now and do the cron thing la [6:25pm] GaborHojtsy: Druplicon: tell attiks happy new year! your review feedback on http://drupal.org/node/1807692 would be amazing I think you have some stake with image fields [6:25pm] Druplicon: http://drupal.org/node/1807692 => Introduce a column synchronization capability to translate alt and titles through the core image field widget => Drupal core, translation_entity.module, normal, needs review, 25 comments, 4 IRC mentions [6:25pm] Druplicon: GaborHojtsy: I'll pass that on when attiks is around. [6:26pm] YesCT: EclipseGc needed help, I think best from Sutharsan, with some tests of translation of ui, but I dont think Chris posted its in progress patch yet. I invited him to pop in to this meeting. [6:27pm] GaborHojtsy: Sutharsan: hum, I think integrating the update with cron (even if it requires some rework of existing underlying APIs) is not feature freeze bound [6:27pm] GaborHojtsy: Sutharsan: the feature is already in core [6:27pm] GaborHojtsy: Sutharsan: so I think we have free reign to work on it for months to come [6:27pm] GaborHojtsy: Sutharsan: I believe it should not be you alone working on this though, unless you prefer to [6:28pm] plach: GaborHojtsy: the only concern I have about this approach is that it somehow steers things away from having a table recording entity translations, which is currently my preferred approach for http://drupal.org/node/1810370 [6:28pm] Druplicon: http://drupal.org/node/1810370 => Find a clean way to deal with translation metadata and the existence of translations => Drupal core, translation_entity.module, normal, active, 4 comments, 1 IRC mention [6:28pm] GaborHojtsy: plach: well, if we need it for speedy lookups or keeping other metadata, we should [6:28pm] GaborHojtsy: plach: but working around some entities not having status and authors looks pretty hackish [6:28pm] GaborHojtsy: p [6:29pm] GaborHojtsy: plach: I cannot say catch pushed back due to this, but I can imagine [6:29pm] GaborHojtsy: plach: I think he might have been confused before realising how this works even [6:29pm] plach: GaborHojtsy: yeah, the only problem I have with that issue is that he didn't actually ptovide a feedback [6:30pm] YesCT: plach: yeah, I agree. [6:30pm] YesCT: his feedback was "looks good" iirc [6:30pm] YesCT: [6:31pm] Sutharsan: YesCT: np helping EclipseGc [6:32pm] plach: GaborHojtsy: this is the entity translation table schema in D7, how would you see it move into D8? http://drupalcode.org/project/entity_translation.git/blob/refs/heads/7.x-1.x:/entity_translation.install#l11 [6:32pm] YesCT: Sutharsan: EclipseGc says berdir just helped and it might be ok: http://drupal.org/node/1722882#comment-6894596 [6:32pm] Druplicon: http://drupal.org/node/1722882 => Plugin CacheDecorator caches globally, ignores request context, and does not specify tags for cache items => Drupal core, base system, critical, needs review, 21 comments, 20 IRC mentions [6:32pm] GaborHojtsy: YesCT: plach: yeah, well, my understanding was he did not get the role of the separate statuses yet [6:32pm] GaborHojtsy: YesCT: plach: I might be mistaken [6:32pm] GaborHojtsy: YesCT: plach: therefore my ask on the issue for more feedback from him [6:33pm] GaborHojtsy: plach: for the schema I think the source and translate columns are unique and not available anywhere else I guess [6:33pm] GaborHojtsy: plach: and I assume created/changed/status can be calculated from entity values if the entities provide them that is [6:34pm] GaborHojtsy: plach: so I assume the table would be relevant at least for the source and translate values [6:35pm] plach: GaborHojtsy: ok, which is what it's already doing in D8, I wanted it to be also the base table of an "entity_translation2 entity [6:35pm] YesCT: I pestered webchick about http://drupal.org/node/1848490 [6:35pm] Druplicon: http://drupal.org/node/1848490 => Make installation process use automatically translation import => Drupal core, locale.module, normal, reviewed & tested by the community, 52 comments, 22 IRC mentions [6:35pm] GaborHojtsy: YesCT: lol [6:35pm] plach: * "entity_translation" entity [6:35pm] GaborHojtsy: YesCT: at least that one is easy to test with just applying the patch [6:35pm] YesCT: [6:35pm] YesCT: it [6:35pm] YesCT: s [6:35pm] GaborHojtsy: plach: ah, hum [6:36pm] YesCT: it's so ready and really nice. [6:36pm] GaborHojtsy: plach: interesting [6:36pm] Jibran is now known as Jibran|afk. [6:36pm] GaborHojtsy: YesCT: [6:36pm] GaborHojtsy: Sutharsan++ [6:36pm] YesCT: Sutharsan++ [6:36pm] GaborHojtsy: plach: so what would you use that entity for? [6:36pm] Sutharsan: YesCT: thanks for keeping the issues alive [6:36pm] Sutharsan: YesCT++ [6:37pm] YesCT: [6:37pm] plach: GaborHojtsy: we would get CRUD hooks without having to invent translation-specific ones [6:37pm] plach: GaborHojtsy: currently ET in D7 does very nasty things to fire CRUD hooks [6:39pm] plach: GaborHojtsy: we could also leverage the Entity Access API for free, without the need to introduce per-langauge grants if node grants are generalized [6:40pm] GaborHojtsy: plach: hum [6:40pm] GaborHojtsy: plach: any other uses of the "cached" values on the translation entities? [6:41pm] plach: GaborHojtsy: cached? [6:41pm] GaborHojtsy: plach: well, the author, created time, etc. of a translation entity would be derived from values on the entity where the translation happened, no? [6:42pm] ClemensTolboom left the chat room. (Quit: Leaving.) [6:44pm] plach: GaborHojtsy: ah ok, in D7 we have Views integration for the entity_translation table: something similar would help with creating administrative pages listing translations (sortable/filerable, ...) [6:44pm] plach: * filterable [6:44pm] plach: GaborHojtsy: however, if we generalized support at entity-level I think it's fine anyway [6:45pm] plach: GaborHojtsy: as I told you, 'm just concerned that this approach could kill the translation as entity stuff before even disucssing it [6:46pm] GaborHojtsy: plach: well, as per your explanation on the patch, the behaviour on nodes is just proxied/cached/whatever you prefer to name it [6:46pm] GaborHojtsy: plach: which underlines how it is a hack for other types [6:47pm] GaborHojtsy: plach: so having it generally work as a proxy/cache for the representation of the translation entity, even is merely for quicker lookups or any other convenience handling would be good on its own, but I think this trojan horse might not be a good one [6:47pm] GaborHojtsy: plach: AGAIN [6:47pm] GaborHojtsy: plach: if catch thinks its a good solution, then sure go with it [6:47pm] GaborHojtsy: plach: I don't want to stop any progress from happening, but my opinion was asked [6:48pm] YesCT: (did that help notice issue get in… what issue is that?) [6:49pm] plach: GaborHojtsy: I have no strong preference between those two approaches, it just seemed to me that introducing the metadat only at translation level would be quicker and then we could expand on it afterwards. But this was when I hought feature fereeze would happen on Dec 1st [6:49pm] GaborHojtsy: plach: you just got a yched review on http://drupal.org/node/1807692 probably thanks to the tweet [6:49pm] Druplicon: http://drupal.org/node/1807692 => Introduce a column synchronization capability to translate alt and titles through the core image field widget => Drupal core, translation_entity.module, normal, needs review, 25 comments, 5 IRC mentions [6:49pm] dclavain left the chat room. (Quit: Saliendo) [6:49pm] GaborHojtsy: YesCT: http://drupal.org/node/1831846 [6:49pm] Druplicon: http://drupal.org/node/1831846 => arg() is using _current_path() instead of current_path() => Drupal core, base system, normal, needs work, 23 comments, 14 IRC mentions [6:49pm] GaborHojtsy: YesCT: not very nicely labeled anymore [6:49pm] plach: GaborHojtsy: you're my favourite twitter client after @webchick [6:50pm] YesCT: I dont know if I missed it in the scrollback, but http://drupal.org/node/365615 needs reviews. it will really help with thresholds. [6:50pm] Druplicon: http://drupal.org/node/365615 => Language detection not working correctly for most Chinese readers => Drupal core, language system, major, reviewed & tested by the community, 124 comments, 40 IRC mentions [6:51pm] YesCT: oh, right 1831846 needs a re-roll and crell had an issue with it.. maybe we can make a follow-up for crell's concern. [6:54pm] GaborHojtsy: YesCT: well, I'm not sure it is possible to resolve to Crell's satisfaction soon [6:54pm] YesCT: right.. so a follow-up for it? [6:54pm] GaborHojtsy: YesCT: (side note: just submitted an Acquia ticket about the D8MI site being inaccessible regularly) [6:55pm] YesCT: oh super! [6:55pm] GaborHojtsy: YesCT: I'm experiencing that too [6:55pm] GaborHojtsy: YesCT: on the arg() problem, it is used widely in core [6:55pm] YesCT: it wont help new new people if they cant see it. [6:55pm] YesCT: ah. so definately dont want to hold it up on the greater problem. [6:55pm] lucascaro joined the chat room. [6:56pm] mzgadzaj joined the chat room. [6:56pm] GaborHojtsy: YesCT: arg() used 27 places in D7: http://api.drupal.org/api/drupal/core%21includes%21bootstrap.inc/function/arg/8 [6:56pm] GaborHojtsy: D8 rather [6:59pm] GaborHojtsy: Druplicon: tell penyaskito happy new year! your continued work on http://drupal.org/node/1658846 could help move this through the finnish line - it seems very close to me thanks! [6:59pm] Druplicon: http://drupal.org/node/1658846 => Add language support to node access grants and records => Drupal core, node system, major, needs work, 131 comments, 33 IRC mentions [6:59pm] Druplicon: GaborHojtsy: I'll pass that on when penyaskito is around. [7:00pm] GaborHojtsy: plach: thanks for the review on http://drupal.org/node/1862202 btw [7:00pm] Druplicon: http://drupal.org/node/1862202 => Objectify the language system => Drupal core, language system, normal, needs review, 17 comments, 6 IRC mentions [7:01pm] GaborHojtsy: plach: looks like you can work out the details with chx [7:01pm] GaborHojtsy: plach++ [7:01pm] plach: GaborHojtsy: np, do you think the UX issue for language negotiation has some priority now? [7:01pm] YesCT: oh detection and selection! [7:02pm] GaborHojtsy: plach: I think more important would be furthering anything that gets us closer to property translation on entities [7:02pm] plach: GaborHojtsy: in the immediate future I'd like to focus on making nodes multilingual and review the config stuff, but that one could help with thesholds [7:02pm] GaborHojtsy: plach: if the UX one is blocking in thresholds, then sure that could use some love [7:03pm] GaborHojtsy: plach: otherwise I'd prioritise it later [7:05pm] plach: GaborHojtsy: it's currently major [7:05pm] plach: GaborHojtsy: I'll work on it if I have some spare spare time [7:05pm] plach: [7:06pm] GaborHojtsy: plach: good plan [7:06pm] plach: fago: pm? [7:06pm] YesCT: GaborHojtsy: I think nagwani might be up for an easy one and helping out with others to work on detection and selection (and it at a non-sprint pace) [7:06pm] GaborHojtsy: Druplicon: tell reyero happy new year! - your feedback on https://drupal.org/node/1763640#comment-6879334 would be fabulous, it is your original patch with some adjustments for scope nesting [7:06pm] Druplicon: https://drupal.org/node/1763640 => Introduce config context to make original config and different overrides accessible => Drupal core, configuration system, major, needs review, 113 comments, 36 IRC mentions [7:06pm] Druplicon: GaborHojtsy: I'll pass that on when reyero is around. [7:07pm] GaborHojtsy: YesCT: http://drupal.org/node/1869328 and http://drupal.org/node/1832614 are also simple things for nagwani or others of his caliber [7:07pm] Druplicon: http://drupal.org/node/1869328 => Restore simplicity of language list => Drupal core, language.module, normal, needs work, 17 comments, 3 IRC mentions [7:07pm] Druplicon: http://drupal.org/node/1832614 => Unchanged strings on page become customized when editing others => Drupal core, language system, normal, needs review, 20 comments, 6 IRC mentions [7:07pm] YesCT: GaborHojtsy: but nagwani wanted to talk with someone about it in irc. so if anyone sees them, give nagwani ping maybe? [7:07pm] GaborHojtsy: YesCT: thinking vijaycs85 for example when he moves off of http://drupal.org/node/1871328 [7:07pm] Druplicon: http://drupal.org/node/1871328 => Modules in new Multilingual package are no longer tested by Module\EnableDisableTest => Drupal core, language.module, normal, reviewed & tested by the community, 45 comments, 2 IRC mentions [7:07pm] Sutharsan: bye all [7:07pm] Sutharsan left the chat room. (Quit: Sutharsan) [7:08pm] plach: YesCT: I might try to drop an initial patch on the queue and leave the rest to him for refinment, what about it? [7:08pm] YesCT: I think I gave nagwani a true novice issue suggestion not because it is novice, just to have some non-epic like movement and success on an issue. He thought one easy and one hard was good to have on his plate. [7:08pm] GaborHojtsy: YesCT: yeah I think the negotiation block and settings exposure thing might be tricky, especially with chx working on objectifying the underlying layer, so maybe that is not the right one for nagwani [7:09pm] GaborHojtsy: YesCT: well, if plach gives it a start, then maybe [7:09pm] YesCT: ok. maybe in a supporting role, code style review, or manual testing and such. [7:09pm] mzgadzaj left the chat room. (Ping timeout: 252 seconds) [7:09pm] YesCT: and then coding up on an easier one. [7:10pm] GaborHojtsy: Druplicon: tell chx happy new year! great stuff in tje objectifying the language system patch beejeebus is back with a working context patch with scopes at https://drupal.org/node/1763640#comment-6879334, your review would be welcome! [7:10pm] Druplicon: https://drupal.org/node/1763640 => Introduce config context to make original config and different overrides accessible => Drupal core, configuration system, major, needs review, 113 comments, 37 IRC mentions [7:10pm] Druplicon: GaborHojtsy: I'll pass that on when chx is around. [7:10pm] GaborHojtsy: YesCT: yeah, http://drupal.org/node/1869328 and http://drupal.org/node/1832614 are also simple things IMHO [7:11pm] GaborHojtsy: YesCT: probably much more contained [7:11pm] Druplicon: http://drupal.org/node/1869328 => Restore simplicity of language list => Drupal core, language.module, normal, needs work, 17 comments, 4 IRC mentions [7:11pm] Druplicon: http://drupal.org/node/1832614 => Unchanged strings on page become customized when editing others => Drupal core, language system, normal, needs review, 20 comments, 7 IRC mentions [7:11pm] YesCT: (my internet might spotty over the next week.) [7:11pm] alexpott left the chat room. (Ping timeout: 245 seconds) [7:11pm] GaborHojtsy: YesCT: also they don't need to be on the board, they were/are there because it seemed like progress is happening and it makes it easier to track [7:11pm] YesCT: right. [7:11pm] GaborHojtsy: YesCT: speaking of boards, I think we should/can discuss additional summary board tomorrow my morning? [7:12pm] YesCT: GaborHojtsy: feelings on a (non-sprint) board for the levels: novice, medium, challenging? [7:12pm] GaborHojtsy: YesCT: I'd be happy to give you content admin on the site (which was one of the reasons to have the site on its own and we can work out additional board and how to integrate them in navigation, etc. [7:12pm] YesCT: heh! [7:12pm] • GaborHojtsy thinking alike [7:12pm] YesCT: yeah, discussing tomorrow your morning should be great. [7:13pm] YesCT: [7:13pm] GaborHojtsy: YesCT: ok [7:13pm] YesCT: GaborHojtsy: plach: feel free to give me some direction for something to focus on. [7:13pm] GaborHojtsy: YesCT: in my mind, if we come up with a great navigation scheme for them, it could be pretty extensive [7:15pm] GaborHojtsy: YesCT: I think you are doing very good stuff around (1) keeping RTBC issues applying (2) helping new people (3) organising issues [7:15pm] aries_mwz left the chat room. (Ping timeout: 240 seconds) [7:15pm] GaborHojtsy: YesCT: are main challenges keep being the stuff around property translation on entities and all the CMI stuff [7:16pm] GaborHojtsy: heyrocker set a deadline for the CMI stuff for Jan 15th, so we have time to finalise implementation before the freeze [7:16pm] YesCT: right. [7:16pm] GaborHojtsy: I think very wisely [7:16pm] YesCT: I agree. wise. [7:16pm] GaborHojtsy: however not much move there, so my prediction is it will be like if we committed it Dec 1st, but with 1.5 months spent lingering [7:17pm] YesCT: yep. I figure it's likely. [7:17pm] GaborHojtsy: YesCT: anyway, I think it is mostly still on the key people there, chx, effulgentsia, reyero, beejeebus, etc. [7:17pm] GaborHojtsy: YesCT: so not sure anything grand to help with there [7:18pm] YesCT: right. if it gets to a point where I might be helpful… I'll keep an eye on it. [7:18pm] GaborHojtsy: YesCT: http://drupal.org/node/1833334 is the next one for properties [7:18pm] Druplicon: http://drupal.org/node/1833334 => EntityNG: integrate a dynamic property data table handling => Drupal core, entity system, major, needs work, 75 comments, 11 IRC mentions [7:19pm] YesCT: GaborHojtsy: I think beejeebus had some question about how to focus on moving forward. Since many people were on break, maybe a check in with beejeebus. [7:19pm] GaborHojtsy: YesCT: also well in hand probably by fago, Berdir, das-peter I think [7:19pm] GaborHojtsy: YesCT: yeah, I pinged his issue to many people and also commented on specifically asking feedback from several people who had concerns before [7:20pm] YesCT: ah, right, that's fago's other entityNG issue. [7:20pm] GaborHojtsy: one more [7:20pm] plach: GaborHojtsy: when you have 1 minute: http://drupal.org/node/1620010#comment-6894874 [7:20pm] Druplicon: http://drupal.org/node/1620010 => Move LANGUAGE constants to the Language class => Drupal core, language system, normal, needs work, 16 comments, 3 IRC mentions [7:20pm] GaborHojtsy: Druplicon: tell heyrocker happy new year! beejeebus has a complete context proposal at https://drupal.org/node/1763640#comment-6879334 - it would be great if you could review it [7:20pm] Druplicon: https://drupal.org/node/1763640 => Introduce config context to make original config and different overrides accessible => Drupal core, configuration system, major, needs review, 113 comments, 38 IRC mentions [7:20pm] Druplicon: GaborHojtsy: I'll pass that on when heyrocker is around. [7:20pm] plach: guys I have to go now [7:21pm] plach: read you soon [7:21pm] YesCT: plach: see you around. [7:21pm] plach: GaborHojtsy: please, have a look to the permission/workflows issue when you can [7:21pm] plach: bye! [7:21pm] GaborHojtsy: plach: sure thing! [7:21pm] plach left the chat room. (Quit: ChatZilla 0.9.89 [Firefox 17.0.1/20121128204232]) [7:22pm] GaborHojtsy: ok, I need to go too [7:22pm] GaborHojtsy: thanks all for coming, I did not think it would be this crowded and active [7:22pm] YesCT: