# DoneJS Contributors Meeting – 2016-12-23

**URL:** <https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512>\
**Category:** DoneJS\
**Created:** [December 20, 2016, 1:41am UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512 "2016-12-20T01:41:11Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![chasen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/chasen/32/402_2.png) [@chasen](https://forums.bitovi.com/u/chasen)\
**Post date:** [December 20, 2016, 1:41am UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/1 "2016-12-20T01:41:11Z")

</div>

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

[Live Stream](https://www.youtube.com/watch?v=aXR7Gvy3AMI)

- [Bitcentive MVP](https://github.com/donejs/bitcentive/issues/96) - `99 / 133`
  - [Feathers + CanJS](https://github.com/donejs/bitcentive/issues/83) - `90 / 121`

- [DoneJS 1.0](https://github.com/donejs/donejs/issues/703) - `21 / 386`
  - [DoneJS 1.0 site](https://github.com/donejs/donejs/issues/706) - `9 / 133`

- [2016-12 Developer Relations & Evangelism](https://github.com/donejs/donejs/issues/752) - `150 / 189`

---

<div class="post-metadata">

**Author:** ![justinbmeyer](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/justinbmeyer/32/179_2.png) [@justinbmeyer](https://forums.bitovi.com/u/justinbmeyer)\
**Post date:** [December 20, 2016, 4:37pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/2 "2016-12-20T16:37:51Z")

</div>

Topics:

- Ember’s task implementation. [http://ember-concurrency.com/#/docs](http://ember-concurrency.com/#/docs)
- [define.keys](https://github.com/canjs/can-define/issues/126)
- [can-connect-map-merge](https://github.com/canjs/can-connect/issues/231)

Last Week:

- Bitovi stuff
- Fixed bug with `{{#each}}` and `DefineMap`
- Worked on topic proposals

Next Week:

- Hopefully DoneJS 1.0

---

<div class="post-metadata">

**Author:** ![matthewp](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/matthewp/32/77_2.png) [@matthewp](https://forums.bitovi.com/u/matthewp)\
**Post date:** [December 20, 2016, 6:36pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/3 "2016-12-20T18:36:19Z")

</div>

Last Week:

- Released StealJS 1.0

This Week:

- A few Steal patches (up to 1.0.5 now).
- StealJS 1.0 article is being worked on.

I’m on vacation on Friday so won’t be able to attend the meeting. Happy Holidays everyone!

---

<div class="post-metadata">

**Author:** ![phillipskevin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/phillipskevin/32/102_2.png) [@phillipskevin](https://forums.bitovi.com/u/phillipskevin)\
**Post date:** [December 20, 2016, 9:54pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/4 "2016-12-20T21:54:40Z")

</div>

Topic: Node Version Support for DoneJS 1.0

---

<div class="post-metadata">

**Author:** ![matthewp](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/matthewp/32/77_2.png) [@matthewp](https://forums.bitovi.com/u/matthewp)\
**Post date:** [December 20, 2016, 10:02pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/5 "2016-12-20T22:02:06Z")

</div>

I would be here on Friday, so in regards to @phillipskevin’s topic I think we should poll the community and clients to see versions they are using and how flexible they are about being able to upgrade.

---

<div class="post-metadata">

**Author:** ![chasen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/chasen/32/402_2.png) [@chasen](https://forums.bitovi.com/u/chasen)\
**Post date:** [December 23, 2016, 2:24pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/6 "2016-12-23T14:24:26Z")

</div>

Status last week:

- Published “How to Upgrade a DoneJS Plugin to CanJS 3”: [https://www.bitovi.com/blog/how-to-upgrade-a-donejs-plugin-to-canjs-3](https://www.bitovi.com/blog/how-to-upgrade-a-donejs-plugin-to-canjs-3)
- Hosted a training on the migration guide: [https://www.youtube.com/watch?v=Z7Z14rv-V6s](https://www.youtube.com/watch?v=Z7Z14rv-V6s)
- PRs:  
– [Improve the migration guide](https://github.com/canjs/canjs/pull/2908)  
– [Replace v3.canjs.com with just canjs.com](https://github.com/canjs/canjs/pull/2910)  
– [Fix a broken link on the Mission page](https://github.com/canjs/canjs/pull/2912)  
– [Improve the Migration Guide’s structure](https://github.com/canjs/canjs/pull/2921)  
– [Use a specific snapshot for all of our JS Bins](https://github.com/canjs/canjs/pull/2923)

Next week:

- [Review the Steal Migration Guide](https://github.com/stealjs/stealjs/issues/23)
- [Review the steal-conditional docs](https://github.com/stealjs/stealjs/issues/25)
- [CanJS Flow Super Issue](https://github.com/canjs/canjs/issues/2547)
- [Improve the home page](https://github.com/canjs/canjs/issues/2902)
- [Re(move) the API Guide page](https://github.com/canjs/canjs/issues/2863)
- [Make the can package vs. modules explanation more clear](https://github.com/canjs/canjs/issues/2882)
- [Add descriptions to the “Who Uses CanJS” page](https://github.com/canjs/canjs/issues/2880)

Topic: improve the CanJS home page: [https://github.com/canjs/canjs/issues/2902](https://github.com/canjs/canjs/issues/2902)

Specifically, I want to talk about [moving the “Collections” and “The can Package” sections](https://github.com/canjs/canjs/issues/2868) and going forward with some [design ideas from Tom](https://github.com/canjs/canjs/issues/2752#issuecomment-261007106). This is related to the [general flow](https://github.com/canjs/canjs/issues/2547) of the website.

---

<div class="post-metadata">

**Author:** ![phillipskevin](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/phillipskevin/32/102_2.png) [@phillipskevin](https://forums.bitovi.com/u/phillipskevin)\
**Post date:** [December 23, 2016, 3:43pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/7 "2016-12-23T15:43:57Z")

</div>

**Last Week:**

- CanJS 3.3.0 - last piece of moving “stateful” modules out of can-util
- DoneJS generators ~ready for 1.0
- Started releasing 1.0 alpha releases
- Hopefully will have SSR working soon
- [steal-typescript](https://www.npmjs.com/package/steal-typescript)

**Next Week:**

- Vacation

---

<div class="post-metadata">

**Author:** ![Macrofig](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/macrofig/32/24_2.png) [@Macrofig](https://forums.bitovi.com/u/Macrofig)\
**Post date:** [December 23, 2016, 3:44pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/8 "2016-12-23T15:44:02Z")

</div>

Hey everyone,

I’ve been working on can-validate recently. Specifically, a refactor based on [this proposal](https://github.com/canjs/can-validate/issues/42).

I’d like to discuss a couple things:

- can-validate-legacy (3.0 compatible version of what can-validate is _now_)
- can-validate suite

The plan is to break out can-validate into parts, following the pattern we’re using with other 3.0 projects. Those parts would consist of…

- DefineMap plugin
- Our own validation library
- ValidateJS library plugin

This might be a lot to talk about so, if we need to focus on one topic, I think how we are handling the different “versions” was a hot topic last time.

---

<div class="post-metadata">

**Author:** ![chasen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.bitovi.com/chasen/32/402_2.png) [@chasen](https://forums.bitovi.com/u/chasen)\
**Post date:** [December 23, 2016, 7:41pm UTC](https://forums.bitovi.com/t/donejs-contributors-meeting-2016-12-23/512/9 "2016-12-23T19:41:33Z")

</div>

Rough meeting notes:

**Attendees:** @chasen @cherif_b @justinbmeyer @Macrofig @phillipskevin

**Discussed topics:**

[ember-concurrency](http://ember-concurrency.com/#/docs):

- Would be cool to have something like this for CanJS

[define.keys](https://github.com/canjs/can-define/issues/126):

- General consensus: 👍
- Discussed whether we should have this functionality in the module or in something like `can-util/operators/`
- Long term goal: match the JS APIs as much as possible and take advantage of things like Symbol

[can-connect-map-merge](https://github.com/canjs/can-connect/issues/231):

- General consensus: 👍

[can-validate](https://github.com/canjs/can-validate/issues/42):

- `can-validate-legacy`: currently a pre-release; docs should be available soon
- `can-validate`: break it up into smaller modules
- Proposal options  
– option 1: more explicit APIs you have to learn about  
– option 2: simplified APIs; lose flexibility of different validators, but that doesn’t seem like a worthwhile goal
- It’d be great to make this module usable with the decorators syntax
- We need to expose more of the DefineMap internals for can-define-stream and can-define-validate  
– Need to figure out hooks that could be used for both of them

DoneJS 1.0 supported Node.js versions:

- We’ll poll the community to see which versions are being used
- Idea: support the same versions that are maintained by the Node.js community  
– [Node.js LTS schedule](https://github.com/nodejs/LTS#lts-schedule)
- Node.js v4 should be easy to support; only missing out on ES6 features

[canjs.com](http://canjs.com) homepage design changes:

- Idea: [Move the “Collections” and “The can Package” sections off the home page](https://github.com/canjs/canjs/issues/2868)
- Central issue: whether the website should target new or existing issues
- We want new users to go to the guides
- Idea: the home page should direct different users to their destinations
- Idea: cheat sheet with a mini app to see the different parts/APIs  
– Kinda related to [Make the main components of a CanJS app more obvious](https://github.com/canjs/canjs/issues/2865)
- Idea: expand the info shown about each module (related to [https://github.com/canjs/canjs/issues/2871](https://github.com/canjs/canjs/issues/2871))
- Implement search: [https://github.com/canjs/bit-docs-html-canjs/issues/123](https://github.com/canjs/bit-docs-html-canjs/issues/123)
- Some consensus around creating an APIs page in the main navigation with all of the modules
