From ca36ab2e7dc1f27816ebdc41e5b13f03a1d7f4af Mon Sep 17 00:00:00 2001 From: Kenneth Larsen Date: Fri, 9 Nov 2018 07:31:39 +0100 Subject: [PATCH 1/5] Added section on RFC 300 --- source/blog/2018-11-09-the-ember-times-issue-72.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/source/blog/2018-11-09-the-ember-times-issue-72.md b/source/blog/2018-11-09-the-ember-times-issue-72.md index 1a50796171..f16981b449 100644 --- a/source/blog/2018-11-09-the-ember-times-issue-72.md +++ b/source/blog/2018-11-09-the-ember-times-issue-72.md @@ -1,6 +1,6 @@ --- title: The Ember Times - Issue No. 72 -author: Chris Ng, the crowd +author: Chris Ng, Kenneth Larsen, the crowd tags: Recent Posts, Newsletter, Ember.js Times, Ember Times, 2018 alias : "blog/2018/11/09-the-ember-times-issue-X72X.html" responsive: true @@ -9,7 +9,7 @@ responsive: true Emberistas! 🐹 . -We need **Emberistas at JSConf EU**, so submit a talk to the newly opened CFP! 🗣️ +We need **Emberistas at JSConf EU**, so submit a talk to the newly opened CFP! 🗣️, there's an update to the RFC about RFCs!, --- @@ -26,8 +26,13 @@ _”Pick the topic you feel most passionate about. This is your conference.”_ --- -## [SECTION TITLE](#section-url) +## [Yo Dawg, I Heard You Like RFCs](https://github.com/emberjs/rfcs/pull/300) +There has been an update to the RFC about the RFC process itself. The RFCs has been crucial in defining **the future of Ember** and that is still the case. +However, in the process of reading and merging all of these RFCs the Core Team has discovered some shortcomings of the current RFC process as well as new requirements. + +To solve some of these issues the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging ember-cli/rfcs into emberjs/rfcs. +There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md) which I recommend you read through and leave a comment with your thoughts. --- @@ -99,4 +104,4 @@ That's another wrap! ✨ Be kind, -Chris Ng, the crowd and the Learning Team +Chris Ng, Kenneth Larsen, the crowd and the Learning Team From 36f68716e4c987251753e6be7eebe8ef489d8890 Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Fri, 9 Nov 2018 08:01:40 +0100 Subject: [PATCH 2/5] Update source/blog/2018-11-09-the-ember-times-issue-72.md Co-Authored-By: kennethlarsen --- source/blog/2018-11-09-the-ember-times-issue-72.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/2018-11-09-the-ember-times-issue-72.md b/source/blog/2018-11-09-the-ember-times-issue-72.md index 3dfa3da5b8..dff935ab01 100644 --- a/source/blog/2018-11-09-the-ember-times-issue-72.md +++ b/source/blog/2018-11-09-the-ember-times-issue-72.md @@ -28,7 +28,7 @@ _”Pick the topic you feel most passionate about. This is your conference.”_ ## [Yo Dawg, I Heard You Like RFCs](https://github.com/emberjs/rfcs/pull/300) There has been an update to the RFC about the RFC process itself. The RFCs has been crucial in defining **the future of Ember** and that is still the case. -However, in the process of reading and merging all of these RFCs the Core Team has discovered some shortcomings of the current RFC process as well as new requirements. +However, in the process of reading and merging all of these RFCs, the Core Team has discovered some shortcomings of the current RFC process as well as new requirements. To solve some of these issues the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging ember-cli/rfcs into emberjs/rfcs. From c075bb5204a4203990a2114494b4290f7e223010 Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Fri, 9 Nov 2018 08:01:53 +0100 Subject: [PATCH 3/5] Update source/blog/2018-11-09-the-ember-times-issue-72.md Co-Authored-By: kennethlarsen --- source/blog/2018-11-09-the-ember-times-issue-72.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/2018-11-09-the-ember-times-issue-72.md b/source/blog/2018-11-09-the-ember-times-issue-72.md index dff935ab01..d60c7400b0 100644 --- a/source/blog/2018-11-09-the-ember-times-issue-72.md +++ b/source/blog/2018-11-09-the-ember-times-issue-72.md @@ -30,7 +30,7 @@ _”Pick the topic you feel most passionate about. This is your conference.”_ There has been an update to the RFC about the RFC process itself. The RFCs has been crucial in defining **the future of Ember** and that is still the case. However, in the process of reading and merging all of these RFCs, the Core Team has discovered some shortcomings of the current RFC process as well as new requirements. -To solve some of these issues the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging ember-cli/rfcs into emberjs/rfcs. +To solve some of these issues, the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging [ember-cli/rfcs](https://github.com/ember-cli/rfcs) into [emberjs/rfcs](https://github.com/emberjs/rfcs). There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md) which I recommend you read through and leave a comment with your thoughts. From e84b4b582749a1eda1cb22a0182c8a28b3fd6b2e Mon Sep 17 00:00:00 2001 From: Amy Lam Date: Fri, 9 Nov 2018 08:02:14 +0100 Subject: [PATCH 4/5] Update source/blog/2018-11-09-the-ember-times-issue-72.md Co-Authored-By: kennethlarsen --- source/blog/2018-11-09-the-ember-times-issue-72.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/2018-11-09-the-ember-times-issue-72.md b/source/blog/2018-11-09-the-ember-times-issue-72.md index d60c7400b0..a51f992605 100644 --- a/source/blog/2018-11-09-the-ember-times-issue-72.md +++ b/source/blog/2018-11-09-the-ember-times-issue-72.md @@ -32,7 +32,7 @@ However, in the process of reading and merging all of these RFCs, the Core Team To solve some of these issues, the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging [ember-cli/rfcs](https://github.com/ember-cli/rfcs) into [emberjs/rfcs](https://github.com/emberjs/rfcs). -There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md) which I recommend you read through and leave a comment with your thoughts. +There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md), which I recommend you read through and leave a comment with your thoughts. --- From a05f498e96dcf16381b7e758abf3b1a03b2bc0d0 Mon Sep 17 00:00:00 2001 From: Kenneth Larsen Date: Fri, 9 Nov 2018 08:02:47 +0100 Subject: [PATCH 5/5] Update 2018-11-09-the-ember-times-issue-72.md --- source/blog/2018-11-09-the-ember-times-issue-72.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/2018-11-09-the-ember-times-issue-72.md b/source/blog/2018-11-09-the-ember-times-issue-72.md index a51f992605..9aab176991 100644 --- a/source/blog/2018-11-09-the-ember-times-issue-72.md +++ b/source/blog/2018-11-09-the-ember-times-issue-72.md @@ -32,7 +32,7 @@ However, in the process of reading and merging all of these RFCs, the Core Team To solve some of these issues, the RFC proposes that new RFCs are assigned a **Core Champion** from the Core Team as well as merging [ember-cli/rfcs](https://github.com/ember-cli/rfcs) into [emberjs/rfcs](https://github.com/emberjs/rfcs). -There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md), which I recommend you read through and leave a comment with your thoughts. +There are more proposed solutions in [the RFC](https://github.com/emberjs/rfcs/blob/rfc-process-update/text/0300-rfc-process-update.md), which we recommend you read through and leave a comment with your thoughts. ---