DoneJS Contributors Meeting – 2016-12-02

DoneJS
1

Please add topics for discussion (and your status if you’re a contributor).

Live Stream

In Progress Epic Status:

2

Topic proposal: How to handle custom generators

3

Last Week:

  • Worked on bitcentive MVP
  • Some client work

Next Week:

  • Finish Bitventive MVP
4

Last Week:

  • CanJS 3.0 release article
  • CanJS tech highlights
  • New site goes out today
    Next Week:
  • Bitovi retreat planning so not much OS other than publishing 3.0 release article.
5

Last week:

  • Fixed can-fixture’s XHR to use getters/setters and not break socket.io
  • Fixed issue in can-view-live list.js so adding/removing items will happen in the correct order
  • Fixing issue in can-stache so foo[bar][baz] will work

Next week:

  • can-namespace
6

Last Week:

  • done-ssr 0.13.5 and 0.14.0-pre.2
  • WebPack and Browserify fixes
  • Working on plugins configuration (so close!)

Next Week:

  • Not sure.
7

Last week:

Next week:

Topic suggestion: how to require multiple versions of the same package

8

Last Week:

  • Finished documenting can-connect-feathers
  • Fixed a bug in can-connect-feathers that prevent query params from hitting the server on getList
  • Added feathers-authentication-popups message handling & validation to can-connect-feathers
  • New prerelease of can-connect-feathers
  • Fixed sorting bug in Bitcentive with ^^^
    Next week:
  • More Bitcentive
  • can-connect SSR support for Feathers
9

Rough meeting notes:

Attendees: @BigAB, @chasen, @ilyavf, @pYr0x, @justinbmeyer, @phillipskevin, @marshallswain, @matthewp, & @obaid

Discussed topics:

Directional shift with CanJS 3:

  • Previous misson: simple and efficient web framework for complex apps
  • New direction: handling the progressive march of technology enhancement
  • How do we make it so developers can deal with tech changes?
    – Make upgrading easier
    – Forward-compatibility: the code that you write will be valuable as possible over time
    – Open to experimentation: explore new ideas; enable mixin behavior; embrace decorators
  • First step: smaller, independent repositories
    – More isolation and packages
  • Question: what will 4.0 look like?
    – Answer: Justin will probably write a roadmap article
  • Concerns: people don’t like to upgrade, so they’ll rewrite instead; how long do apps stick around?
    – Upgrades have been hard, so if we make it easy then we’ll get more people to upgrade
    – Keep the current users happy! We want to continually increase our user base.
    – Some people don’t upgrade old code because of lack of test coverage
    – Opt to use native technologies from the browser; custom elements for components, etc.
    – Less of a need to completely rewrite if you follow best-practices

Topic: same dependency at different versions

  • Problem with the npm approach: duplicate loading of packages at different versions
    – Keep infrastructure modules very stable and as small as possible to combat that issue

Topic: custom generators

  • Solutions are not mutually exclusive
  • Solution 1a could use a templates.json file or read from the filesystem
  • Codemods are more complex but allow for greater flexibility/transforms