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

For Ember Times No. 96: Add Writeup for Milestones + Ember Paris Contributor Workshop #97

Merged
merged 8 commits into from
May 1, 2019

Conversation

jayjayjpg
Copy link
Contributor

What it does

Related Issue(s)

Sources

@jayjayjpg jayjayjpg requested a review from a team April 30, 2019 20:03
@jayjayjpg jayjayjpg changed the title For Ember Times No. 96: Add Writeup for Milestones For Ember Times No. 96: Add Writeup for Milestones + Ember Paris Contributor Workshop Apr 30, 2019
Copy link
Member

@amyrlam amyrlam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯 my bad for not reading this first! Made a couple suggestions.

Let's use this writeup and I'll close #98

@ijlee2
Copy link
Member

ijlee2 commented May 1, 2019

Awesome writing in both articles!

Copy link
Contributor

@MinThaMie MinThaMie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found some minor things, otherwise an awesome write-up :)

<add blurb and emoji to "SOME-INTRO-HERE">
Last week's **contributor workshop**, organised by the folks over at the [EmberJS Paris meetup](https://twitter.com/EmberJSParis), was a **real success**: with new changes to Ember CLI, improvements to Ember addons and even a brand-new RFC written, the Ember community gave back to the project, with some of the work even being made by first-time contributors! 🙌

Already feeling inspired to participate in or initiate your own **Ember contributor workshop**? Be sure to check out [these helpful resources to help you get you started](https://github.com/ember-learn/emberjs-contributors-workshop). And don't forget to check back on [#dev-ember-learning Discord channel](https://discordapp.com/invite/emberjs) and the [Ember Help Wanted app](https://help-wanted.emberjs.com/) to find something neat to work on. Codage heurex! 💻❤️
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove the help after the to, helpful resources in itself are meant to help :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I'll update that one 👍


Managing **concurrency in your app** can be hard (at least, until you start using [ember-concurrency](http://ember-concurrency.com) ✨). Managing **concurrency in your tests** can be even harder.
But **managing concurrent behaviour** in your **tests** can be even harder.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe make this the hardest or something other than can be even harder because you already use that before.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good 👍

@jayjayjpg
Copy link
Contributor Author

Thank you for the reviews @ijlee2 and @amyrlam, I updated the branch accordingly ✨

@jayjayjpg
Copy link
Contributor Author

Thank you for the review @MinThaMie, I updated the writeup accordingly ✨

Copy link
Contributor

@MinThaMie MinThaMie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome ✨

@jayjayjpg jayjayjpg merged commit 8ed0438 into ember-learn:blog/embertimes-96 May 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants