emberjs / core-notes Goto Github PK

• Move tomdale/glimmer-website to glimmerjs org [@tomdale]
• Move tildeio/glimmer to glimmerjs/glimmer-vm [@chancancode]
• Make @glimmer/application depend on @glimmer/component [@tomdale]
• Sync Github/NPM permissions for core team members [@locks]
• Stop publishing glimmer-engine on NPM [@tomdale]
• Send Doodle for meeting times [@chancancode]
• Propose replacing core team slack with Discord as a trial in next core team meeting [@wycats]
• "Fix nulls" (?) [@tomdale]
• File arguments.length issue against TypeScript [@krisselden]
• Investigate issue with using web components with non-ES6 classes [@wycats]
• Review glimmerjs/glimmer-application#40 [@tomdale]
• Add browser support policy to website [@tomdale]
• Add back expect() to vm [@chadhietala]
• Use babel 6 in tests [@rwjblue]
• Fix type errors [@chancancode/@wycats]
• Extract @glimmer/utils into top-level packages, move Opaque there [@wycats]
• Fix glimmerjs/* builds [@rwjblue]
• Add dev/prod mode to glimmerjs/* [@rwjblue / @dgeb]
• Start glimmerjs/glimmer-stdlib [@chancancode]
• "peer dependencies" [@rwjblue]
• Implement emberjs/rfcs#213 [@chancancode]
• Refactor getComponentDefinition in emberjs/ember.js [@tomdale]
• Change WC wrapper to generate <$APP_NAME-app /> as the entry point (unless $APP_NAME already contain an "app" suffix?) to avoid collision with private collections [@tomdale]
• Finish stack branch [@chancancode / @wycats]
• Integrate stack branch into Ember [@chancancode / @wycats]
• Confirm complex-lists benchmark regression [@chadhietala]
• Implement capabilities mask [@chancancode / @wycats]
• Fix loc [@rwjblue]
• Strip partials from glimmerjs [@tomdale]
• Strip IE support from glimmerjs [@tomdale]

Hello,
I'm a big supporter of this wonderful project (I think emberjs rocks web development) but I'm quite disappointed in seeing highly political and divisive statements on the top line of the main page on https://emberjs.com/.

As Tabarrok wrote in his good "small steps toward a better world" the ember community should focus on its aim and avoid topics that has nothing to do with the project and that only creates division and animosity between people with no other advantages.

You should adopt the Mission Protocol and change you documentation as explained in the code of conduct for a safer and more inclusive experience.

I opened an issue here because I could not find a better "meta" repository for this kind issue, feel free to direct me to better places, if any.

Review archived repos (locks, 10min)

We have a bunch of archived repos that, to me, do not offer any meaningful historic context and should be removed so contributors aren't overwhelmed when navigating the org.

• https://github.com/ember-learn/ember-issue-triage-chrome internal tool. one commit by me.
• https://github.com/ember-learn/ember-issue-triage-lambda internal tool. one commit by me.
• https://github.com/ember-learn/tomster-chatbot very basic slack chatbot. was broken before we even moved to Discord. most work by me.
• https://github.com/ember-learn/dashboard couple of commits by me. I don't think it ever got used.

ember-cli-addon-docs (locks, 10min)

Proposal to create an ember-cli-addon-docs org and move repos there.

Agenda:

Please edit or comment to add items to the agenda

I really enjoy reading these. I watch this repo so that I can get notifications when new notes are added. Today I saw that the two fastboot-team notes weren't added via PR and thus I didn't get notified. I don't think there is a way to get Github alerts for every commit.

If it's not too much trouble, would you guys mind adding all new note files via PR. Even if they're merged right away.

This is obviously a minor thing, but could the day values used in the naming convention always have two digits? This would help keep things in chronological order for those meetings that take place within the single-digit days of the month.

Ex:

february-11.md
february-19.md
february-4.md

Becomes:

february-04.md
february-11.md
february-19.md

Thanks for the consideration!

The learning team would like to automate the creation of the following week's agenda as a quality of life improvement.
This can be done as a GitHub action that is triggered once the current agenda is merged.
The action would create a new PR with the agenda in the correct place and the relevant date.

Howdy folks 👋

We have recently documented our process for getting the Learning team core-notes into this repo and today is the first time that I have come to add minutes (it's my turn) 🎉

I noticed that there is no learning-team folder and that our learning team minutes are instead in the docs-team folder. I don't fully understand the history of the learning team since I'm new, but I was under the impression that we very purposely don't call it a docs-team for various reasons that are probably spread over many videos on YouTube and blogs.

Is there any objection to renaming the folder from docs-team to learning-team?