+
-In our 5th edition of the contributor interview series community member **Lisa Backer**, also known as [@eshtadc](https://github.com/eshtadc) talks about her work on `ember-service-worker`, public speaking, the things that make open-source so valuable and why anyone in the community can be an expert who has important insights to share.
+In our 6th edition of the contributor interview series community member **Lisa Backer**, also known as [@eshtadc](https://github.com/eshtadc) talks about her work on `ember-service-worker`, public speaking, the things that make open-source so valuable and why anyone in the community can be an expert who has important insights to share.
You can read the full interview on [the Ember Forum](https://discuss.emberjs.com/t/i-contribute-to-ember-with-lisa-backer/16168).
diff --git a/source/blog/2019-02-22-the-ember-times-issue-86.md b/source/blog/2019-02-22-the-ember-times-issue-86.md
new file mode 100644
index 0000000000..0471c5c36c
--- /dev/null
+++ b/source/blog/2019-02-22-the-ember-times-issue-86.md
@@ -0,0 +1,126 @@
+---
+title: The Ember Times - Issue No. 86
+author: Chris Ng, Gaurav Munjal, Amy Lam, Alon Bukai, Jessica Jordan, Jared Galanis
+tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2019
+alias : "blog/2019/02/22-the-ember-times-issue-86.html"
+responsive: true
+---
+
+สวัสดี Emberistas! 🐹
+
+Fill out the **2019 Ember Community Survey**! 📝 We have RFCs galore: two follow-up RFCs to make **Tracked Properties** better 👣, the full deprecation of **Partials** 🥛, the renaming of `htmlSafe` and the **deprecation of with** 🚫, and a **RFC Roundup Redux** episode of Ember Weekend 🔈 for you. This week we're also highlighting a wholesome **Ember community experience** 🤝, and last, but not least, an exclusive interview with Ember contributor **@cibernox**! 💬
+
+---
+
+## [2019 Ember Community Survey 📝](https://emberjs.com/blog/2019/02/19/ember-community-survey.html)
+
+The **official 2019 Ember Community Survey** is here! We would like your help to learn about who is in the Ember community and how they work with the framework.
+
+This is the fifth year we're learning about the community's makeup and interests, and we look forward to sharing the results at [EmberConf 2019](http://emberconf.com/) on March 18th. Over 1300 participants took part in the survey in 2018 ([2018 survey results](https://www.emberjs.com/ember-community-survey-2018/)) and we are aiming for even more participation this year!
+
+Completing the survey should take about **15 minutes**. We've added a few new questions this year, while retaining opportunities to share feedback as free-form text. All submissions are completely anonymous, and demographic data about the community is not released in the same raw data files as the free-form text and other answers.
+
+Submissions will be accepted **until March 12th**. More info about the survey can be found [here](https://emberjs.com/blog/2019/02/19/ember-community-survey.html). Why not fill it out now?!
+
+Take the Survey
+
+Please help us **spread the word** by sharing the [survey landing page](https://emberjs.com/ember-community-survey-2019) on your social network feeds, at meetups and around your office and other communities.
+
+We look forward to your participation! If you have any immediate questions, feel free to email the survey team via [survey@emberjs.com](mailto:survey@emberjs.com), or ping us in [#dev-ember-learning](https://discordapp.com/channels/480462759797063690/480777444203429888) in [Discord](https://discordapp.com/invite/zT3asNS) chat.
+
+---
+
+## [RFCs for Decorator Support and Tracked Property Classic Class Descriptor 👣](https://github.com/emberjs/rfcs/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+440+442)
+
+[@pzuraq](https://github.com/pzuraq) opened up a pair of RFCs that supplemented the recently merged [Tracked Properties RFC](https://github.com/emberjs/rfcs/pull/410).
+
+The **Decorator Support RFC** is a follow up to the [Decorators RFC](https://github.com/emberjs/rfcs/blob/master/text/0408-decorators.md) since it was premised on decorators moving from stage 2 in the TC39 process to stage 3. However since decorators remained in stage 2, and have not been rejected, and that all parties were in agreement about the *invocation syntax* of decorators – decorators should present a minimal amount of risk to Ember and its users. The changes in the spec will mostly affect library and framework maintainers, but not end users in *most cases*. Ember will begin by supporting the latest version of the decorators transform provided by Babel.
+
+The **Tracked Property Classic Class Descriptor RFC** adds the `descriptor` decorator for classic classes only which allows users to define native getters and setters (and other properties). This provides a clear 1-1 translation between native and classic syntax invocations as a way to add getters and setters to classic classes.
+
+Read and comment on the [Decorator Support RFC](https://github.com/emberjs/rfcs/pull/440) or the [Tracked Property Classic Class Descriptor RFC](https://github.com/emberjs/rfcs/pull/442) on GitHub!
+
+---
+
+## [Let's Fully Deprecate Partials! 🥛](https://github.com/emberjs/rfcs/pull/449)
+**Partials** in Ember have been around for quite some time. Today however, they are considered bad practice and all of their functionality **can be replaced** with Components. There is an [Ember Template Lint rule](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-partial.md) against their use. There was a [Pre-RFC](https://github.com/emberjs/rfcs/issues/390) created a while ago that recommended deprecating partials. Today we finally have a full RFC to [Deprecate Partials](https://github.com/emberjs/rfcs/pull/449) written up by [@GavinJoyce](https://github.com/GavinJoyce). If you want to learn more about the deprecation or maybe the alternatives to partials [check out the RFC](https://github.com/gavinjoyce/rfcs/blob/gj/deprecate-partials/text/0000-template.md). Also be sure to chime in and voice your concerns or add a 👍🎉 to the [RFC itself](https://github.com/emberjs/rfcs/pull/449).
+
+---
+
+## [Less Confused 🤷♀️🚫 with htmlSafe and with](https://github.com/emberjs/rfcs/pull/443)
+
+Two new **Requests for Comments (RFC)** propose deprecations to better avoid confusion in Ember apps:
+[One of the proposals](https://github.com/emberjs/rfcs/pull/443) aims to rename the `htmlSafe` template helper and util to `trustedHtml` in an effort to convey the mechanism of the util better.
+
+[The second RFC](https://github.com/emberjs/rfcs/pull/445) proposes the **deprecation** of the `with` template helper acknowledging the rather recent [`let` helper](https://guides.emberjs.com/release/templates/built-in-helpers/#toc_built-in-block-helpers), that can now be used in templates instead of and with much clearer intent than `with`.
+
+Be sure to check out the original proposals for [the renaming of *htmlSafe*](https://github.com/emberjs/rfcs/pull/443) and [the deprecation of the with helper](https://github.com/emberjs/rfcs/pull/445) and leave your comments below!
+
+---
+
+## [Ember Weekend RFC Roundup Redux Episode 🔈](https://twitter.com/emberweekend/status/1095017680892035072)
+
+Don't miss [@rondale-sc](https://github.com/rondale-sc) and [@code0100fun](https://github.com/code0100fun) interviewing [@rwjblue](https://github.com/rwjblue) on **Episode 128** of the **Ember Weekend podcast** [RFC Roundup Redux](http://emberweekend.com/episodes/rfc-roundup-reduce). They discussed the [auto-published unified RFC's repo](https://emberjs.github.io/rfcs/introduction.html), the [Glimmer Components RFC](https://emberjs.github.io/rfcs/0416-glimmer-components.html) and its implications for hooks, the [Render Element Modifiers RFC](https://emberjs.github.io/rfcs/0415-render-element-modifiers.html), including the official addon it proposes, and more!
+
+---
+
+## [An Ember Community Experience by Gaurav Munjal 💛](https://twitter.com/gaurav9576/status/1098298137507217408)
+
+I had wanted to make some large breaking changes to [ember-simple-tree](https://github.com/btecu/ember-simple-tree),
+in order to enable me to customize it to my liking. Given that it would break backward compatibility and existing applications, I figured my changes would never be accepted. So I forked it and released my version as **ember-light-tree**.
+
+I was surprised when **Bujorel Tecu** AKA [@btecu](https://github.com/btecu), the author of ember-simple-tree,
+contacted me and wanted to work together to include my changes. As a result, my changes are now in the latest version of
+ember-simple-tree.
+
+Even though we had to sacrifice technical backward compatibility, it was important to @btecu that we had **a shared solution**. One of the main strengths of Ember is how shared conventions enable developers to build on top of each other's work and **improve the ecosystem for everyone**. It's heartening to see this view echoed in the Ember addon community.
+
+---
+
+## ["I contribute to Ember" with Miguel Camba ✍️](https://discuss.emberjs.com/t/i-contribute-to-ember-with-miguel-camba/16193)
+
+
+This week we'd like to thank @rwjblue, @cibernox, @pzuraq, @ppcano, @Gaurav0, @MelSumner, @mixonic, @chrisrng, @runspired, @XaserAcheron, @scalvert, @mansona, @nummi, @jaredgalanis, @samselikoff, @aklkv, @bartocc, @locks, @jenweber, @EndangeredMassa and @CodingItWrong for their contributions to Ember and related repositories! 💖
+ +--- + +## [Got a Question? Ask Readers' Questions! 🤓](https://docs.google.com/forms/d/e/1FAIpQLScqu7Lw_9cIkRtAiXKitgkAo4xX_pV1pdCfMJgIr6Py1V-9Og/viewform) + +
+
+ Wondering about something related to Ember, Ember Data, Glimmer, or addons in the Ember ecosystem, but don't know where to ask? Readers’ Questions are just for you!
+ +Submit your own short and sweet question under bit.ly/ask-ember-core. And don’t worry, there are no silly questions, we appreciate them all - promise! 🤞
+ +