[18:02:28] GaborHojtsy: so welcome everybody!
[18:03:08] plach: hey
[18:03:21] GaborHojtsy: first some celebration stuff
[18:03:29] GaborHojtsy: we got LOTS of good stuff in the past two weeks
[18:03:34] weal: yay
[18:03:48] webchick: YAY
[18:04:11] GaborHojtsy: we made plurals editable and discoverable (recorded properly even if you don't use .po files) in core!
[18:04:18] GaborHojtsy: we introduced langcode on various entity types!
[18:04:27] GaborHojtsy: and standardized on langcode (almost) all around
[18:04:43] GaborHojtsy: fixed a couple of other bugs
[18:04:51] weal: plurals will be amazing to work with
[18:05:45] GaborHojtsy: so good stuff I think we are "in direction" for Drupalcon Denver and we can continue with some cool stuff, if you look at http://hojtsy.hu/d8mi/current-top-priority-tasks on the entity front, we are still working on renaming fields to langcode and introducing a getter/setter for fields
[18:06:17] millette [~millette@cogitateurs-agitateurs/oqp] entered the room.
[18:06:21] GaborHojtsy: and let people assign new special languages we have introduced
[18:06:31] weal: bienvenue millette
[18:06:34] GaborHojtsy: oh, and Desire was hard at work on more flexible language defaults for content types too so help in any of those areas would be welcome! on the UI translation front, we have been discussing a new UI for UI translation  which got lots of feedback, but more helps  http://drupal.org/node/1452188
[18:07:23] Druplicon: http://drupal.org/node/1452188 => New UI for string translation => Drupal core, locale.module, normal, active, 46 comments, 4 IRC mentions
[18:07:46] weal: very curious about that one
[18:08:02] GaborHojtsy: that is you know OOP, PSR-0, Iterator-using, and all that stuff
[18:08:23] webchick: lol
[18:08:29] GaborHojtsy: at http://drupal.org/node/1189184 sutha is on it, but more help is welcome!
[18:08:31] Druplicon: http://drupal.org/node/1189184 => Make gettext .po generation its own abstracted functionality => Drupal core, locale.module, normal, needs review, 23 comments, 5 IRC mentions
[18:08:40] plach: in one word it's being cool-stuffed
[18:09:01] GaborHojtsy: we discovered Drupal 7 has some helper functions that are PHP 3 era code, eg. reimplementations of wordwrap() in userspace
[18:09:02] GaborHojtsy: fun things
[18:09:58] GaborHojtsy: and finally, usability stuff for moving negotiation to the language module: http://drupal.org/node/1468930
[18:10:04] Druplicon: http://drupal.org/node/1468930 => Move negotiation functionality from locale module to language module => Drupal core, locale.module, normal, needs work, 9 comments, 1 IRC mention
[18:10:04] GaborHojtsy: huge patch :)
[18:10:35] GaborHojtsy: so I think we'll hopefully make good progress on these things as well as on config languages for CMI and property language support in Denver
[18:10:42] GaborHojtsy: its a tall order but we have many great people :)
[18:11:16] GaborHojtsy: if you have not signed up for the sprints(!) there, please read and do so at http://groups.drupal.org/node/209803 (and the doodle)
[18:11:18] Druplicon: http://groups.drupal.org/node/209803 => Drupal 8 Multilingual Initiative sprint at and after the end of Drupalcon Denver => 3 comments, 4 IRC mentions
[18:11:28] GaborHojtsy: any questions, or specifics people want to talk about from these focus issues?
[18:11:31] colan: any thoughts on http://drupal.org/node/1188394 ?  wondering what the direction is here.
[18:11:32] Druplicon: http://drupal.org/node/1188394 => Make title behave as a field (again) => Drupal core, entity system, major, active, 23 comments, 4 IRC mentions
[18:12:02] GaborHojtsy: colan: great question, we want to set up a property translation BoF in Denver to talk about this specifically with plach, fago, etc. al, if you are present you are welcome to attend
[18:12:04] weal: since I'll be new to working with *this* code (hint, git git git please) I'm curious about the renaming of language properties and/or that huge patch of moving stuff to the language module.  seems like good learning, or too much?
[18:12:15] GaborHojtsy: colan: we had difficulties scheduling it so far
[18:12:25] GaborHojtsy: colan: so that it would be right for everybody
[18:12:45] GaborHojtsy: colan: basically if you look at the getter/setter patch, it prepares the code for supporting properties with language assigned
[18:13:01] GaborHojtsy: colan: so then it would be on the entity to support them internally, the API would support it (and fall back proper if not supported)
[18:13:14] GaborHojtsy: colan: I think the real tricks are efficient storage and transparent APIs
[18:13:23] Bojhan (~kvirc@ip4da63989.direct-adsl.nl) joined the channel.
[18:13:32] GaborHojtsy: colan: hopefully we can solve the transparent API, so efficient storage is still to figure out
[18:13:55] colan: GaborHojtsy: makes sense.  i'd love to be there, but have to skip this con - can't make it this time :(
[18:14:19] webchick: i'm curious when a few of the WOW changes like http://drupal.org/node/1188388 and the ability to translate things like menu links/taxonomy terms in core (which I don't see issues for off-hand) are slated
[18:14:19] colan: first NA one i can't make in years.
[18:14:20] Druplicon: http://drupal.org/node/1188388 => Move translatable fields UI into core => Drupal core, language system, normal, active, 7 comments, 1 IRC mention
[18:14:39] GaborHojtsy: colan: any wise words for us to help start off?
[18:14:46] webchick: The consistency/clean-up patches have been nice, also the UI improvements. But there is still a big delta between D8 core and what i18n cna do
[18:15:13] GaborHojtsy: weal: the negotiation move looks like a huge patch but is mostly copying code around.... we might need to break it up in smaller chunks, but would need constant committer help to commit the parts in a timely fashion :)
[18:15:27] plach: colan: (shameless plug) you might want to have a look to http://groups.drupal.org/node/197848#api-dx and following for some toughts of mine about this :)
[18:15:29] Druplicon: http://groups.drupal.org/node/197848 => Content language support in Drupal 8 => 0 comments, 2 IRC mentions
[18:15:35] colan: GaborHojtsy: not really, i think that direction makes sense.  once there's a generic properties API for language stuff, applying it to titles makes sense.
[18:16:09] weal: GaborHojtsy: that might be a good one for me to tackle on Monday, I'll be arriving in Denver Saturday morning
[18:16:20] webchick: and also curious if there's a BoF or similar scheduled in Denver to get http://drupal.org/node/1448330 figured out once and for all
[18:16:21] Druplicon: http://drupal.org/node/1448330 => Implement internationalization of configuration => Drupal core, configuration system, critical, active, 18 comments, 3 IRC mentions
[18:17:11] GaborHojtsy: webchick: yes, for field translation UI the contrib module itself is plach's child, so I keep encouraging him on that front - he keeps saying it needs to mature a bit in contrib + that we need the API improvements like the getter/setter to have a sane API for developers
[18:17:15] plach: webchick: i've been working hard to the new ET UI theese days
[18:17:17] GaborHojtsy: plach: more comments? :)
[18:17:23] plach: but didn't get mugh UX feedback
[18:17:35] webchick: work on it in the core queue, you'll get plenty of feedback :D
[18:17:41] plach: eh
[18:17:57] weal: <3 sane api
[18:17:59] Artusamak: hmm i wrote in my calendar that the D8MI meeting was starting at 19h :/ [re-reading]
[18:18:16] plach: I'd love to have some pseudo-stable D7 code before moving it to core
[18:18:17] plach: see
[18:18:21] GaborHojtsy: plach: webchick: I think we need to stage the introduction of that, the problem with entity_translation module is that it is a UI for field translation + workarounds for missing functionality like property translation, and we want to solve property translation proper
[18:18:29] webchick: I <3 sane API too, but I hate i18n requiring 50 modules and a bit of bandy-wire to get right, so it'd be nice to see the focus start to shift more to end-user features from API consistency.
[18:18:35] webchick: just my 2 cents
[18:18:52] GaborHojtsy: webchick: exactly :)
[18:18:57] weal: webchick: similar concerns here
[18:18:59] plach: http://drupal.org/node/1480388
[18:19:00] Druplicon: http://drupal.org/node/1480388 => ETA for dev or rc of ml_edit_form branch? => Entity translation, Miscellaneous, normal, fixed, 2 comments, 1 IRC mention
[18:19:37] GaborHojtsy: webchick: so we can move some parts of the UI module without it being actually useful
[18:19:39] webchick: GaborHojtsy: putting missing plumbing in place makes sense
[18:19:42] GaborHojtsy: webchick: if that helps
[18:20:17] plach: GaborHojtsy: webchick: my main concers is we don't have an officially Bojhan -yoroy approved UI atm
[18:20:39] webchick: plach: I assume they've been contacted. Just busy?
[18:21:10] webchick: I know yoroy will be in Denver, not sure about Bojha
[18:21:12] webchick: Bojhan*
[18:21:27] GaborHojtsy: plach: webchick: likely setting up a discussion / call with them to discuss the details would be great, I think
[18:21:31] colan: plach: is that ml_edit_form branch sufficiently baked for folks to test?
[18:21:34] webchick: But if that's the blocker, next week is a great time to get unblocked on things. :D
[18:22:22] plach: GaborHojtsy: webchick: they both are subscribed to http://drupal.org/node/1282018#comment-5703004 but we got almost no feedback yet
[18:22:25] Druplicon: http://drupal.org/node/1282018 => Drop the translation form in favor of a language-aware edit form => Entity translation, Code, critical, active, 57 comments, 3 IRC mentions
[18:22:28] colan: nm, just saw the issue :)
[18:22:28] GaborHojtsy: webchick: yeah, I hoped to move forward next week with underlying issues like property translation and config language
[18:22:38] GaborHojtsy: webchick: which look like the two big things next up
[18:22:42] webchick: plach: Maybe reach out and let them know you feel stuck.
[18:22:58] plach: colan: it should be yes, but it needs a core patch
[18:22:59] webchick: plach: I follow a lot of issues but unless it's clear someone's specifically waiting on me for something, I often don't get engaged
[18:23:08] GaborHojtsy: Bojhan is here :)
[18:23:09] webchick: GaborHojtsy: cool
[18:23:53] plach: webchick: I focues on code for now ;)
[18:23:58] plach: * focused
[18:23:59] webchick: oookay. :)
[18:24:09] colan: plach: core issue url/# ?
[18:24:10] webchick: Just don't let yourself get to Munich and go OH NOES we nee to start UI design
[18:24:18] GaborHojtsy: webchick: from my POV the problem on the entity front is more like not being able to resolve even simple issues like http://drupal.org/node/1277776 because of many high profile stakeholders providing feedback far in between but then with strong opinions
[18:24:20] Druplicon: http://drupal.org/node/1277776 => Add generic field/property getters/setters (with optional language support) for entities => Drupal core, entity system, normal, needs review, 89 comments, 10 IRC mentions
[18:24:49] plach: colan: no core issue yet
[18:24:52] webchick: GaborHojtsy: yes that sounds like a great conversation to hash out next week
[18:25:04] plach: colan: the patch is ont the ET issue, one of the latest comments
[18:25:27] plach: webchick: sure
[18:25:41] webchick: GaborHojtsy: also following that now. was not before.
[18:27:27] GaborHojtsy: webchick: so that would be for all things entity, then for all things config, we've been discussing that for ages, and people been pushing back to support arbitrary contexts instead of just language, so that only required strong hands to shake out :)
[18:27:44] webchick: Yep. :) And it gets a lot more real now that we have some actual code committed for CMI
[18:27:56] webchick: So that should hopefully provide a bit of extra "ahem" to get a decision of some kind made
[18:27:57] plach: I have to review the latest patch but I still think the main apsetc to be covered over there is the default language one
[18:27:59] GaborHojtsy: yes, finally
[18:28:51] GaborHojtsy: plach: I think the reviews on the getter/setter issue are mostly cryptic enough that is hard to tell what is the list of things we still want to solve there, so its impossible to tell whether we are there yet
[18:29:08] GaborHojtsy: plach: and my feeling on that extends to the whole entity API meta-verse
[18:30:19] plach: GaborHojtsy: IMO:
[18:30:33] plach: 1) decide how to handle the default language issue
[18:31:38] plach: this brings in the question on how to tell in which caes we should act on a single language and which ones should have all languages processed for field/properties
[18:32:24] plach: there has not been much discussion on this
[18:32:34] plach: but I think this is the central point
[18:32:36] Bojhan: plach: I am atm, eating - but feel free to ping me later if UI is blocking it from being comitted - we have loads of issuess in our queues, not always aware when something is blocked
[18:32:52] plach: the other one is figuring out a storage
[18:33:03] plach: i.e.
[18:33:21] plach: 2) decide how to store arbitrary multingual entity data
[18:34:07] plach: these are more-or-less covered by bullets 3-4-5 of my content battleplan
[18:34:16] plach: at least my POV on these ;)
[18:34:34] plach: I think thees are the big architectural decisions we have to make
[18:34:46] plach: then compelte the UI and shove it in ;)
[18:36:19] GaborHojtsy: plach: I think its best to follow on the D7 model of default language for fields, so we can get moving on the real user problems :)
[18:36:36] plach: Bojhan: I'll have sometime tonight but it may be very late, baically the new UI is almost functionally ready but we need to figure out how to hsndle shared fields, I posted an issue summary with screenshot since your latest review
[18:36:52] plach: Bojhan: would you please have a look at them and tell me if you need mor info?
[18:38:23] GaborHojtsy: plach: I think we should forego the introduction of this complication that a node can have fields in varying languages in its original form, that sounds like (a) a pretty special case (b) work-aroundable in contrib
[18:38:42] plach: GaborHojtsy: that model is semibroken on the API side we have a critcal task open to fix it, I ain't sure we want to base the D8 architecture on it...
[18:39:19] GaborHojtsy: plach: ok, so how do we solve it then to make it simpler by making it more flexible/complex? :)
[18:40:41] plach: GaborHojtsy: I think that can be easily split into: a patch to allow it in contrib (i.e. introduce the distinction in core between linguistic and shared field/property) and the actual work which does not need to be implemented in core
[18:41:08] plach: GaborHojtsy: I think we are mixing two matters
[18:41:49] plach: GaborHojtsy: one is single-language vs multiple-alnguage workflow, the othe is the LANGUAGE_NOT_APPLICABLE vs LANGUAGE_NOT_SPCEFIED stuff
[18:42:11] plach: they are somehow related but independent
[18:42:21] GaborHojtsy: plach: well, yes, and no, if you have multiple language fields on a "single language" entity, then they cross :)
[18:42:38] GaborHojtsy: plach: ok, so where is our issue for the default language handling / workflow problem?
[18:44:01] plach: GaborHojtsy: it should be discussed in the getter/setter one
[18:44:19] plach: GaborHojtsy: IIRC it has, but not really solved IMO
[18:44:46] GaborHojtsy: plach: well, we solved it by falling back on the entities default language, which works if we consider the D7 model of supporting language on fields if the entity has language, right?
[18:46:49] plach: GaborHojtsy: we have skipped the context-specific default change, which I fear will bit us if we don't adress properly, bit I guess we need a separate issue for that, once we have a context/request object to rely on
[18:47:17] GaborHojtsy: plach: yeah, we don't yet have context, so how would we solve it now? :)
[18:49:10] fago (~fago@213.235.217.10) left IRC. (Ping timeout: 260 seconds)
[18:49:55] plach: GaborHojtsy: no way to solve it now, but it is a big issue :)
[18:50:18] GaborHojtsy: plach: yeah, so my question was what is holding *that* patch up :)
[18:51:10] GaborHojtsy: plach: so far I was pretty successful in other areas of D8MI to break up tasks to smaller issues and keep going in small achievements, but entities did not work at all due to never-ending discussions and config did not work due to no base to work off of
[18:51:30] plach: GaborHojtsy: sorry, misread your line, I have to review the latest patch, it mught just be fine
[18:51:32] GaborHojtsy: plach: so we are past half time for D8MI announced vs. D8 frozen and still almost no entity changes
[18:51:44] GaborHojtsy: plach: we need to get moving faster :)
[18:52:15] GaborHojtsy: plach: if we extrapolate from what we achieved so far it is indeed not a happy picture :/ which is webchick's point I guess
[18:53:11] Artusamak is now known as Artusamak_afk
[18:53:17] plach: GaborHojtsy: no it is not
[18:54:45] GaborHojtsy: plach: I've been thinking a lot lately on how to stage the introduction of entity translation module
[18:55:09] ClemensTolboom (~Adium@a82-95-247-112.adsl.xs4all.nl) left IRC. (Ping timeout: 252 seconds)
[18:55:17] GaborHojtsy: plach: ie. start off an entity_translation or entity_language module in core that would provide an entity setting for all entity types plus expose the field translatability setting (without actually providing anything else)
[18:55:27] plach: GaborHojtsy: as part of the Denver discussions we can try to come up with a series of actioable issues to get there
[18:55:34] GaborHojtsy: plach: I think that in itself would need enough work and would ignite enough discussion as to how to store those things, the UI, etc.
[18:56:00] GaborHojtsy: plach: sure we don't need to solve it here, just wanted to get your thinking started :)
[18:56:25] zly (~zly@3EC979B7.catv.pool.telekom.hu) joined the channel.
[18:58:04] plach: GaborHojtsy: with field translatabilty setting you mean the entity info keys ET currently uses to build the UI?
[18:58:23] plach: i.e. the 'translation' key?
[18:58:39] GaborHojtsy: yup, have a UI for making any entity 'entity translatable' and making any field translatable
[18:58:49] GaborHojtsy: and its storage for those settings
[18:59:42] plach: are you thinking about an UI to switch translatability for multiple fields at once?
[19:00:06] GaborHojtsy: I think overall we want to get rid of translation module but the new field/entiy translation module would not be called translation module since it does not translate anything but entities/fields and we'll have other plumbing to solve config translation lets say
[19:00:39] plach: GaborHojtsy: so retaingin entity_translation? it's awfully long
[19:00:42] weal continues reading up on plurals ... facinating stuff
[19:00:49] GaborHojtsy: plach: no, I don't have any huge plans to revamp that thing just thinking getting that part of the ET module would be a good first step, relatively simple, it would establish our new module, etc.
[19:01:24] GaborHojtsy: plach: see, we'll need to discuss the module name :) better start it sooner then later :)
[19:01:36] GaborHojtsy: plach: we don't need to solve the UI problems or entity API problems for it :)
[19:01:42] plach: GaborHojtsy: ok, bootstrappong core entity translation sounds fine
[19:02:14] GaborHojtsy: plach: yeah, so that would at least make ET set foot in core :)
[19:02:18] plach: GaborHojtsy: maybe coming up with a series of cationable tasks as for the base language and UI translation sub-initiatives
[19:02:22] GaborHojtsy: plach: and we can gradually add to it
[19:02:41] GaborHojtsy: plach: right :)
[19:02:50] plach: GaborHojtsy: on thing I'm not really clear about:
[19:03:15] plach: do you think we will be able to re-use some code for th contrib mdoule or it would be better to rewrite completely?
[19:03:54] colan: plach: speaking of naming, why was it called "entity translation" & not "field translation"?
[19:04:26] plach: colan: because it does not deal with just fields :)
[19:04:31] GaborHojtsy: plach: I hope we can reuse code as much as possible, but we need to dissect it to figure it out piece by piece
[19:04:42] GaborHojtsy: colan: it provides workaround for properties at least :)
[19:04:50] colan nods
[19:05:10] colan: GaborHojtsy: how about sticking the entire module in the branch & then working on it from there?
[19:05:23] zly (~zly@3EC979B7.catv.pool.telekom.hu) left the channel. ("Távozom")
[19:05:27] colan: seeing then what needs to dropped/added.
[19:05:44] webflo (~Adium@gateway.digi-info.de) left IRC. (Quit: Leaving.)
[19:06:06] plach: colan: well, it's not even stable
[19:06:26] colan: gotta start somewhere.
[19:06:28] plach: colan: and it woll need quite some work just to adapt it to the D8 codebase
[19:06:50] GaborHojtsy: colan: plach: well, we could do that in a D8MI sandbox, but really "random" parts of it will need to be dropped and the parts that are not will conflict with any new module we build to migrate its code in core IMHO
[19:06:54] plach: colan: I'm not saying it's not a possibility, but I ain't sure about it
[19:07:53] colan: waiting until it's stable may put things too far out.  may be better to fork now & get working on the core stuff.  can merge / cherry-pick particular things later to sync them up.
[19:07:53] GaborHojtsy: colan: so far what worked for the other initiatives working on big changes in a sandbox was that they worked on it for months, then submitted a huge core patch, then got rejected with lots of discussions, then went back, redone some stuff, rinse and repeat
[19:08:00] berdir1 (~berdir@62-2-205-114.static.cablecom.ch) left IRC. (Quit: Leaving.)
[19:08:11] floretan (~floretan@ppp-188-174-45-59.dynamic.mnet-online.de) left IRC. (Remote host closed the connection)
[19:08:11] GaborHojtsy: colan: what worked for D8MI is much-much smaller patches, which got naturally through the core queue with much less debating
[19:08:20] colan: ok
[19:08:45] reyero: sorry to interrupt (I've been around for a while) but: what about getting a stable ET module and a good UI for D7 before making D8 into a big sandox?
[19:09:19] GaborHojtsy: reyero: that is what plach was targeting but he had little time to work on it AFAI understand
[19:09:27] colan: reyero: ideal, but like i suggested above, it may take too long.  may be necessary though.
[19:09:28] webflo (~Adium@gateway.digi-info.de) joined the channel.
[19:09:49] reyero: I'm just for keeping experiments in contrib, move to core concepts that work
[19:09:55] reyero: so if we cannot get even that...
[19:10:03] GaborHojtsy: reyero: and we *know* many parts of the ET UI are core worthy, or would need to be re-thought for D8 anyway, like entity and field level settings for translatability :)
[19:10:16] colan: reyero: ...then we get this into D9 :)
[19:10:44] GaborHojtsy: reyero: I'm advocating we parallelize the work as much as possible
[19:11:17] colan: i don't have much experience with core, so if you guys & gals think we can't parallelize, then that's probably best.
[19:11:22] plach: reyero: I don't think we are too much far from a D7 stable release
[19:12:00] plach: reyero: it's just I have had little time to work on it in the last month
[19:12:03] colan: plach: ballpark ETA then?
[19:12:26] plach: colan: define "ballpark", please :)
[19:12:44] plach: no idea of what that means
[19:12:55] colan: plach: a wide area estimate.
[19:13:18] colan: something in the ball park, as in the baseball stadium.
[19:13:23] plach: colan: well the new UI patch is almost ready, I think i can have it ready in 2/3 days
[19:13:31] plach: from afunctional pov
[19:14:00] colan: then i guess it's GaborHojtsy's decision.
[19:14:11] GaborHojtsy: ?%?!%?+
[19:14:20] colan: :D
[19:15:05] colan interprets that for swearing, unless it's Unicode for something else
[19:15:39] GaborHojtsy: look, I've been successfully parallelizing all kinds of tasks from negotiation, new special languages, langcode renames, plural support, etc. in http://hojtsy.hu/d8mi/current-top-priority-tasks, so I think we can shuffle in pieces of introducing an entity translation UI just as well
[19:16:26] GaborHojtsy: we are regularly blocked on things are places, so the best way to work is to have another important / next step thing to jump to at that point and let some issues work out in the meantime
[19:16:38] GaborHojtsy: "blocked on things at places" :)
[19:16:48] plach: GaborHojtsy: I agree
[19:17:41] GaborHojtsy: problem with entity stuff is that we have little to work on ATM due to missing issue breakdown of the bigger tasks plus a one step forward two steps back progress on http://drupal.org/node/1277776 :/
[19:17:43] Druplicon: http://drupal.org/node/1277776 => Add generic field/property getters/setters (with optional language support) for entities => Drupal core, entity system, normal, needs review, 89 comments, 11 IRC mentions
[19:17:47] plach: GaborHojtsy: I only hope well'get the necessary Entity/WSCCI infrastructre in time to address the issues I mentioned abbove :)
[19:18:17] GaborHojtsy: plach: yeah, I would not count on that for now :) we need to have plan Bs for each case
[19:19:32] GaborHojtsy: plach: and anyway, focus on actionable "small" steps that we can move forward :)
[19:20:10] plach: GaborHojtsy: agreed, we'll also get the bonus of avoiding gates ;)
[19:20:10] GaborHojtsy: speaking of which...
[19:20:48] GaborHojtsy: reyero: we are working at http://drupal.org/node/1471432 in part to introduce some of the i18n functionality in core possible, like disabling special languages for content, etc.
[19:20:49] Druplicon: http://drupal.org/node/1471432 => Let users assign LANGUAGE_NOT_APPLICABLE and LANGUAGE_MULTIPLE => Drupal core, language system, normal, needs review, 4 comments, 1 IRC mention
[19:21:05] GaborHojtsy: reyero: there are two implementation plans outlined which are opposite of each other
[19:21:13] GaborHojtsy: reyero: any opinion on what way should we go?
[19:22:28] reyero: GaborHojtsy: not really, will take a look at them
[19:22:37] GaborHojtsy: reyero: that would be superb, thanks :)
[19:22:51] reyero: GaborHojtsy: right now I'm working only on strings/help texts/tokens, etc..
[19:23:13] GaborHojtsy: reyero: have you been able to talk to jhodgdon in particular about it?
[19:24:35] reyero: GaborHojtsy: no, just working on patches atm
[19:24:57] GaborHojtsy: reyero: I'd very *strongly* advise you talk to jhodgdon and cross-check plans
[19:25:48] reyero: GaborHojtsy: ok, I'll take note
[19:27:12] GaborHojtsy: reyero: ok, great
[19:27:31] GaborHojtsy: reyero: she is the help text/docs lead
[19:27:50] hairqles (~hairqles@2E6B26E1.catv.pool.telekom.hu) joined the channel.
[19:27:50] GaborHojtsy: after all :)
[19:28:08] GaborHojtsy: hah, we are 30 min after the planned timeslot, any other topics? :)
[19:29:02] plach: dinner?
[19:29:38] plach: scheduling the entity bof if possible?
[19:29:46] GaborHojtsy: plach: ah, dinner :)
[19:29:58] weal just finished lunch
[19:30:11] colan: yeah, only 1430h EST :)
[19:30:12] GaborHojtsy: plach: well, I thought we can actually schedule it 6pm for Tues or Wed, but there are in fact no slots for that
[19:30:40] plach: personally I'll disregard any other thing to attend it
[19:30:44] weal: now that I'm up to speed on the ET stuff I'm very keen to attend that proposed BoF.  I *really* could have used the getters and setters back in d6!
[19:30:49] plach: so no problem from me
[19:31:29] GaborHojtsy: weal: :)
[19:31:50] plach: fago has gone :(
[19:31:54] GaborHojtsy: plach: yeah, ok, well, fago is not around now, I tried to ping him before to figure out a different timeslot, but was unable to
[19:32:15] weal: I'm with plach on the schedule front.  The only "must see" item on my schedule is the coding for views presentation
[19:32:38] GaborHojtsy: also would be great to see other "entity stakeholders" around, I mean fago and the two of us are not enough for a revolution :)
[19:32:58] reyero is leaving, have some other meeting now, bye
[19:33:01] plach: GaborHojtsy: did you ping em directly?
[19:33:05] reyero (~reyero@213.254.72.43.dyn.user.ono.com) left the channel.
[19:33:06] plach: reyero: bye!
[19:33:26] colan: thanks everyone. take good notes @ the con for those of us that can't make it. :)
[19:33:56] GaborHojtsy: weal: ok, well, I have two sessions (core conversation and main track), hold a BoF, scheduled to man the Acquia booth for an hour, got Dries to reschedule his D8 plans core convo to be able to attend, so I'm a bit more complicated :)
[19:33:58] weal: yes, thanks all!  this has been very informative
[19:34:15] GaborHojtsy: plach: yes, I did
[19:34:18] plach: GaborHojtsy: was the doodle about it?
[19:34:30] plach: no sprint
[19:34:44] GaborHojtsy: plach: no, we don't (yet?) have a doodle on the property translation bof :)
[19:35:14] GaborHojtsy: also for the record, wanted to schedule a specific time to talk about config translation but heyrocker did not want to fix a specific timeslot because "he is available anytime"
[19:35:31] plach: GaborHojtsy: what about joining the main entity bof?
[19:35:49] GaborHojtsy: plach: yeah, I don't want to take it over, but we can try :)
[19:36:22] plach: GaborHojtsy: maybe schedule an appendix ?
[19:36:43] plach: GaborHojtsy: is there a date scheduled for it yet?
[19:37:17] GaborHojtsy: plach: I think fago decided on a timeslot for it, but don't see it in the schedule
[19:38:21] GaborHojtsy: plach: I dropped you and fago an email
[19:38:30] GaborHojtsy: plach: let's see if that works :)
[19:39:02] GaborHojtsy: weal: thank you for signing up for the sprint next week, looking forward to working together again :)
[19:39:18] plach: GaborHojtsy: however, count me in for both the entity/entity translation and i18n CMI bofs anywhere/anytime ;)
[19:40:11] weal: GaborHojtsy: no problemo, I'm very happy to be contributing more!  I've been working full-time with Drupal since Sept 2008.
[19:41:54] GaborHojtsy: plach: ok, dropping you and hejrocker and email on the CMI discussion too :)
[19:43:22] weal: ok, I'm signing off... gotta get back to business hours!
[19:43:52] GaborHojtsy: weal: sure, thanks!
[19:44:10] GaborHojtsy: plach: so hope we can fix times for these :)
[19:44:38] GaborHojtsy: plach: BTW I'm planning to attend the Florian/Suzanne talk mainly for the questions after it which always help understand current common problems/requests better
[19:44:51] GaborHojtsy: plach: and am holding the questions/answers BoF on multilingual for similar reasons
[19:45:07] GaborHojtsy: plach: basically filling up on more real user feedback :)
[19:45:30] GaborHojtsy: plach: eg. we can bring the new translation UI to the question/answer BoF and ask for some feedback there if time allows
[19:46:21] floretan (~floretan@p549A55ED.dip.t-dialin.net) joined the channel.
[19:46:25] plach: GaborHojtsy: yes, that could be a good plan
[19:47:29] Etern4L (~quassel@46.12.14.235.dsl.dyn.forthnet.gr) joined the channel.
[19:47:32] GaborHojtsy: plach: but we should plan on cornering Bojhan and yoroy :)
[19:47:35] GaborHojtsy: too
[19:47:52] GaborHojtsy: plach: eg. book them for a lunch or breakfast or something, we can coordinate on site :)
[19:48:01] Bojhan is not going to be at drupalcon
[19:48:09] GaborHojtsy: Bojhan: uhm :/
[19:48:15] GaborHojtsy: Bojhan: double uhm :/
[19:48:25] Bojhan: GaborHojtsy: yoroy will be around
[19:49:01] plach: GaborHojtsy: sounds good, yoroy expressed interest for the new ET UI too
[19:49:18] GaborHojtsy: ok, good, we'll corner yoroy then :)
[19:49:20] plach: GaborHojtsy: so it should jjust be matter of scheduling a meetingù
[19:49:33] GaborHojtsy: plach: yup
[19:49:42] plach: I'd have to go now
[19:49:46] plach: anyithing left?
[19:49:58] GaborHojtsy: plach: I'll drop you and yoroy an email too :P
[19:50:02] GaborHojtsy: plach: nothing else from me :)
[19:50:10] webflo (~Adium@gateway.digi-info.de) left IRC. (Quit: Leaving.)
[19:51:27] plach: GaborHojtsy: ok, thanks
[19:52:02] plach: bye
[19:52:08] plach (~chatzilla@host251-166-static.42-88-b.business.telecomitalia.it) left IRC. (Quit: ChatZilla 0.9.88.1 [Firefox 10.0.2/20120215223356])
[19:52:18] GaborHojtsy: webchick++
[19:52:24] GaborHojtsy: webchick: thanks for asking the right questions :D
[19:52:30] fubhy is now known as fubhy|afk
[19:52:53] webchick: Aw. :)
[19:52:57] webchick: I try :D
[19:53:42] GaborHojtsy: so that concludes are two hour long meeting :) that was planned for an hour :) good turnout, thanks again everybody!