Minutes of the core team meeting-2014/01/31


-Passing

Trek to Glovac

Although most of our collaboration is conducted on Github, IRC (#emberjs On freenode.net), and our Discourse site
This Ember.js core team Meet in private via Google Hangout every Friday at 2pm Eastern Standard Time / 11am Pacific Standard Time to discuss everything about Ember every week.

If you have a topic you want to discuss, please contact your favorite core team member and let them know!

participant

@ebryn, @krisselden, @machty, @stefanpenner, @tomdale, @wifelette, @wycats

Pass/Fail function list

  • ember-routing-named-substates #3655

    @krisselden: I like this feature very much (we should do it) @wycats: Using global naming is completely unsolvable. @machty: If FooLoading is not clear, we should warn that this feature does not support global mode @tomdale: We need a separate working group to consider the module-only feature.

    Resolution: Tom and Stef will review

  • ember-handlebars-caps-lookup Chapter 3218

    Solution: Check the local first, warn and fall back to the global seems to be a good strategy

  • ember-testing-simple-setup #3785

    Resolution: Tom and Stef will review

  • version api docs

    Frequently asked. We should work with the community to see if robert can be owned and help commission.

  • query-params-new #4008

    Misleading error report, but the controller’s eager loader was the initial pain point, making it “not working”

  • composable-computed-properties Chapter 3696

    @wycats: The alias in the example is a short word, should it be recorded to match this content? @ebryn:: There may be problems with the new CP work, @wycats and @ebryn and David should talk about it.

    Solution: @ebryn will discuss blocking issues with David

  • ember-routing-auto-location Chapter 3725

    Solution: Alex will make sure the document is good, then this becomes “Go”

  • ember-routing-bound-action-name Chapter 3936

    Solution: “Go”, but we need an intermediate version that issues a deprecation warning, and there will be interruptions in future versions. This future version may contain some useful warnings, and the release notes will include this information.

PR/issues to review


Please enable JavaScript to view

Comments are powered by Disqus.


Leave a Reply

Your email address will not be published. Required fields are marked *