Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add June Learning Team agenda #306

Merged
merged 9 commits into from
Jun 10, 2020
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 76 additions & 0 deletions learning-team/2020-06/2020-06-04.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
# June 4, 2020

Facilitator & Note Taker:

## Attendees

Add yourself to the list if you attend and check the box!

### Core Team
- [ ] Chris Manson (CM)
- [ ] Amy Lam (AL)
- [ ] Ricard Mendes (RM)
- [ ] Jessica Jordan (JJ)
- [ ] Melanie Sumner (MS)
- [ ] Jen Weber (JW)
- [ ] Kenneth Larsen (KL)
- [ ] Robert Wagner (RW)
- [ ] Jared Galanis (JG)
- [ ] Isaac Lee (IL)

### Guests

## Weekly Agenda (20mins)

- [ ] Review action items (update weekly)
- [ ] Review [Initiatives Board](https://github.com/orgs/ember-learn/projects/33) (every second week)
- [ ] How is our PR queue doing? How many older than a week? [Tracking sheet](https://docs.google.com/spreadsheets/d/1sPyN9z9wZMpTNwqCfa6R9QSPZkIW4iQd-H4gZC7ILLk/edit#gid=2035777454)
- [ ] Review new RFCs/[RFC Tracking](https://github.com/emberjs/rfc-tracking)
- [ ] Any suggestions for the Ember Times? Add writeup ideas / call for contributors / suggestions to [the latest PR](https://github.com/ember-learn/ember-blog/pulls?q=is%3Aopen+is%3Apr+label%3A%22%F0%9F%97%9E+embertimes%22%20or%20#support-ember-times) or [#support-ember-times](https://discordapp.com/channels/480462759797063690/485450546887786506) on Discord.

## Topics

If you would like to add a topic to the agenda please add a suggestion to the PR using the following format:

```markdown
### Topic goes here (your initials - 00mins)

description of topic goes here
```

### replacing `ember-ref-modifier` (@chriskrycho - CK)

One of the advanced examples in the guides, [Communicating Between Elements in
a Component][example], uses `ember-ref-modifier` to show how to implement some
custom functionality. This example dates to a time before the existence of
`ember-modifier`, and was reasonable to include at the time. However, today the
example can be implemented much more cleanly using a class-based modifier from
`ember-modifier`. Just as importantly, using `ref` has significant performance
implications that are *not* obvious: it requires two rendering passes. I’ve had
to wave people off of using `ref` a couple times already in our app as we adopt
Octane, because it’s officially recommended in the Guides, which we point people
to as our *first* source of truth for how to write Octane. I suggest we remove
it in favor of another example using one of the `ember-modifier` variants.

[example]: https://guides.emberjs.com/release/components/template-lifecycle-dom-and-modifiers/#toc_communicating-between-elements-in-a-component
- Echoed by @rwjblue

- Alternate suggestion by @jrjohnson, CK has comments on this will mention at the meeting: https://github.com/emberjs/core-notes/pull/306#issuecomment-632801292
- Aside from @lifeart: https://github.com/emberjs/core-notes/pull/306#issuecomment-633190688

### Ember CLI API docs (from @mehulkar, who may or may not attend - 10mins)

I want to get an update on getting API docs on `https://api.emberjs.com/ember-cli`
and redirecting `ember-cli.com/api`. As embroider approaches and the larger
JS community experiments with JS development (e.g. Snowpack), it is
important for the Ember project to _enable_ its community to experiment also.
Moving the API docs to the main site will make it easier to improve
documentation, add examples, and propose API improvements that can
enable such experimentation.

<!-- replace with topic -->
amyrlam marked this conversation as resolved.
Show resolved Hide resolved
<!-- replace with topic -->
jenweber marked this conversation as resolved.
Show resolved Hide resolved
<!-- replace with topic -->

## Any Questions?
Questions, comments or concerns? Submit a comment or PR for this set of notes.