View Source

<ac:macro ac:name="toc" />


<li>Date: 11 January 2012, 18:00-19:00 UTC</li>
<li><ac:link><ri:page ri:content-title="2012-01-11 Meeting Agenda" /><ac:link-body>Agenda</ac:link-body></ac:link></li>
<li>Moderator: Evan Coury (nickname EvanDotPro)</li>
<li>Next meeting: 25 January 2012</li>


<h3>Finalize Beta3 Components</h3>

<p>Matthew raised a thread on the mailing list to start the ball rolling on finalizing the list of components for Beta3:</p>

<li><a class="external-link" href=""></a></li>

<p>Discussion ranged for some time, but the following was agreed upon:</p>

<li>Beta3 will drop last week of February; components to be included should be code complete the previous week to allow for review.</li>
<li>Components slated for beta3:
<li>Cloud (should be done Thursday, 12 Jan 2012)</li>
<li>Config (almost complete)</li>
<li>Log (almost complete)</li>
<li>DB (in process, and limited scope; see <a href="">Ralph's post</a>)</li>
<li>View (<ac:link><ri:page ri:content-title="RFC - View Layer" /><ac:link-body>RFC now available</ac:link-body></ac:link>)</li>
<li>Console (Artur Bodera, aka Thinkscape, will spearhead, and piggy-back off of View)</li>
<li>Components slated for beta4:
<li>i18n/l10n <ac:emoticon ac:name="question" /></li>

<h3>ZF 1.X EOL</h3>

<p>Matthew indicated he's had a lot of inquiries surrounding community plans for the ZF 1.X end-of-life &ndash; how long we'll be supporting it, and to what extent.</p>

<p>Opinions ranged a ton, but the following was agreed upon:</p>

<li>1.12 will be the last minor release of the 1.X series</li>
<li>Once 2.0 is marked stable, 1.12 will receive support for 18 months; such support will include only critical and security bugfixes.</li>
<li>Most agreed that the community should spearhead the EOL support. The consensus is to ask members of the existing CR Team who rely on ZF 1.X sites to assist, and to solicit additional volunteers via the mailing list (Mike Willbanks, aka lubs, volunteered during the meeting).</li>

<h3>Brainstorm ZF2 Module Options</h3>

<p>Evan Coury indicated he's run into a number of situations where he needs direct access to module-specific configuration options. His examples included cases where he needed authentication adapters to hint whether or not a redirect was needed, whether or not an authentication adapter should select by username, and more (URLs are in the log, below). Right now, he's using static members on his module class that he sets during bootstrapping; the question is how we want to handle this as a framework.</p>

<p>Matthew indicated he's accomplished similar goals typically via direct injection via event listeners registered within a scope that has access to the application configuration. Several others voiced approval for this method, but also indicated it comes at a cost of complexity and education.</p>

<p>In the end, we decided there was not sufficient use cases or discussion prior to the meeting to warrant further discussion at this time; Evan promised to follow up on the list and in IRC.</p>


<ac:macro ac:name="html"><ac:parameter ac:name="output">html</ac:parameter><ac:plain-text-body><![CDATA[
pre.log {
white-space: -moz-pre-wrap; /* Mozilla, supported since 1999 */
white-space: -pre-wrap; /* Opera 4 - 6 */
white-space: -o-pre-wrap; /* Opera 7 */
white-space: pre-wrap; /* CSS3 - Text module (Candidate Recommendation) */
word-wrap: break-word; /* IE 5.5+ */
border: 1px solid darkgray;
padding: 0.5em;
<pre class="log">
Jan 11 18:01:20 &lt;EvanDotPro&gt; alright.. let's get right into it... item #1, finalizing beta3 components
Jan 11 18:01:31 &lt;EvanDotPro&gt; agenda is here:
Jan 11 18:02:03 &lt;DASPRiD&gt; Beta 3 date was when?
Jan 11 18:02:27 &lt;EvanDotPro&gt; the priorities for Beta3 are currently View, Forms, and Db... with the other scheduled components being lower priority in favor of finishing the key componenets.
Jan 11 18:02:53 &lt;weierophinney&gt; DASPRiD, 4-6 weeks.
Jan 11 18:02:58 &lt;Thinkscape&gt; I'd propose we start with defining a desirable deadline
Jan 11 18:03:08 &lt;DASPRiD&gt; Opening links here is damn slow
Jan 11 18:03:27 &lt;weierophinney&gt; For those who haven't seen, I posted the View RFC today:
Jan 11 18:03:37 &lt;Thinkscape&gt; ralphschindler: do you see Db coming to an early working prototype in 4 weeks time ?
Jan 11 18:03:42 &lt;DASPRiD&gt; Config should be good for B3 then
Jan 11 18:03:54 &lt;Thinkscape&gt; DASPRiD: remember me ? :)
Jan 11 18:03:55 &lt;weierophinney&gt; Thinkscape, ralphschindler posted a list of targets for beta3 AND beta4
Jan 11 18:04:12 &lt;weierophinney&gt; with the assumption of 4-6 weeks for each beta
Jan 11 18:04:13 &lt;ralphschindler&gt; yep
Jan 11 18:04:36 &lt;ocra|afk&gt; Saw. Mwop, is there alreasy some sode or just rfc?
Jan 11 18:04:52 &lt;ocra|afk&gt; S/sode/code
Jan 11 18:04:53 &lt;weierophinney&gt; I think View is do-able, now that the RFC is ready, though we'll need to vote on it soonish.
Jan 11 18:05:05 &lt;weierophinney&gt; ocra|afk, no, but it's actually pretty minimal in terms of code.
Jan 11 18:05:49 &lt;weierophinney&gt; ocra|afk, runs an event to get a renderer, passes to a renderer, and then triggers another event for response munging.
Jan 11 18:06:17 &lt;weierophinney&gt; The one bit I'm unsure on is Forms, as I'm still in early processes of creating an RFC.
Jan 11 18:06:42 &lt;EvanDotPro&gt; do we want to set any sort of target date to give people a psychological deadline?
Jan 11 18:07:16 &lt;weierophinney&gt; EvanDotPro, how about last week of February? That's actually around six weeks.
Jan 11 18:07:31 &lt;DASPRiD&gt; Re
Jan 11 18:07:33 &lt;DASPRiD&gt; Bah, I don't even notice when I'm disconnected :(
Jan 11 18:07:33 &lt;weierophinney&gt; with the idea that code should be complete the week prior.
Jan 11 18:07:43 &lt;lsmith&gt; weierophinney: while event driven view rendering seems very flexible .. it should also be noted that events tend to be a bitch to debug and basically require a step by step debugger to grasp .. so i would be quite cautious with events
Jan 11 18:07:59 &lt;EvanDotPro&gt; that sounds fair to me.. ralphschindler does that seem realistic with Db?
Jan 11 18:08:24 &lt;weierophinney&gt; lsmith, please read the RFC before making a judgment like that.
Jan 11 18:08:46 &lt;weierophinney&gt; lsmith, the events are for strategy selection and response munging specifically -- they're more like filter chains in this regard.
Jan 11 18:08:50 &lt;EvanDotPro&gt; lsmith: the RFC is still very much an RFC.. feel free to read it and comment
Jan 11 18:09:03 &lt;lsmith&gt; weierophinney: i have .. well skimmed it just now
Jan 11 18:09:14 &lt;EvanDotPro&gt; right now we're just talking about what components will be scheduled for b3. :)
Jan 11 18:09:43 &lt;ralphschindler&gt; EvanDotPro: it is reasonable
Jan 11 18:09:45 &lt;weierophinney&gt; EvanDotPro, besides View, DB, and possibly Forms, it looks like Config and Log are about complete.
Jan 11 18:09:52 &lt;ralphschindler&gt; thats what my email was assuming
Jan 11 18:10:00 &lt;lsmith&gt; but i think its very smart that you guys are considering shipping a "view layer" out of the box .. thats missing in Symfony2 core
Jan 11 18:10:06 &lt;DASPRiD&gt; Evan: count config in.
Jan 11 18:10:23 &lt;weierophinney&gt; EvanDotPro, and ezimuel is almost done getting Cloud migrated and refactored to ZF2 -- should be done by tomorrow.
Jan 11 18:10:29 &lt;EvanDotPro&gt; weierophinney: possibly forms? should we make a decision on that now?
Jan 11 18:10:36 &lt;weierophinney&gt; EvanDotPro, good point. :)
Jan 11 18:10:50 &lt;EvanDotPro&gt; k -- counting Config and Cloud in for b3.
Jan 11 18:10:57 &lt;weierophinney&gt; lsmith, thanks -- it's been a common request, and we felt it necessary to add.
Jan 11 18:11:01 &lt;DASPRiD&gt; Yay forms ;)
Jan 11 18:11:01 &lt;Thinkscape&gt; I'd set up forms discussion in 2 weeks time, with an RFC and possibly a prototype to bash :)
Jan 11 18:11:36 &lt;weierophinney&gt; Thinkscape, with that, though, would we have time to get it in beta3? Also, in 2 weeks time, I won't be able to attend the meeting, as I'll be travelling to phpbnl. :-/
Jan 11 18:11:37 &lt;skiller&gt; +1 for view layer :)
Jan 11 18:11:43 &lt;lsmith&gt; for content type negotiation i have been meaning to sit down and implement mod_negotiation in php
Jan 11 18:11:57 &lt;lsmith&gt; maybe something we can collaborate on ..
Jan 11 18:12:00 &lt;Thinkscape&gt; that's 2 weeks out of 6 available..
Jan 11 18:12:06 &lt;weierophinney&gt; lsmith, that would be awesome -- it could be consumed as a strategy easily.
Jan 11 18:12:18 &lt;Thinkscape&gt; weierophinney: "DefaultStrategy" :)
Jan 11 18:12:19 &lt;weierophinney&gt; lsmith, let's discuss elsewhere, though -- off topic for this meeting.
Jan 11 18:12:27 &lt;lsmith&gt; k
Jan 11 18:12:30 &lt;EvanDotPro&gt; yeah let's stay on topic :)
Jan 11 18:12:40 &lt;weierophinney&gt; Thinkscape, damn, I meant to add that to the RFC, too. I'll update with that after the meeting.
Jan 11 18:12:47 &lt;Thinkscape&gt; Who's the Forms leader?
Jan 11 18:12:49 &lt;DASPRiD&gt; Neop: maybe we meet there
Jan 11 18:12:57 &lt;DASPRiD&gt; Mwop
Jan 11 18:12:58 &lt;SpiffyJr&gt; weierophinney, he is
Jan 11 18:13:12 &lt;weierophinney&gt; Thinkscape, right now, me, but if I get a reasonable RFC in place, there are a number of folks who have expressed interest in helping code it.
Jan 11 18:13:15 »» SpiffyJr is sad he's missed most the meeting already
Jan 11 18:13:15 &lt;EvanDotPro&gt; so to recap, we have View, Db, Config, and Cloud slated for release with Beta3 at the end of Feb.
Jan 11 18:13:19 &lt;Thinkscape&gt; ok, so it's up to you man, to say if 2 weeks is enough for an RFC to talk about on irc...
Jan 11 18:13:25 &lt;Thinkscape&gt; and then 4 weeks to implement fully...
Jan 11 18:13:29 &lt;weierophinney&gt; EvanDotPro, and Log
Jan 11 18:13:41 »» EvanDotPro adds Log to that list
Jan 11 18:13:47 &lt;skiller&gt; I understand that Console is out of scope for b3… do you think there is a chance it will make it to b4? Not sure how to read the statement about the availability.
Jan 11 18:13:51 &lt;weierophinney&gt; Thinkscape, well, 3. And don't forget there's work on View, too. :)
Jan 11 18:14:07 &lt;weierophinney&gt; Thinkscape, want to address skiller here -- that's also on-topic.
Jan 11 18:14:16 &lt;Thinkscape&gt; weierophinney: in any case - it's your time you're allocating
Jan 11 18:14:27 &lt;weierophinney&gt; Thinkscape, it sounds a bit like you need View to be ready for Console...
Jan 11 18:14:35 &lt;Thinkscape&gt; yep
Jan 11 18:14:44 &lt;DASPRiD&gt; Really?
Jan 11 18:14:49 &lt;EvanDotPro&gt; so would it be safe to say Forms might be pushed to beta4
Jan 11 18:14:54 &lt;MikeA&gt; Is it essential that the view layer is well on before forms, or can development be run in conjunction?
Jan 11 18:15:00 &lt;weierophinney&gt; Thinkscape, though could you work on the application and routing layers before it's ready?
Jan 11 18:15:09 &lt;Thinkscape&gt; I feel it'd be great to have a "pure" MVC which allows for interactive input (CLI) requests and responses (console output).
Jan 11 18:15:17 &lt;Thinkscape&gt; weierophinney: yes
Jan 11 18:15:20 &lt;weierophinney&gt; EvanDotPro, let's target beta4 for forms. If we get it done for beta3, great, but if not, we've set the expectation.
Jan 11 18:15:44 &lt;Kit-10&gt; i second that weierophinney
Jan 11 18:15:52 &lt;iH8&gt; weierophinney, what happens to View\Helpers?
Jan 11 18:15:53 &lt;weierophinney&gt; MikeA, they could be in conjunction. The only view-related part of forms would be view helpers, and those can be done anytime.
Jan 11 18:15:55 &lt;DASPRiD&gt; +1
Jan 11 18:16:07 &lt;Thinkscape&gt; That said, console prototype can follow view. Routing too. I think 6 wks is enough for me to prepare a working prototype
Jan 11 18:16:11 &lt;MikeA&gt; weierophinney: +1
Jan 11 18:16:13 &lt;weierophinney&gt; iH8, they're already in place. the view layer is actually _above_ the renderer, which is pretty stable right now.
Jan 11 18:16:16 &lt;Thinkscape&gt; (so people can play in console at last)
Jan 11 18:16:40 &lt;weierophinney&gt; Thinkscape, working prototype as in "include in beta3"?
Jan 11 18:16:42 &lt;EvanDotPro&gt; I18N? we had it slated for B2 originally..
Jan 11 18:16:53 &lt;Thinkscape&gt; yes, thought with no api freeze.
Jan 11 18:17:09 &lt;weierophinney&gt; EvanDotPro, I'm going to say beta4 on that, and I need to push thomas a bit harder to be more inclusive in his process.
Jan 11 18:17:15 &lt;Thinkscape&gt; i18n's kinda stalled
Jan 11 18:17:16 &lt;weierophinney&gt; so that it can actually happen
Jan 11 18:17:30 &lt;weierophinney&gt; Thinkscape, our betas do not imply an api freeze, so that'd be okay. :)
Jan 11 18:17:37 &lt;Thinkscape&gt; weierophinney: is there any exit strategy ? anyone who can take over from Thomas?
Jan 11 18:17:48 &lt;weierophinney&gt; Thinkscape, that's what I'm unsure of.
Jan 11 18:18:05 &lt;weierophinney&gt; Thinkscape, he's done a CLDR-based l10n layer, which requires a fair bit of knowledge.
Jan 11 18:18:16 &lt;DASPRiD&gt; I *cohld*...
Jan 11 18:18:23 &lt;weierophinney&gt; Thinkscape, if we were to downgrade to just using ext/intl, sure, we could do it, but we'd lose capabilities.
Jan 11 18:18:35 &lt;Thinkscape&gt; DASPRiD: hahhahha :)
Jan 11 18:18:42 &lt;DASPRiD&gt; I'm familiar with cldr
Jan 11 18:18:46 &lt;Thinkscape&gt; weierophinney: I've noticed there are already some missing features from zf1
Jan 11 18:18:56 &lt;DASPRiD&gt; Thanks to iCal rfc
Jan 11 18:19:14 &lt;weierophinney&gt; So, recap:
Jan 11 18:19:27 &lt;EvanDotPro&gt; Acl and Auth was also scheduled for beta3 in a past meeting...
Jan 11 18:19:31 &lt;weierophinney&gt; beta2: View, DB, Log, Console, Cloud,
Jan 11 18:19:46 &lt;weierophinney&gt; beta3: Form, i18n/l10n(?)
Jan 11 18:19:55 &lt;weierophinney&gt; sorry, that should be beta3 and beta4, respectively.
Jan 11 18:19:56 &lt;Thinkscape&gt; wait, beta2 ?
Jan 11 18:19:59 &lt;Thinkscape&gt; :0
Jan 11 18:20:02 &lt;weierophinney&gt; Thinkscape, ^^
Jan 11 18:20:05 &lt;DASPRiD&gt; Lol
Jan 11 18:20:10 &lt;Thinkscape&gt; EvanDotPro: you should do the recap :)
Jan 11 18:20:11 &lt;DASPRiD&gt; Typo :P
Jan 11 18:20:22 &lt;skiller&gt; Yay for Console in b3, terrific!
Jan 11 18:20:24 &lt;EvanDotPro&gt; to paste from my notes...
Jan 11 18:20:25 &lt;weierophinney&gt; EvanDotPro, no RFCs as yet for refactoring on either, so no way to schedule at this time.
Jan 11 18:20:26 &lt;EvanDotPro&gt; * Beta3 target for last week of February. Components slated to be ready: Config, Cloud, Db Log, View
Jan 11 18:20:27 &lt;ocra|afk&gt; How's ezimuel on cloud?
Jan 11 18:20:30 &lt;EvanDotPro&gt; * Components re-scheduled for Beta4: i18n/l10n, Form (with remote possibility to be in B3)
Jan 11 18:20:37 &lt;DASPRiD&gt; Mwop: back to the future :P
Jan 11 18:20:45 &lt;ezimuel&gt; ocra|afk: i will finish the cloud stuff tomorrow
Jan 11 18:20:47 &lt;weierophinney&gt; ocra|afk, ezimuel is hours away from completing migration
Jan 11 18:21:02 &lt;weierophinney&gt; ocra|afk, but hours away means tomorrow, as it's end of day for him now. :)
Jan 11 18:21:04 &lt;MikeA&gt; So what about ACL and Auth?
Jan 11 18:21:15 &lt;ocra|afk&gt; +1 for console pushed into priorities...
Jan 11 18:21:16 &lt;EvanDotPro&gt; weierophinney: for Authentication, I haven't heard anyone be vocally in favor of my proposed refactoring, so I'll likely drop that.
Jan 11 18:21:35 &lt;weierophinney&gt; MikeA, see above -- nobody has indicated they're working on RFCs, other than EvanDotPro for Authentication at this time -- which has been.. #zftalk.2
Jan 11 18:21:38 &lt;ocra|afk&gt; Mwop: awesome!
Jan 11 18:21:58 &lt;weierophinney&gt; EvanDotPro, does this mean we can move on to the next topic?
Jan 11 18:22:05 &lt;DASPRiD&gt; Do for i18n l10n: I could take over if required
Jan 11 18:22:09 &lt;skiller&gt; EvanDotPro: umm... Re Auth: got a link?
Jan 11 18:22:14 &lt;weierophinney&gt; DASPRiD, noted.
Jan 11 18:22:16 &lt;MikeA&gt; weierophinney: that's a shame because I though EvanDotPro was on the right path
Jan 11 18:22:27 »» Aldemar wasn't it going to be Zend/Access by the way?
Jan 11 18:22:41 &lt;Thinkscape&gt; mmm...
Jan 11 18:22:41 &lt;EvanDotPro&gt; skiller: it's on the mailing list, bug me for a link after the meeting in #zftalk.2
Jan 11 18:22:46 &lt;Thinkscape&gt; we could try to push it a little bit
Jan 11 18:22:46 &lt;DASPRiD&gt; Sounds like ms access :P
Jan 11 18:22:49 &lt;weierophinney&gt; MikeA, the problem is the path is app-specific. I'll dig up the discussions for you later if desired.
Jan 11 18:22:59 &lt;weierophinney&gt; Aldemar, no, Acl, to describe the approach.
Jan 11 18:23:04 &lt;skiller&gt; EvanDotPro: thx
Jan 11 18:23:06 &lt;EvanDotPro&gt; Okay... NEXT TOPIC: ZF 1.X EOL
Jan 11 18:23:10 »» EvanDotPro puts fist down
Jan 11 18:23:16 &lt;ocra|afk&gt; Edp: like your auth but would limit it to an adapter for now...
Jan 11 18:23:58 &lt;weierophinney&gt; So, lots of folks are asking about ZF1 EOL with ZF2 on the horizon.
Jan 11 18:24:14 &lt;Thinkscape&gt; weierophinney: how are they asking?
Jan 11 18:24:17 &lt;EvanDotPro&gt; so i'd say this next topic is mostly on the shoulders of the Zend team.. but it would be nice to get feedback from the community... probably most of us ZF2 early adopters have zf2 apps in production that we'd like to have a clear picture of support for.
Jan 11 18:24:17 &lt;weierophinney&gt; The big questions are: how long will it be supported? and who will do the supporting.
Jan 11 18:24:20 &lt;Thinkscape&gt; Like in a positive way ?
Jan 11 18:24:31 &lt;weierophinney&gt; Thinkscape, clients, twitter, IRC, email, lots of places.
Jan 11 18:24:38 &lt;Thinkscape&gt; no, not the places, but the tone...
Jan 11 18:24:49 &lt;Thinkscape&gt; Is it like: "Please please keep zf1 alive"
Jan 11 18:24:54 &lt;Thinkscape&gt; or "get over it" ?
Jan 11 18:24:57 &lt;weierophinney&gt; Thinkscape, many are worried, as they've developed large ZF1 infrastructures.
Jan 11 18:25:01 &lt;EvanDotPro&gt; there's also the possibility of utilizing the CR team or establishing a new team to manage the zf1.x maintenance to keep the Zend team resources freed up for ZF2.
Jan 11 18:25:28 &lt;weierophinney&gt; Thinkscape, that said, I'd also characterize those asking as primarily corporate users (or freelancers developing for corporate clients)
Jan 11 18:25:29 &lt;ocra|afk&gt; I'd freeze it and keep only updates
Jan 11 18:25:38 &lt;StephanFX&gt; weierophinney: i am one of those, have 2 major projects on ZF1
Jan 11 18:25:39 &lt;MikeA&gt; Bad marketing to make any decision now -- ZF2 need to be much further on
Jan 11 18:25:45 &lt;leedavis81_&gt; As a bit of an outsider, and a dev who's used ZF1.x on several projects, I'd rather the EOL be as near as practically possible. It gives me ammo to entice the business(es) to invest my time on the next evolution.
Jan 11 18:25:47 &lt;weierophinney&gt; EvanDotPro, that's my main question at thsi time: how we assign responsibility.
Jan 11 18:25:51 &lt;ocra|afk&gt; It is clear there's not many people with time to contribute...
Jan 11 18:26:13 &lt;iH8&gt; i would decide on what components are considered "core" in ZF1
Jan 11 18:26:18 &lt;EvanDotPro&gt; so let's establish two things... a timeline for zf1.x support, and delegation of the responsibility of said support.
Jan 11 18:26:21 &lt;iH8&gt; and focus on them
Jan 11 18:26:22 &lt;Thinkscape&gt; EvanDotPro: it sounds like a good idea. People who depend on and are avid zf1 users should hold the maintenance responsibility.
Jan 11 18:26:32 &lt;weierophinney&gt; I've discussed it with Zeev a fair bit, and 18 months seems reasonable -- a lot of people need that long to come up with a migration plan and implement it.
Jan 11 18:26:43 &lt;weierophinney&gt; (corporate/enterprise development is often very, very slow)
Jan 11 18:26:58 &lt;DASPRiD&gt; Re
Jan 11 18:27:00 &lt;DASPRiD&gt; Stupid connection
Jan 11 18:27:15 &lt;skiller&gt; It sounds like 1.12 will be the last dot release of ZF1, and I'd like to make that clear (even now), but offer extended bug/security patch support
Jan 11 18:27:21 &lt;Aldemar&gt; I think that support should go until a major release of zf2 is alive (I mean ZF2.1)
Jan 11 18:27:34 &lt;jowoz&gt; As a corporate user I could handle a freeze but I'd like to see a couple of years worth of security updates. Some of the apps I deal with are far too big to port to ZF2. I'd never be given the funds to do it.
Jan 11 18:27:37 &lt;DASPRiD&gt; At least two of mine :(
Jan 11 18:27:38 &lt;weierophinney&gt; skiller, that's the idea -- 1.12 becomes last minor release branch, and gets only critical and/or security fixes.
Jan 11 18:27:39 &lt;MikeA&gt; Aldemar: +1
Jan 11 18:27:47 &lt;skiller&gt; 18mo sound good, but 3ys would be better :)
Jan 11 18:28:02 &lt;Jigal&gt; would it be an idea to make the last release of 1.X a migration script of ZF1 to ZF2? Or will that be impossible?
Jan 11 18:28:04 &lt;EvanDotPro&gt; i think we could have two support timelines
Jan 11 18:28:07 &lt;Thinkscape&gt; I'd say it all lies in details - the "infrastructure" you mentioned, I understand it as dozens of controllers, helpers, plugins and such. They won't break from day-to-day, or even one year from now. They possibly will live until the end of PHP 5.x branch. So it's rather a question of security updates...
Jan 11 18:28:21 &lt;EvanDotPro&gt; maybe one date that is backed up by Zend, and a second date beyond that which falls on the community to support.
Jan 11 18:28:23 &lt;Thinkscape&gt; i.e. do we consider Zend_Service_* upgrades as APIs change ?
Jan 11 18:28:39 &lt;weierophinney&gt; Jigal, probably impossible. We'll likely build tools _after_ zf2 is out to assist with migration. But they'd be a separate project.
Jan 11 18:28:40 &lt;leedavis81_&gt; EvanDotPro +1
Jan 11 18:28:46 &lt;Thinkscape&gt; Jigal: i'd say more of a migration FAQ, not script.
Jan 11 18:28:46 &lt;ocra|afk&gt; What would still be maintained in 18 months?
Jan 11 18:29:16 &lt;weierophinney&gt; Thinkscape, if they need upgrades to Service components, we can direct them to the ZF2 equivalents.
Jan 11 18:29:25 &lt;ocra|afk&gt; Also I'd NOT support 5.4
Jan 11 18:29:45 &lt;DASPRiD&gt; Idd, its not full stack after all
Jan 11 18:29:46 &lt;Thinkscape&gt; weierophinney: we could _always_ direct them to zf2, but ^^ what you said before
Jan 11 18:29:47 &lt;weierophinney&gt; ocra|afk, well, we'll likely still work in 5.4 regardless; I've already tested on it. :)
Jan 11 18:29:51 &lt;skiller&gt; I, personally, wouldn't tie the EOL of 1.x to the "birth" of 2.0 . There are plenty of projects that remain pretty much unchanged for years.
Jan 11 18:29:57 &lt;Jigal&gt; Ok. But maybe it will be good to write down somewhere in a prominent place in the 1.x manual that EOL will be within an x period so new people will have a clear knowledge of that b4 starting new projects with 1.X
Jan 11 18:30:14 &lt;weierophinney&gt; Jigal, +1
Jan 11 18:30:21 &lt;ocra|afk&gt; Mwop: better, but without warranties...
Jan 11 18:30:31 &lt;skiller&gt; EvanDotPro: +1 Re: 2 support timelines
Jan 11 18:30:42 &lt;DASPRiD&gt; Skiller, by support, we probably mean security and critical bugs
Jan 11 18:30:55 &lt;StephanFX&gt; will this be 18 months on the release of zf1.12 or release of zf2?
Jan 11 18:31:00 &lt;weierophinney&gt; EvanDotPro, skiller -- not sure I agree. Infrastructure for building releases and pushing them is on my team.
Jan 11 18:31:09 &lt;Thinkscape&gt; I'd rather focus on defining _what_ does the x-month period mean? Security? Features? General bugs? Enhancements? Which packages?
Jan 11 18:31:10 &lt;Aldemar&gt; Support should not stop until a mature version of zf2 is on production
Jan 11 18:31:11 &lt;weierophinney&gt; StephanFX, that's one of the questions. :)
Jan 11 18:31:25 &lt;weierophinney&gt; Thinkscape, critical bugfixes and security fixes ONLY
Jan 11 18:31:26 &lt;Jigal&gt; aldemar: I agree!
Jan 11 18:31:54 &lt;lubs&gt; ok finally caught up after a team lunch
Jan 11 18:31:54 &lt;weierophinney&gt; Aldemar, we'll have a stable ZF2 version this year, likely w/in first half of year.
Jan 11 18:31:57 &lt;Jigal&gt; StephanFX, weierophinney i prefer after stable zf2 release
Jan 11 18:32:07 &lt;Thinkscape&gt; weierophinney: so basically that means that current release is the last one. is it ?
Jan 11 18:32:16 &lt;weierophinney&gt; Thinkscape, 1.12 will be.
Jan 11 18:32:17 &lt;StephanFX&gt; i would say zf2, to give dev a decent chance to catch up
Jan 11 18:32:24 &lt;Aldemar&gt; weierophinney: ppl is afraid of 0.0 versions
Jan 11 18:32:29 &lt;lubs&gt; with ZF 1.x I think it might be fair to also say there may be a 1.13 release as a backporting release for components in ZF 2?
Jan 11 18:32:38 &lt;weierophinney&gt; lubs, no
Jan 11 18:32:41 &lt;lubs&gt; k
Jan 11 18:32:41 &lt;Thinkscape&gt; how about: zf2 release date + 12 mo ?
Jan 11 18:32:55 &lt;ocra|afk&gt; Lubs -1
Jan 11 18:32:59 &lt;weierophinney&gt; lubs, we'll be adding things like EM and autoloaders to 1.12 -- but any sort of forward compats will be via a separate project.
Jan 11 18:33:03 &lt;Aldemar&gt; lubs, not agreed, it wouldn't be longer zf1
Jan 11 18:33:03 &lt;skiller&gt; If 18mo means 1.12 receives bug and security fixes until 18mo after 2.0 is out, all is well.
Jan 11 18:33:06 &lt;iH8&gt; Thinkscape +1
Jan 11 18:33:09 &lt;Jigal&gt; Thinkscape, if 18 months have been proven to be the right timespan why not sticking to that?
Jan 11 18:33:22 &lt;leedavis81_&gt; I think skiller was right, and we should tie the EOL of 1.x to the birth of 2.0
Jan 11 18:33:23 &lt;weierophinney&gt; skiller, that was my original suggestion.
Jan 11 18:33:23 &lt;Thinkscape&gt; MS broadcasts EOL timelines the moment they officially comercially release new version of MS Windows package.
Jan 11 18:33:23 &lt;ezimuel&gt; Thinkscape: I think 18 months is better after the zf2 release date
Jan 11 18:33:28 &lt;leedavis81_&gt; * shoudn't
Jan 11 18:33:35 &lt;lubs&gt; i'm fine with whatever in terms of the EOL; i know that internally it will take us about a year to restructure our application for zf2 (which we've started already)
Jan 11 18:33:49 &lt;skiller&gt; And I wouldn't provide migration scripts. Sounds like a recipe for headache.
Jan 11 18:34:12 &lt;weierophinney&gt; skiller, more like FAQ, but potentially some scripts to automate things like conversion to namespaces, mapping old classes to new, etc.
Jan 11 18:34:28 &lt;skiller&gt; weierophinney: thought so. Thanks for clarifying!
Jan 11 18:34:31 &lt;Thinkscape&gt; ok, so ZF2 Final (2.0.0) date + 18 mo ?
Jan 11 18:34:36 &lt;MikeA&gt; The more I think about this: any announcement before ZF2 release could cause fear for anyone contemplating a new ZF project
Jan 11 18:34:38 &lt;weierophinney&gt; Thinkscape, yes.
Jan 11 18:34:48 &lt;EvanDotPro&gt; so is anyone _against_ zf2 final + 18 months?
Jan 11 18:34:53 &lt;StephanFX&gt; Thinkscape, agreed
Jan 11 18:34:57 &lt;weierophinney&gt; MikeA, yes, we'd announce when ZF2 stable is released.
Jan 11 18:34:58 &lt;EvanDotPro&gt; or have any concerns about it?
Jan 11 18:34:59 &lt;Aldemar&gt; MikeA: I agree
Jan 11 18:35:00 &lt;ocra|afk&gt; Some articles about zf1-2 comparison on maybe
Jan 11 18:35:05 &lt;weierophinney&gt; ocra|afk, yep
Jan 11 18:35:06 &lt;iH8&gt; It al depends on critical issues per month, i don't think there's too many.
Jan 11 18:35:15 &lt;Thinkscape&gt; ok, so we decided on WHEN? now let's decide on WHO?
Jan 11 18:35:17 &lt;weierophinney&gt; iH8, that's the next point I want to bring up...
Jan 11 18:35:22 &lt;weierophinney&gt; Thinkscape, EXACTLY
Jan 11 18:35:48 &lt;weierophinney&gt; Part of this will require somebody examining incoming issues and determing if they are (a) critical, (b) security related, or (c) neither.
Jan 11 18:35:57 &lt;skiller&gt; MikeA: I think quite the contrary. "Hey people, we'll support 1.12 until way after 2.x is out" will probably soothe a lot of people who are developing ZF1 projects right now.
Jan 11 18:35:57 &lt;weierophinney&gt; In the case of (c), they can be marked "won't fix".
Jan 11 18:36:02 &lt;weierophinney&gt; The question is, who does that part?
Jan 11 18:36:15 &lt;weierophinney&gt; I'd like to nominate a release manager, ideally outside my team.
Jan 11 18:36:17 &lt;EvanDotPro&gt; i'm for establishing a community team
Jan 11 18:36:26 &lt;Thinkscape&gt; How about: which members of CR team use/depend on zf1 in their (corpo?) environments ?
Jan 11 18:36:32 &lt;skiller&gt; +1 for 2.0 + 18mo
Jan 11 18:36:33 &lt;StephanFX&gt; community team +1
Jan 11 18:36:38 &lt;EvanDotPro&gt; i'd like to keep our resources from Zend freed up for ZF2, and also those of the CR team if possible.
Jan 11 18:36:44 &lt;weierophinney&gt; Thinkscape, or adding folks to the CR Team who want to take that on.
Jan 11 18:37:07 &lt;EvanDotPro&gt; personally i'd like to see the CR team focused on zf2 as well... so maybe a specific ZF1 LTS team.
Jan 11 18:37:08 &lt;Thinkscape&gt; weierophinney: if we have such volunteers ;)
Jan 11 18:37:11 &lt;weierophinney&gt; Maybe I should send out a request to the ML, and we can see who is interested?
Jan 11 18:37:28 &lt;Aldemar&gt; weierophinney: when is it scheduled to release zf 2.0.0 ?
Jan 11 18:37:32 &lt;Thinkscape&gt; are you pro a single person responsible for that ? (leader)
Jan 11 18:37:53 &lt;EvanDotPro&gt; weierophinney: +1 for ml post.
Jan 11 18:38:11 &lt;StephanFX&gt; weierophinney: +1 for ml post
Jan 11 18:38:20 &lt;weierophinney&gt; Thinkscape, we'll likely need a pool of folks -- 18 months may be longer than an individual volunteer is willing.
Jan 11 18:38:24 &lt;EvanDotPro&gt; if no one steps up, maybe that's in indication of the importance of such support to the community (that may be a harsh assumption though)
Jan 11 18:38:33 &lt;Thinkscape&gt; EvanDotPro: too harsh
Jan 11 18:38:35 &lt;lubs&gt; weierophinney: i could assist in ZF 1.x; we're going to be stuck on it over the next year easily
Jan 11 18:38:50 &lt;Thinkscape&gt; it's 8pm here:P most devs are resting after their corpo work...
Jan 11 18:38:53 &lt;weierophinney&gt; Aldemar, hopefully no later than June -- depends on how fast these betas get out there and we zero in on stable MVC.
Jan 11 18:38:58 &lt;DASPRiD&gt; Re
Jan 11 18:39:10 &lt;DASPRiD&gt; So am I thibkscape :P
Jan 11 18:39:15 &lt;weierophinney&gt; lubs, cool.
Jan 11 18:39:19 &lt;weierophinney&gt; So, summary:
Jan 11 18:39:52 &lt;weierophinney&gt; * ZF 1.12 becomes last 1.X release, and continues to receive critical bugfix/security fix support ONLY starting from 2.0 stable release until 18 months following.
Jan 11 18:40:21 &lt;weierophinney&gt; * Matthew to send ML post to list asking for volunteers to act as RMs for 1.12.X once we hit that time.
Jan 11 18:40:34 »» Aldemar thinks 2.0+18months is too much :P I would say 12 months, in a year I think we might be already on zf2.1
Jan 11 18:40:59 &lt;lubs&gt; Aldemar: i think it is almost fair... however, porting over a complex architecture on ZF 1.x is not trivial
Jan 11 18:41:01 &lt;EvanDotPro&gt; Aldemar: unfortunately corporate development timelines are not very fast
Jan 11 18:41:09 &lt;Evil_Otto&gt; I'd suggest that the life expectancy of a zf1 application is more than 12 months
Jan 11 18:41:12 &lt;jowoz&gt; Would removing the CLA from ZF1 and moving it to github not help with the community helping out with security fixes?
Jan 11 18:41:13 &lt;DASPRiD&gt; True
Jan 11 18:41:18 &lt;skiller&gt; EvanDotPro: agreed 100%
Jan 11 18:41:31 &lt;iH8&gt; jowoz, great point
Jan 11 18:41:48 &lt;weierophinney&gt; jowoz, won't happen for ZF1 -- we need to keep the licensing and contribution guidelines the same for a given branch
Jan 11 18:42:11 &lt;weierophinney&gt; Otherwise 1.11 becomes the last version some folks can use due to legal issues.
Jan 11 18:42:29 &lt;skiller&gt; weierophinney: makes sense
Jan 11 18:42:49 &lt;EvanDotPro&gt; yeah, it's an unfortunate reality.
Jan 11 18:42:52 &lt;iH8&gt; there is no option to do so, move on :)
Jan 11 18:42:53 &lt;weierophinney&gt; kk... next topic?
Jan 11 18:43:05 &lt;EvanDotPro&gt; yeah next topic
Jan 11 18:43:09 &lt;EvanDotPro&gt; Brainstorm ZF2 Module Options
Jan 11 18:43:17 &lt;DASPRiD&gt; Note to myself: umts sucks at 300kmh
Jan 11 18:43:22 &lt;weierophinney&gt; EvanDotPro, we could do accessors for the config in the MvcEvent...
Jan 11 18:43:39 &lt;weierophinney&gt; EvanDotPro, that would solve like 90% or more of your use cases, I'd think...
Jan 11 18:43:41 &lt;skiller&gt; DASPriD What a fast car you have ;_)
Jan 11 18:43:50 &lt;EvanDotPro&gt; Bittarman: ping
Jan 11 18:44:25 &lt;DASPRiD&gt; Skiller: train
Jan 11 18:44:31 &lt;EvanDotPro&gt; weierophinney: possibly, but that starts playing the game of how do we make sure every object that is going to have any "options" logic be aware of the mvcevent or get the options injected into it.
Jan 11 18:44:40 &lt;skiller&gt; DASPRiD: thought so :)
Jan 11 18:44:58 &lt;weierophinney&gt; EvanDotPro, true.
Jan 11 18:45:04 &lt;skiller&gt; What's the approach that best matches DI?
Jan 11 18:45:13 &lt;weierophinney&gt; EvanDotPro, so far, I've gotten around it via DI.
Jan 11 18:45:13 &lt;Thinkscape&gt; One idea was config injection from application or mod.manager into a module, then SomeModule::getOption() and ::getConfig().
Jan 11 18:46:05 &lt;DASPRiD&gt; I should just do DNS tunneling with the train WiFi
Jan 11 18:46:06 &lt;weierophinney&gt; EvanDotPro, Thinkscape: also, if you're _in_ the Module class, you can grab the config from the event passed to the bootstrap event, and use it to pass to objects and/or closures.
Jan 11 18:46:27 &lt;EvanDotPro&gt; weierophinney: that's how i'm setting the static property now
Jan 11 18:46:28 &lt;weierophinney&gt; I've done that for things like my listeners, view helpers, etc.
Jan 11 18:46:46 &lt;DASPRiD&gt; Static...
Jan 11 18:46:48 &lt;Thinkscape&gt; Where I didn't like it was when view helpers and form elements started to query a module. Querying config settings from UI widgets seemed a bad architecture to me, because it should be the other way around - controller or view _configures_ a UI widget, and UI widgets complies accordingly.
Jan 11 18:46:49 &lt;EvanDotPro&gt; weierophinney:
Jan 11 18:47:13 &lt;Aldemar&gt; Thinkscape: I agree
Jan 11 18:47:21 &lt;Thinkscape&gt; Additionally, if you reuse those components ---- which module do I query ?
Jan 11 18:47:26 &lt;DASPRiD&gt; Thibkscape ack
Jan 11 18:47:34 &lt;EvanDotPro&gt; here's a use-case: ... that happens to be in a controller where passing the config in the MbvEvent _would_ work, but that's not always the case.
Jan 11 18:48:11 &lt;Thinkscape&gt; Also, if module A extends module B functionality but uses module A Form... then this form will have module A hard-coded as source of config options.
Jan 11 18:48:50 &lt;weierophinney&gt; EvanDotPro, see, I'd register with the dispatch() event, and inject the configuration from there (using high priority).
Jan 11 18:48:56 &lt;DASPRiD&gt; Indeed, please no registry like stuff again
Jan 11 18:49:07 &lt;weierophinney&gt; EvanDotPro, that can then be done from the module, and you have the configuration readily at hand at that point.
Jan 11 18:49:31 &lt;Thinkscape&gt; On the other hand, Bittarman or Akrabat (sorry) suggested that: if I import module A from vendor, I don't care about how it's form work - I just want to USE it and it is expected to work.
Jan 11 18:49:33 &lt;skiller&gt; weierophinney: +1 Re: register/dispatch/inject
Jan 11 18:49:33 &lt;lubs&gt; i also can see the value in statics within the actual module itself for options although...
Jan 11 18:50:16 &lt;Thinkscape&gt; weierophinney: this requires for each and every component to be injected ...
Jan 11 18:50:24 &lt;DASPRiD&gt; Lubs, statics are bad for re usability
Jan 11 18:50:30 &lt;EvanDotPro&gt; lubs: right.. that's the thing, you can't quantify where you'll need to access the options
Jan 11 18:50:37 &lt;lubs&gt; DASPRiD: the Module.php class itself is not really reusable
Jan 11 18:51:01 &lt;EvanDotPro&gt;
Jan 11 18:51:06 &lt;skiller&gt; Thinkscape, weierophinney: I'd favor the approach that alleviates mocking
Jan 11 18:51:07 &lt;weierophinney&gt; Thinkscape, it looks to me like a case of opting-in to specific configuration -- and if so, you can do that in your own logic.
Jan 11 18:51:15 &lt;DASPRiD&gt; No, but the components relying on those statics
Jan 11 18:51:16 &lt;Thinkscape&gt; link ^^ that's the example that I'm referring to
Jan 11 18:51:16 &lt;EvanDotPro&gt; (the inverse of that can be done too, add the element if the preference is enabled)
Jan 11 18:52:10 &lt;EvanDotPro&gt; and you may need access to the same setting in multiple places
Jan 11 18:52:18 &lt;EvanDotPro&gt; for example in the authentication adapter, you may have something like this:
Jan 11 18:52:24 &lt;weierophinney&gt; EvanDotPro, again, I'd argue in that case I'd want it injected early. But I'm seeing the issues.
Jan 11 18:52:26 &lt;lubs&gt; EvanDotPro: exactly... i can see the reasoning for having statics for say and administration panel where you need access to see enabled vs. disabled to provide a correct interface; also say you need to check to see if a module (from another module) has a certain configuration that may be shared but you need to check for it first... I mean there are ways around it but DI is only good if you don't let it get in your way and this seems like we are creati
Jan 11 18:52:50 &lt;weierophinney&gt; lubs, got cut off after "like we are creati"
Jan 11 18:53:11 &lt;lubs&gt; ...sometimes you might need the options outside of the module itself... for instance; say you have an administration panel where you take the options and provide an a
Jan 11 18:53:17 &lt;lubs&gt; grrr
Jan 11 18:53:22 &lt;lubs&gt; now my client is getting all fubared
Jan 11 18:53:25 &lt;Thinkscape&gt; skiller: good point, mocking. That negates the use of hard-coded calls to statics
Jan 11 18:53:33 &lt;DASPRiD&gt; Get a better client :P
Jan 11 18:53:40 &lt;EvanDotPro&gt; well, this sounds like this is something that needs a bit more collaborative thought and planning of use-cases at this point.
Jan 11 18:54:04 &lt;lubs&gt; basically all i am saying is that we can make it complex but all in all it's getting more complex for something that should be simple
Jan 11 18:54:09 &lt;DASPRiD&gt; Evan, let's talk about it when I'm home again ;)
Jan 11 18:54:26 &lt;weierophinney&gt; EvanDotPro, agreed -- I think we need to come up with a list of use cases where you're noticing issues, and discuss on the ML/IRC -- not enough info here to really discuss thoroughly.
Jan 11 18:54:33 &lt;Thinkscape&gt; lubs: it's not that simple. If you make it easy to use (in this case), you make it hard to test... and vice versa.
Jan 11 18:54:43 &lt;weierophinney&gt; Thinkscape, +1
Jan 11 18:54:57 &lt;skiller&gt; Thinkscape: True, those are a real pain to mock. We have terrific PHPUnit support, so let's not forget the busy testers. ;-)
Jan 11 18:54:58 &lt;ocra|afk&gt; Not getting it, missed cause of 3g. Discussing over staticness?
Jan 11 18:55:08 &lt;Thinkscape&gt; global $config is easiest :-) I use it even today with zf1 apps :P
Jan 11 18:55:10 &lt;Aldemar&gt; wouldn't ->getModule() ->setModule() and DI use, make the work?
Jan 11 18:55:11 &lt;DASPRiD&gt; +1
Jan 11 18:55:12 &lt;DASPRiD&gt; Mostly
Jan 11 18:55:14 &lt;lubs&gt; Thinkscape: i agree with that as well - just needs more thought :)
Jan 11 18:55:27 &lt;weierophinney&gt; I'll note that I've run into a few cases where using statics would simplify things, but I've always managed to find another way to accomplish it, either via bootstrapping and/or events, in combination with direct injection.
Jan 11 18:55:45 &lt;Thinkscape&gt; Aldemar: yes, but that is a double-edged sword. It requires to inject _EVERY_ component with the module :\
Jan 11 18:55:56 &lt;EvanDotPro&gt; weierophinney: i'll slate some time this week to walk through some use cases with you then.
Jan 11 18:56:07 &lt;Thinkscape&gt; and it is possibly a hard dep on di
Jan 11 18:56:10 &lt;weierophinney&gt; Aldemar, and I think one thing EvanDotPro is pointing out is that you may be using values from a module other than the one you're in.
Jan 11 18:56:26 &lt;EvanDotPro&gt; yes
Jan 11 18:56:26 &lt;Thinkscape&gt; EvanDotPro: why "with you"?
Jan 11 18:56:28 &lt;DASPRiD&gt; Tginkdcape stab youself :P
Jan 11 18:56:45 &lt;weierophinney&gt; EvanDotPro, s/with you/on the ML and\/or IRC/
Jan 11 18:56:51 &lt;EvanDotPro&gt; Thinkscape: i mean i want to discuss some of the solutions that weierophinney said he's come up with to alleviate the statics
Jan 11 18:56:56 &lt;weierophinney&gt; aha
Jan 11 18:57:12 &lt;EvanDotPro&gt; sorry, should have been more explicit there :)
Jan 11 18:57:23 &lt;DASPRiD&gt; Nah
Jan 11 18:57:59 &lt;EvanDotPro&gt; alright everyone... we're coming up on that time... i think we covered everything we could have hoped to cover today.
Jan 11 18:58:14 &lt;weierophinney&gt; So, summary of the last topic: Needs more discussion and use cases. :)
Jan 11 18:58:21 &lt;Aldemar&gt; :)
Jan 11 18:58:22 &lt;EvanDotPro&gt; yep
Jan 11 18:58:26 &lt;skiller&gt; +1
Jan 11 18:58:35 &lt;weierophinney&gt; I'll get the summary page up later today, and post a link to the ML and on twitter.
Jan 11 18:58:38 &lt;DASPRiD&gt; Hehe
Jan 11 18:58:50 &lt;Thinkscape&gt; thx
Jan 11 18:59:04 &lt;EvanDotPro&gt; alright everyone -- meeting adjourned! discussions can continue on #zftalk.2 if anyone has lingering thoughts.