View Source

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

<h2>Information</h2>

<ul>
<li>Date: 12 October 2011, 17:00-18:00 UTC</li>
<li><ac:link><ri:page ri:content-title="2011-10-12 Meeting Agenda" /><ac:link-body>Agenda</ac:link-body></ac:link></li>
<li>Moderator: Evan Coury (nickname EvanDotPro)</li>
</ul>


<h2>Summary</h2>

<p>This meeting primarily centered around the upcoming beta1, and planning for the betas that will immediately follow.</p>

<h3>Beta 1 Readiness</h3>

<ul>
<li>Documentation and examples need work</li>
<li>Matthew is working on MVC/module documentation</li>
<li>Ralph will be updating DI documentation with latest refactorings</li>
<li>Evan will provide Matthew with more module examples / documentation</li>
<li>ZF2 component packaging / pyrus channel distribution needs refined. Ralph and Matthew working on that today/tomorrow.</li>
<li>Evan to remove exception from di factory instantiator today</li>
</ul>


<p>Basically, things appear to be on target, with the primary thrust being completing initial documentation and getting the packaging process finalized.</p>

<h3>Milestones</h3>

<ul>
<li>Maximum beta release cycle of 6 weeks, with option to push beta releases before week 6 if ready.</li>
<li>Set up a milestone for refactoring components to the new options RFC. We should coordinate an effort to encourage component maintainers to do their part in refactoring their components.</li>
<li>Short-term component milestones: cache, locale/translator, log, mail, servers</li>
<li>Does acl/auth need any work or refactoring? Ralph mentioned going an RBAC route? Matthew wonders if ACL is already pretty much RBAC. (ACL/RBAC goals as possible topic for next meeting?)</li>
<li>Beta2: cache, log, mail, <em>possibly</em> locale/translator if possible</li>
<li>Beta3: server, acl, auth, db <ac:emoticon ac:name="question" /></li>
<li>Evan will work with Ralph and Matt Cockayne on possibly having module distribution via pyrus with cli install ready?</li>
</ul>


<p>Some components are currently being refactored by their leads, but with little transparency. Several contributors will be reaching out to these leads to find out status, and hopefully get that status posted publicly on the mailing list, along with what pieces could use help.</p>

<h3>Server RFC</h3>

<p>This part of the discussion referenced the <ac:link><ri:page ri:content-title="RFC - Server Classes" /><ac:link-body>RFC about Server class architecture</ac:link-body></ac:link>. </p>

<ul>
<li>No objections / negative feedback; couple of questions were quickly answered.</li>
<li>Marking RFC as accepted and safe to begin work on. Work will likely begin in the weeks following ZendCon if left to Matthew and Evan, though others are welcome to start helping sooner.</li>
</ul>


<h2>Log</h2>

<ac:macro ac:name="html"><ac:parameter ac:name="output">html</ac:parameter><ac:plain-text-body><![CDATA[
<style>
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) http://www.w3.org/TR/css3-text/#white-space */
word-wrap: break-word; /* IE 5.5+ */
border: 1px solid darkgray;
padding: 0.5em;
}
</style>
<pre class="log">
Oct 12 17:00:00 &lt;weierophinney&gt; EvanDotPro, take it away
Oct 12 17:00:02 &lt;EvanDotPro&gt; Alright, let's call this meeting to order. Greetings everyone!
Oct 12 17:00:14 &lt;weierophinney&gt; EvanDotPro is MODERATOR today
Oct 12 17:00:24 &lt;weierophinney&gt; In other words, HE CAN TELL YOU TO STOP TALKING. :)
Oct 12 17:00:35 &lt;EvanDotPro&gt; Okay, first up: beta 1 readiness... would anyone like to add to the list of "known issues" on the agenda, as far as outstanding tasks for tagging beta 1?
Oct 12 17:00:56 &lt;weierophinney&gt; EvanDotPro, I've got a few. :)
Oct 12 17:01:03 &lt;weierophinney&gt; * Documentation.
Oct 12 17:01:11 &lt;EvanDotPro&gt; those listed are: MVC documentation and examples, DI documentation and examples, and Module Manager documentation and examples
Oct 12 17:01:16 &lt;weierophinney&gt; I'm a couple hours out from having "adequate" docs for MVC done.
Oct 12 17:01:23 &lt;weierophinney&gt; which also includes an overview of modules.
Oct 12 17:01:31 &lt;weierophinney&gt; ralphschindler, where are we on DI docs?
Oct 12 17:01:48 &lt;intiilapa&gt; Hello
Oct 12 17:01:49 &lt;ralphschindler&gt; they need to be updated with refactorings
Oct 12 17:02:00 &lt;weierophinney&gt; ralphschindler, how long will that take?
Oct 12 17:02:10 &lt;weierophinney&gt; and do any additional examples need to be written up?
Oct 12 17:02:14 &lt;weierophinney&gt; and can anybody help you?
Oct 12 17:02:30 &lt;ralphschindler&gt; EvanDotPro: could probably help put examples into that use-case repository i have
Oct 12 17:02:40 &lt;ralphschindler&gt; 2-3 hours on completion
Oct 12 17:03:05 &lt;weierophinney&gt; ralphschindler, would end-of-day tomorrow for those be too hard to accomplish?
Oct 12 17:03:37 &lt;EvanDotPro&gt; ralphschindler: noted.. one of the example use-cases i have is instantiation via a static factory; without getting too far off topic, what's the status on that "incomplete implementation" exception being thrown there?
Oct 12 17:03:50 &lt;ralphschindler&gt; weierophinney: sounds reasonable
Oct 12 17:03:52 &lt;weierophinney&gt; EvanDotPro, are there any parts of the module manager you feel should be documented other than basic module creation and hooking in the module manager into bootstrapping?
Oct 12 17:04:00 &lt;weierophinney&gt; ralphschindler, cool, thx
Oct 12 17:04:15 &lt;weierophinney&gt; ralphschindler, see EvanDotPro's question above
Oct 12 17:04:15 &lt;ralphschindler&gt; EvanDotPro: I'm sure removing the exception might just fix that ;)
Oct 12 17:04:27 &lt;weierophinney&gt; EvanDotPro, sounds like a PR from you would fix that, then. :)
Oct 12 17:04:28 &lt;EvanDotPro&gt; weierophinney: possibly some use-cases for different module path locations and such; i can help writing those up.
Oct 12 17:04:53 &lt;weierophinney&gt; EvanDotPro, that would be awesome. I'm writing in markdown right now, and will convert to docbook using pandoc later
Oct 12 17:05:03 &lt;EvanDotPro&gt; weierophinney: prefect.
Oct 12 17:05:11 &lt;weierophinney&gt; So if you get me even a quick doc in markdown today or tomrrow morning, I can slip it in.
Oct 12 17:05:17 &lt;EvanDotPro&gt; ralphschindler: i'll submit a PR removing that exception then.
Oct 12 17:05:31 &lt;ralphschindler&gt; ok, test it out too
Oct 12 17:05:37 &lt;ralphschindler&gt; just to make sure it actually works ;)
Oct 12 17:05:50 &lt;EvanDotPro&gt; ralphschindler, weierophinney: will do
Oct 12 17:05:54 &lt;weierophinney&gt; Any other documentation issues?
Oct 12 17:06:20 &lt;jurians&gt; will DI include examples with the docs?
Oct 12 17:06:25 &lt;EvanDotPro&gt; how about any non-documentation related issues that should be wrapped up for prior to tagging beta 1?
Oct 12 17:06:30 &lt;weierophinney&gt; The bits I've done so far are an overview of the MVC, including modules; a "quick start" building an intitial module using the skeleton app/module repos, and a section on controllers.
Oct 12 17:06:44 &lt;weierophinney&gt; I have bits on the router, mvcevent, and exceptions I'll complete today.
Oct 12 17:06:52 &lt;weierophinney&gt; jurians, yes, examples are the main part of DI docs.
Oct 12 17:07:01 &lt;weierophinney&gt; EvanDotPro, non-doc issues: packaging.
Oct 12 17:07:06 &lt;weierophinney&gt; ralphschindler, want to give an update?
Oct 12 17:08:06 &lt;weierophinney&gt; I'll start filling in...
Oct 12 17:08:44 &lt;ralphschindler&gt; I'm not sure what you're asking
Oct 12 17:08:51 &lt;ralphschindler&gt; you want to know about all of the refactorings?
Oct 12 17:09:03 &lt;weierophinney&gt; ralphschindler, no, just a quick update on where packaging stands right now.
Oct 12 17:09:07 &lt;ralphschindler&gt; oh, packaging
Oct 12 17:09:17 &lt;weierophinney&gt; we have automatic dependency detemination going
Oct 12 17:09:28 &lt;ralphschindler&gt; we are close, right now trying to get optional dependencies working via our pyrus/pear channel server
Oct 12 17:09:36 &lt;ralphschindler&gt; we have a new repo with a testing branch where all of this is happening:
Oct 12 17:09:44 &lt;ralphschindler&gt; https://github.com/zendframework/ZF2Package/
Oct 12 17:09:45 &lt;weierophinney&gt; also, trying to figure out how to do "bundling" of packages.
Oct 12 17:10:03 &lt;weierophinney&gt; and ralphschindler is working with the pear/pyrus folks to try and get that figured out.
Oct 12 17:10:15 &lt;weierophinney&gt; We should have something working today or tomorrow.
Oct 12 17:10:27 &lt;weierophinney&gt; One aspect to this is figuring out how to publish docs.
Oct 12 17:10:28 &lt;PadraicB&gt; Sounds good ;)
Oct 12 17:10:44 &lt;weierophinney&gt; I'm likely going to simply generate them and push them to packages.zendframework.com as a temporary solution.
Oct 12 17:10:50 &lt;NickBelhomme&gt; publishing docs is good! ;) now we have them as files in the repo...
Oct 12 17:11:05 &lt;weierophinney&gt; NickBelhomme, agreed -- it's just figuring out how to do it. :)
Oct 12 17:11:12 &lt;weierophinney&gt; I think I'll make them unthemed for now.
Oct 12 17:11:19 &lt;EvanDotPro&gt; is all of that work strictly for packaging ZF2 components; or are we including module distribution under this effort as well?
Oct 12 17:11:34 &lt;intiilapa&gt; NickBelhomme: docs is already in repo for ZF1 O_O
Oct 12 17:11:35 &lt;weierophinney&gt; EvanDotPro, right now, just for the ZF2 components.
Oct 12 17:11:50 &lt;weierophinney&gt; We figured it's too much to try and do modules quite yet. Same principles will apply, though.
Oct 12 17:12:07 &lt;intiilapa&gt; weierophinney: maybe see with mikaelkael for the theme (if he can)
Oct 12 17:12:11 &lt;weierophinney&gt; PadraicB, anything you see as missing for beta1?
Oct 12 17:12:21 &lt;weierophinney&gt; intiilapa, kk. We're on a short schedule right now, though. :)
Oct 12 17:12:22 &lt;intiilapa&gt; we need a better template for the final release than ZF1 IMHO
Oct 12 17:12:30 &lt;EvanDotPro&gt; weierophinney: gotcha
Oct 12 17:12:33 &lt;weierophinney&gt; intiilapa, that's fine. We have time before then.
Oct 12 17:12:45 &lt;intiilapa&gt; weierophinney: I know
Oct 12 17:12:48 &lt;weierophinney&gt; PadraicB, see above?
Oct 12 17:13:24 &lt;EvanDotPro&gt; okay, so does anyone else want to add something to our plates for the beta1 / ZendCon release? speak now or forever hold your peace!
Oct 12 17:13:38 &lt;intiilapa&gt; EvanDotPro: lol
Oct 12 17:13:55 &lt;AndrejAndb&gt; now Zend\navigation work with \mvc\router? or its in plan? i dont know...
Oct 12 17:14:18 &lt;PadraicB&gt; weierophinney, nothing major - looks like a good start
Oct 12 17:14:20 &lt;weierophinney&gt; AndrejAndb, it doesn't for now. That will need to come at a later date.
Oct 12 17:14:23 &lt;weierophinney&gt; cool
Oct 12 17:14:41 &lt;weierophinney&gt; EvanDotPro, jurians suggested that we switch the order of the next two items on the agenda
Oct 12 17:14:44 &lt;PadraicB&gt; Unless you have free weeks with nothing to do, I'd go with what you have ;)
Oct 12 17:14:49 &lt;intiilapa&gt; router is not included in beta1?
Oct 12 17:14:51 &lt;weierophinney&gt; PadraicB, LOL
Oct 12 17:14:57 &lt;weierophinney&gt; intiilapa, the mvc router *is*
Oct 12 17:15:04 &lt;weierophinney&gt; intiilapa, the question is whether navigation works with it
Oct 12 17:15:12 &lt;weierophinney&gt; (i.e. the navigation component)
Oct 12 17:15:15 &lt;EvanDotPro&gt; is anyone against switching the order of the next to topics? milestones first, then server classes.
Oct 12 17:15:27 &lt;intiilapa&gt; EvanDotPro: no
Oct 12 17:15:57 &lt;EvanDotPro&gt; alright then, we're moving on to "Next milestones" now. :)
Oct 12 17:16:25 &lt;intiilapa&gt; EvanDotPro: are you moderator today?
Oct 12 17:16:38 &lt;jurians&gt; intiilapa: yes
Oct 12 17:16:53 &lt;EvanDotPro&gt; So the question is: where should we focus our efforts for the next couple of beta releases?
Oct 12 17:17:14 &lt;weierophinney&gt; intiilapa, this is your cue, as I know you have some opinions on this. :)
Oct 12 17:17:35 &lt;EvanDotPro&gt; candidates on the agenda are: Server class refactoring, Cache refactor completion, Console tools, Instance Creation by DI with static methods
Oct 12 17:17:41 &lt;intiilapa&gt; cue?
Oct 12 17:17:55 &lt;EvanDotPro&gt; that last item will likely be addressed today, so i'll scratch that off.
Oct 12 17:18:00 &lt;weierophinney&gt; intiilapa, as in: nudge, nudge, start speaking up...
Oct 12 17:18:15 &lt;jurians&gt; I'd say the first next milestone cover the components which will be used the most
Oct 12 17:18:20 &lt;intiilapa&gt; weierophinney: how weeks before beta2? commercial date needed or not?
Oct 12 17:18:33 &lt;weierophinney&gt; intiilapa, no commercial date, but I'd like to keep them coming relatively quickly.
Oct 12 17:18:34 &lt;intiilapa&gt; jurians: Db missing for me in this case
Oct 12 17:18:43 &lt;weierophinney&gt; The less time between them, the more focussed we'll be.
Oct 12 17:18:43 &lt;NickBelhomme&gt; we are using SOAP a lot!
Oct 12 17:18:49 &lt;mattcockayne&gt; I'm all for the CLI getting getting put in place
Oct 12 17:18:56 &lt;jurians&gt; so rather cache/log/db/etc than eg server classes (no offence matthew)!
Oct 12 17:18:59 &lt;intiilapa&gt; weierophinney: how many weeks by beta release?
Oct 12 17:19:13 &lt;weierophinney&gt; intiilapa, good question
Oct 12 17:19:19 &lt;weierophinney&gt; What do folks here think? six weeks?
Oct 12 17:19:21 &lt;weierophinney&gt; 4 weeks?
Oct 12 17:19:25 &lt;weierophinney&gt; 8 weeks?
Oct 12 17:19:26 &lt;weierophinney&gt; Thoughts?
Oct 12 17:19:26 &lt;EvanDotPro&gt; mattcockayne has expressed interest in starting work on the cli tool (module installation, etc)
Oct 12 17:19:54 &lt;weierophinney&gt; We can also tackle multiple items in a given beta, but we need to make sure efforts can be done in parallel
Oct 12 17:19:54 &lt;EvanDotPro&gt; the question is how many weeks between beta releases?
Oct 12 17:19:57 &lt;intiilapa&gt; 4 weeks are too less for contributors I guess
Oct 12 17:20:09 &lt;jurians&gt; intiilapa +1 but 8 sounds too much
Oct 12 17:20:20 &lt;weierophinney&gt; jurians, sounds like 6 weeks is a winner?
Oct 12 17:20:20 &lt;intiilapa&gt; 6?
Oct 12 17:20:20 &lt;PadraicB&gt; 6 weeks seems reasonable. 4 might be too little to expect drastic developments but it depends on progress - does it need to be fixed?
Oct 12 17:20:21 &lt;mattcockayne&gt; 6 weeks tends to be a common cycle time for releases... however thats generally for dedicated teams
Oct 12 17:20:25 &lt;jurians&gt; so 6 sounds actually pretty good
Oct 12 17:20:28 &lt;NickBelhomme&gt; if we are planning multiple betas than 8 weeks is too long
Oct 12 17:20:33 &lt;NickBelhomme&gt; 8 weeks = 2 months
Oct 12 17:20:49 &lt;weierophinney&gt; PadraicB, I don't think it needs to be fixed, but having a good target is good.
Oct 12 17:20:54 &lt;intiilapa&gt; PadraicB: no need, but for the timeline can help to know an average
Oct 12 17:20:55 &lt;EvanDotPro&gt; PadraicB +1, is there a reason for fixing it, other than getting folks to check back regularly?
Oct 12 17:20:58 &lt;weierophinney&gt; NickBelhomme, yes, many betas. :)
Oct 12 17:21:11 &lt;weierophinney&gt; EvanDotPro, two things for having a date:
Oct 12 17:21:14 &lt;intiilapa&gt; if we have 4 new components in 4 weeks with doc = go for the next release
Oct 12 17:21:27 &lt;weierophinney&gt; 1) it gives folks an idea of when they may next be testing new features
Oct 12 17:21:28 &lt;NickBelhomme&gt; then no fix release cycle but small increments
Oct 12 17:21:44 &lt;NickBelhomme&gt; release beta when something is considred done
Oct 12 17:21:47 &lt;PadraicB&gt; weierophinney, I'd use a range of 4-6. But fixed dates are easier to predict, publicise which aren't bad things.
Oct 12 17:21:48 &lt;weierophinney&gt; 2) it gives a "sense of urgency" to contributors -- get it in by this date, or it's dropped until next release.
Oct 12 17:21:49 &lt;NickBelhomme&gt; and not have multiple requirements per beta
Oct 12 17:22:10 &lt;intiilapa&gt; PadraicB: for me, we need to see components as a pyramid with dependency (sample: you refactor navigation after mvc router)
Oct 12 17:22:33 &lt;jurians&gt; weierophinney +1 two very important things for me
Oct 12 17:22:35 &lt;EvanDotPro&gt; how about only a fixed maximum interval, so the longest we can push off a beta release would be 6 weeks, but if we're ready for a release before week 6, that's okay too.
Oct 12 17:22:47 &lt;mattcockayne&gt; sounds sensible
Oct 12 17:23:05 &lt;weierophinney&gt; EvanDotPro, +1
Oct 12 17:23:09 &lt;jurians&gt; EvanDotPro: then a todo list should be there, otherwise you miss the beta where you worked silently on your own
Oct 12 17:23:22 &lt;weierophinney&gt; So, if we can agree on that, we should determine what the next milestone _should_ include.
Oct 12 17:24:13 &lt;NickBelhomme&gt; all applications use cache... so that is important
Oct 12 17:24:14 &lt;intiilapa&gt; cache and locale can have a lot of dependencies
Oct 12 17:24:24 &lt;intiilapa&gt; NickBelhomme: agreed
Oct 12 17:24:33 &lt;PadraicB&gt; On the milestones, has anyone had a stab at listing them loosely? I think we're missing even longer term goals. Thanks to many people here, we can start releasing Modules from our obsessive brains ;).
Oct 12 17:24:47 &lt;weierophinney&gt; :D
Oct 12 17:24:55 &lt;cballou&gt; I'm in agreement on cache.. my bootstrap tends to be litered with cache strategies for production
Oct 12 17:24:59 &lt;intiilapa&gt; Mail is important too, but Dolf is not available at this time
Oct 12 17:25:30 &lt;weierophinney&gt; intiilapa, the basic mail portion -- sending mail -- I could likely refactor in a day or two. The harder part is the mail\reader subcomponent.
Oct 12 17:25:35 &lt;PadraicB&gt; Mainly, I'm concerned about cache (though not too much - it basically is beta state right now), Locale, Translate (the TW stuff)
Oct 12 17:25:41 &lt;weierophinney&gt; that was done by some folks in the mail hosting business.
Oct 12 17:25:47 &lt;mattcockayne&gt; It may be worth considering scheduling 2 or three milestones ahead to allow for some longer running tasks that may need more than 6 weeks for a deliverable
Oct 12 17:25:56 &lt;weierophinney&gt; mattcockayne, agreed.
Oct 12 17:26:05 &lt;intiilapa&gt; PadraicB: we need to fix right now (CS, common pretty API, etc)
Oct 12 17:26:11 &lt;intiilapa&gt; and debug tests
Oct 12 17:26:22 &lt;intiilapa&gt; it's a lot of works to refactor before the final release
Oct 12 17:26:44 &lt;PadraicB&gt; mattcockayne, yes - just feeling out who is willing to do a loose timeline so we have something to debate (and not be empty handed in another two weeks)
Oct 12 17:26:48 &lt;intiilapa&gt; maybe some benchmarks to valid closures are better than foreach or other iterations
Oct 12 17:26:49 &lt;weierophinney&gt; intiilapa, we can do a lot of that _as_ we work on components
Oct 12 17:27:06 &lt;EvanDotPro&gt; What about setting up a longer-term milestone for refactoring components to the new options RFC?
Oct 12 17:27:15 &lt;weierophinney&gt; EvanDotPro, +1
Oct 12 17:27:20 &lt;ralphschindler&gt; +1
Oct 12 17:27:28 &lt;intiilapa&gt; +1
Oct 12 17:27:32 &lt;mattcockayne&gt; +1
Oct 12 17:27:46 &lt;EvanDotPro&gt; i'd say the +1's have it.
Oct 12 17:27:53 &lt;PadraicB&gt; EvanDotPro, sure - it's a longer term goal everyone needs to pitch into for their components
Oct 12 17:27:55 &lt;weierophinney&gt; re: more specific component-based milestones, I'm seeing:
Oct 12 17:27:57 &lt;weierophinney&gt; * Cache
Oct 12 17:28:03 &lt;weierophinney&gt; * Locale/Translator
Oct 12 17:28:13 &lt;weierophinney&gt; * Log
Oct 12 17:28:16 &lt;weierophinney&gt; * Mail
Oct 12 17:28:20 &lt;weierophinney&gt; * Servers
Oct 12 17:28:31 &lt;jurians&gt; db?
Oct 12 17:28:38 &lt;PadraicB&gt; ACL/Auth?
Oct 12 17:28:40 &lt;weierophinney&gt; jurians, I was talking short term
Oct 12 17:28:46 &lt;jurians&gt; kk
Oct 12 17:28:48 &lt;weierophinney&gt; PadraicB, what needs to happen on ACL/Auth?
Oct 12 17:29:00 &lt;intiilapa&gt; I think we need to know a global timeline for locale/translator if Thomas works alone for all components on this area (and he must included event and performance)
Oct 12 17:29:19 &lt;PadraicB&gt; No idea, if it's stable then it can be taken out
Oct 12 17:29:21 &lt;intiilapa&gt; PadraicB: ralph have a plan for access control :)
Oct 12 17:29:25 &lt;weierophinney&gt; intiilapa, do you want to discuss with him, and get him to post to the ML his plans/timeline?
Oct 12 17:29:45 &lt;PadraicB&gt; Man with a Plan ;).
Oct 12 17:29:51 &lt;weierophinney&gt; PadraicB, I've got both working in my sandbox right now. They're pretty much standalone and "just work" right now.
Oct 12 17:30:03 &lt;intiilapa&gt; I can try
Oct 12 17:30:22 &lt;intiilapa&gt; but it may be sensitive lol
Oct 12 17:30:45 &lt;weierophinney&gt; intiilapa, it always is. :)
Oct 12 17:30:47 &lt;intiilapa&gt; I don't know how estimate performance for locale
Oct 12 17:31:16 &lt;intiilapa&gt; Some complained that Thomas does not respond on his mail, and github to their questions.
Oct 12 17:31:24 &lt;weierophinney&gt; One thing I didn't put up ther, but I'm wanting to do, is to move the de/serialization aspects of the various server protocols into Zend\Serializer.
Oct 12 17:31:30 &lt;weierophinney&gt; that could be a short term goal.
Oct 12 17:31:41 &lt;PadraicB&gt; intiilapa, mainly it's the date stuff...since it couldn't leverage DateTime in ZF1.
Oct 12 17:31:41 &lt;weierophinney&gt; intiilapa, that's been... a common pattern, tbh.
Oct 12 17:32:24 &lt;weierophinney&gt; PadraicB, it's more than that. Locale/Translator are basically relying on Registry to get into objects currently, and auto-injecting themselves into it.
Oct 12 17:32:29 &lt;weierophinney&gt; a lot of stuff has to change.
Oct 12 17:32:40 &lt;intiilapa&gt; kill Registry :p
Oct 12 17:32:41 &lt;weierophinney&gt; I don't know what all he's addressing with his refactoring.
Oct 12 17:32:41 &lt;intiilapa&gt; :D
Oct 12 17:33:00 &lt;weierophinney&gt; intiilapa, we use registry in the placeholders as well, in zend_view -- but a local instance, not global.
Oct 12 17:33:02 &lt;intiilapa&gt; weierophinney: maybe included event, injection in CS
Oct 12 17:33:04 &lt;weierophinney&gt; it's still useful.
Oct 12 17:33:22 &lt;weierophinney&gt; intiilapa, yes -- but we need to ensure that the components are architected in such a way as to allow that.
Oct 12 17:33:23 &lt;EvanDotPro&gt; (on a side note, it might be worth advocating more frequent commits + pushes to github among contributors)
Oct 12 17:33:29 &lt;intiilapa&gt; weierophinney: yes, I know but for Locale component between bootstrap and validators or filtors or any component
Oct 12 17:33:48 &lt;weierophinney&gt; Let's back up, though...
Oct 12 17:34:00 &lt;weierophinney&gt; one more thing on htat list: console tools
Oct 12 17:34:13 &lt;intiilapa&gt; migrate all components in console namespace
Oct 12 17:34:16 &lt;weierophinney&gt; so, with that list, what should we tackle for the upcoming beta2 following beta1?
Oct 12 17:34:23 &lt;intiilapa&gt; weierophinney: when we look at ZendX into ZF2?
Oct 12 17:34:29 &lt;weierophinney&gt; intiilapa, any time.
Oct 12 17:34:45 &lt;weierophinney&gt; the only one I'm not certain about is jQuery, but we could still move it in now and address it later.
Oct 12 17:35:01 &lt;EvanDotPro&gt; so far i have this on the overall topic of milestones: http://pastie.org/2684202
Oct 12 17:35:11 &lt;intiilapa&gt; someone create a tool to know if a patch in ZF1 is forward port in ZF2
Oct 12 17:35:18 &lt;intiilapa&gt; as we talk about ZF1 port
Oct 12 17:35:37 &lt;intiilapa&gt; ACL need refactor or work
Oct 12 17:35:46 &lt;weierophinney&gt; PadraicB, oh, btw: I refactored the HTTP adapter of Zend\Authentication last week to work with the new HTTP objects -- works flawlessly right now.
Oct 12 17:35:48 &lt;jurians&gt; I'd say cache/log/mail for beta2 and locale/translator if possible
Oct 12 17:35:53 &lt;ralphschindler&gt; plan for access control?
Oct 12 17:36:06 &lt;PadraicB&gt; weierophinney ;)
Oct 12 17:36:09 &lt;weierophinney&gt; jurians, +1
Oct 12 17:36:19 &lt;PadraicB&gt; jurians +1
Oct 12 17:36:19 &lt;ralphschindler&gt; intiilapa: i think the idea was to go more of an RABC route
Oct 12 17:36:36 &lt;PadraicB&gt; Get some more basics out of the way.
Oct 12 17:36:41 &lt;intiilapa&gt; first time yes, but after Dolf say no about RABC
Oct 12 17:36:48 &lt;weierophinney&gt; ralphschindler, you mean RBAC? isn't that what it does already?
Oct 12 17:36:52 &lt;weierophinney&gt; anyways, off-topic. :)
Oct 12 17:37:02 &lt;weierophinney&gt; does cache/log/mail for beta2 make sense to all?
Oct 12 17:37:07 &lt;ralphschindler&gt; yep, and ok
Oct 12 17:37:14 &lt;weierophinney&gt; can somebody talk with marcmabe to see where he is with cache?
Oct 12 17:37:16 &lt;intiilapa&gt; jurians: translator is started (I know that tmx adapter tests is broken)
Oct 12 17:37:27 &lt;intiilapa&gt; just need some update like events, adapter interface
Oct 12 17:37:39 &lt;intiilapa&gt; and maybe Matthew look the code for ZF2 style and performance
Oct 12 17:37:39 &lt;jurians&gt; we then can push server/acl/auth and db(?) to beta3
Oct 12 17:37:42 &lt;PadraicB&gt; weierophinney, contingent on available of those doing those areas...yes
Oct 12 17:37:45 &lt;jurians&gt; intiilapa kk
Oct 12 17:38:00 &lt;PadraicB&gt; weierophinney, I can check in with him?
Oct 12 17:38:05 &lt;weierophinney&gt; PadraicB, that would be great.
Oct 12 17:38:08 &lt;mattcockayne&gt; suggest CLI for beta 3 also
Oct 12 17:38:14 &lt;jurians&gt; mattcockayne +1
Oct 12 17:38:29 &lt;PadraicB&gt; I've reviewed most of Zend\Cache - it would need very little to get into beta
Oct 12 17:38:36 &lt;weierophinney&gt; markizano, I know robertbasic is working on a module for it now. It may be ready before then, but if not, beta3 makes sense.
Oct 12 17:38:41 &lt;weierophinney&gt; PadraicB, awesome
Oct 12 17:38:43 &lt;intiilapa&gt; ralphschindler: do you know when Db can be available?
Oct 12 17:38:58 &lt;weierophinney&gt; intiilapa, when I let him work on it. :)
Oct 12 17:39:01 &lt;ralphschindler&gt; next big push
Oct 12 17:39:04 &lt;EvanDotPro&gt; i'd like to suggest possibly sneaking in cli + module distribution by beta 3.
Oct 12 17:39:04 &lt;jurians&gt; lol
Oct 12 17:39:09 &lt;intiilapa&gt; someone need to view with doctrine guyes, they want to start the bridge
Oct 12 17:39:13 &lt;weierophinney&gt; intiilapa, we got a lot of architecture done in June, but nothing since.
Oct 12 17:39:18 &lt;intiilapa&gt; weierophinney: looooooool :p
Oct 12 17:39:22 &lt;jurians&gt; EvanDotPro: what's included in "distribution"
Oct 12 17:40:01 &lt;intiilapa&gt; EvanDotPro: maybe write a map of contact/worker for some components (cache, locale, doctrine bridge, etc)
Oct 12 17:40:10 &lt;intiilapa&gt; weierophinney: nice
Oct 12 17:40:22 &lt;intiilapa&gt; EvanDotPro: yes cli can be great :)
Oct 12 17:40:36 &lt;EvanDotPro&gt; jurians: possibly getting pyrus in place, basic code to package modules for pyrus via the Module class, cli tool with ability to install via http, git, pyrus, local. (not all of that for beta3, but i'm advocating on a start with primitive funcationality, we can't put it off forever)
Oct 12 17:40:52 &lt;PadraicB&gt; intiilapa, do you have a list of those interested in Doctrine bridge? If they could throw up an RFC in time for next meeting it would get things moving and let us add it somewhere as a milestone task?
Oct 12 17:41:08 &lt;weierophinney&gt; EvanDotPro, a lot of the infrastructure for that will be done with beta1 -- just need to apply it to modules.
Oct 12 17:41:16 &lt;intiilapa&gt; PadraicB: yes, I can
Oct 12 17:41:31 &lt;weierophinney&gt; PadraicB, honestly, surprised guilherme is not here -- he said he would be.
Oct 12 17:41:43 &lt;PadraicB&gt; Best laid plans... ;)
Oct 12 17:42:01 &lt;intiilapa&gt; PadraicB: guilhermeblanco at first
Oct 12 17:42:02 &lt;weierophinney&gt; So, it sounds like we have a good idea of items for the next two betas at this point.
Oct 12 17:42:11 &lt;PadraicB&gt; It does.
Oct 12 17:42:14 &lt;weierophinney&gt; should we move on?
Oct 12 17:42:14 &lt;EvanDotPro&gt; weierophinney: thoughts on trying to get the functionaity somewhat working with modules for beta1? i'll have some hours to put towards that, but may need some help with the pyrus part.
Oct 12 17:42:25 &lt;weierophinney&gt; EvanDotPro, work with ralphschindler on it. :)
Oct 12 17:42:29 &lt;weierophinney&gt; if you can, great. :)
Oct 12 17:42:32 &lt;EvanDotPro&gt; will do.
Oct 12 17:42:38 &lt;weierophinney&gt; but we'd need it in the docs by Friday morning latest.
Oct 12 17:42:44 &lt;EvanDotPro&gt; mattcockayne: take note of that, i'd like your help on that if possible.
Oct 12 17:42:49 &lt;intiilapa&gt; PadraicB: and maybe Juozas
Oct 12 17:42:56 &lt;intiilapa&gt; (doctrine core team too)
Oct 12 17:42:56 &lt;PadraicB&gt; Any chance we could get the basic milestone list/possibility onto the ML for discussion? See if we can work out a proper timeline for the betas
Oct 12 17:43:16 &lt;jurians&gt; so recap: cache/log/mail => beta2, server/acl/auth/cli => beta3. Others (locale/translate and module-distribution) optional
Oct 12 17:43:20 &lt;intiilapa&gt; PadraicB: guilhermeblanco should write an RFC in 2/3 weeks
Oct 12 17:43:28 &lt;weierophinney&gt; PadraicB, sure, I'll do that as I summarize the meeting today.
Oct 12 17:43:29 &lt;PadraicB&gt; intiilapa, excellent!
Oct 12 17:43:31 &lt;jurians&gt; Is that reasonanle?
Oct 12 17:43:37 &lt;intiilapa&gt; jurians: why servers are not in beta2 now?
Oct 12 17:43:37 &lt;mattcockayne&gt; EvanDotPro: count me in
Oct 12 17:43:45 &lt;jurians&gt; s/reasonanle/reasonable
Oct 12 17:43:56 &lt;intiilapa&gt; weierophinney and EvanDotPro are busy? :D
Oct 12 17:43:59 &lt;weierophinney&gt; intiilapa, we may work on them during beta2, but focus is on the other components.
Oct 12 17:44:06 &lt;intiilapa&gt; ok
Oct 12 17:44:07 &lt;weierophinney&gt; Only so many people with so many hours...
Oct 12 17:44:17 &lt;intiilapa&gt; ^^
Oct 12 17:44:32 &lt;weierophinney&gt; unless you're volunteering, that is. :-)
Oct 12 17:45:02 &lt;intiilapa&gt; weierophinney: can we have an order/priority of components in scope of ZF Team?
Oct 12 17:45:32 &lt;weierophinney&gt; intiilapa, our priority from this point forward will be determined in these meetings.
Oct 12 17:45:39 &lt;EvanDotPro&gt; okay, i think milestones are pretty well covered at this point... so let's move on to the next topic now which is Matthew's server class RFC.
Oct 12 17:45:44 &lt;intiilapa&gt; ok
Oct 12 17:45:49 &lt;EvanDotPro&gt; RFC can be found at http://framework.zend.com/wiki/display/ZFDEV2/RFC+-+Server+Classes
Oct 12 17:46:11 &lt;intiilapa&gt; EvanDotPro: ideas in RFC are good :)
Oct 12 17:46:14 &lt;weierophinney&gt; I've got good feedback from wilmoore
Oct 12 17:46:23 &lt;weierophinney&gt; and good questions from jurians
Oct 12 17:46:42 &lt;weierophinney&gt; I know jurians and NickBelhomme are interested in this bit -- any comments/questions/feedback from you folks?
Oct 12 17:47:01 &lt;EvanDotPro&gt; i've read over it a couple of times and couldn't find anything to nit-pick at, personally.
Oct 12 17:47:33 &lt;jurians&gt; weierophinney: mmz, not really atm actually
Oct 12 17:47:34 &lt;PadraicB&gt; same here, nothing to add ;)
Oct 12 17:47:44 &lt;NickBelhomme&gt; same here
Oct 12 17:47:46 &lt;weierophinney&gt; It's not terribly different from before. The main changes are surrounding how the services are defined and attached to the server.
Oct 12 17:47:56 &lt;intiilapa&gt; weierophinney: ServerCompiler are related to Di?
Oct 12 17:48:07 &lt;weierophinney&gt; Old system was reflection-heavy, and didnt' allow for customizing which methods should/shouldn't be exposed.
Oct 12 17:48:12 &lt;intiilapa&gt; ServiceCompiler*
Oct 12 17:48:22 &lt;intiilapa&gt; weierophinney: +1
Oct 12 17:48:35 &lt;weierophinney&gt; intiilapa, no, it's related to Zend\Code -- it would scan services to create Service defintions.
Oct 12 17:49:04 &lt;jurians&gt; I assume configurations can be created at runtime?
Oct 12 17:49:17 &lt;markizano&gt; <weierophinney> markizano, I know robertbasic is working on a module for it now. It may be ready before then, but if not, beta3 makes sense. <- Was this meant for me? lol
Oct 12 17:49:21 &lt;intiilapa&gt; weierophinney: WsdlGenerator is not in the area of RFC?
Oct 12 17:49:23 &lt;EvanDotPro&gt; so is it safe to say we can mark that RFC as generally accepted and safe to begin work on? work may not start for a couple/few weeks after zendcon, so there will be time for more feedback.
Oct 12 17:49:24 &lt;weierophinney&gt; jurians, yes -- there'd be a version that could use Reflection to generate the services
Oct 12 17:49:37 &lt;weierophinney&gt; markizano, no, meant for mattcockayne
Oct 12 17:49:41 &lt;weierophinney&gt; bad tab completion
Oct 12 17:49:48 &lt;markizano&gt; It's all gravy :)
Oct 12 17:49:51 &lt;intiilapa&gt; EvanDotPro: yeah
Oct 12 17:49:56 &lt;weierophinney&gt; intiilapa, WsdlGenerator would consume ServiceAggregates
Oct 12 17:50:05 &lt;jurians&gt; cool, tab completion, just finding out (omg)
Oct 12 17:50:24 &lt;jurians&gt; weierophinney: same holds for manually => config?
Oct 12 17:51:14 &lt;weierophinney&gt; jurians, yes -- basically, you could do any combination of strategies -- manually creating the service defintions, using reflection to generate them, or using a compiler (which would use the code scanner, likely) to pre-compile them.
Oct 12 17:51:25 &lt;weierophinney&gt; along with configuration, of course.
Oct 12 17:51:48 &lt;weierophinney&gt; jurians, similar in lines to DI definitions, really.
Oct 12 17:52:03 &lt;PadraicB&gt; bbiaf
Oct 12 17:52:03 &lt;jurians&gt; kk
Oct 12 17:53:34 &lt;EvanDotPro&gt; okay, so that about sums up the meeting... i'll open the floor to for 7 minutes.
</pre>
]]></ac:plain-text-body></ac:macro>