Core Team Meeting Minutes - 2014/01/31


Although most of our collaboration takes place on Github, IRC (#emberjs on freenode.net), and our Discourse site the Ember.js Core Team meets privately every Friday at 2pm EST/11am PST through Google Hangout for a weekly discussion of all things Ember.

If you have a topic you'd like to see covered, contact your favorite core team member and let them know!

Attendees

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

Go/No-Go Feature Listing

  • ember-routing-named-substates #3655 @krisselden: likes the feature a lot (we should “just doit”) @wycats: naming with globals is totally unsolvable. @machty: If FooLoading is ambiguous, we should just warn that global mode is not supported for this feature @tomdale: we need a separate task force for thinking about module mode only features.

    resolution: Tom and Stef will review

  • ember-handlebars-caps-lookup #3218

    resolution: check local first, warn and fallback to global seems like a good strategy

  • ember-testing-simple-setup #3785

    resolution: Tom and Stef will review

  • version api docs

    Often asked for. We should work with community, see if robert can own, and help delegate.

  • query-params-new #4008

    misleading bug reports, but eager loader of controllers was the original pain point that kept this a "No go"

  • composable-computed-properties #3696

    @wycats: aliased to short words in the examples, should be documented to match this? @ebryn:: new CP work may have issues, @wycats and @ebryn and David should talk.

    resolution: @ebryn will talk to David about blocking

  • ember-routing-auto-location #3725

    resolution: Alex will make sure docs are good, then this becomes a "Go"

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

    resolution: "Go" but we need an intermediate release issuing deprecation warnings, a future release will have break. This future release may contain some helpful warning, and the release notes will contain this info.

PR's/Issues To Review


comments powered by Disqus