├── README.md
└── .github
    └── ISSUE_TEMPLATE
        └── track-rfc-progress.md


/README.md:
--------------------------------------------------------------------------------
 1 | # RFC Tracking
 2 | 
 3 | Repo for issues to track progress of accepted [Ember RFCs](https://github.com/emberjs/rfcs)
 4 | 
 5 | For each merged RFC a tracking issue is opened. It is assigned to the champion(s) of the RFC. Also available to view in a [project](https://github.com/orgs/emberjs/projects/3). 
 6 | 
 7 | Each RFC needs to be planned by each team. For an example of a planned RFC, see https://github.com/emberjs/rfc-tracking/issues/3 Please use checklists to enable the progress bar. 
 8 | 
 9 | Each team may wish to amend the template for their second (listing expected areas to consider, for example). 
10 | 
11 | ### Champion Tips
12 | 
13 | - [ ] Follow the checklists on the RFC repo https://github.com/emberjs/rfcs#champion-responsibilities
14 | - [ ] Assign yourself to the tracking issue
15 | - [ ] Add labels to the tracking issue. Edition, relevant team(s) as specified in the RFC
16 | - [ ] Ensure each team considers & plan the RFC, adding tasks & issues to the tracking issue
17 | - [ ] Update the tracking issue regularly
18 | - [ ] Make sure the tracking issue is formatted correctly (checkboxes for each task) to gain progress bars
19 | - [ ] Update the project board https://github.com/orgs/emberjs/projects/3 when the RFC enters a new stage
20 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/track-rfc-progress.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | name: Track RFC Progress
 3 | about: This issue template should be completed to track an RFC from emberjs/rfcs
 4 | title: 'RFC #0000 - Tracking for {{RFC Description}}'
 5 | labels: needs planning:ember.js, needs planning:ember-cli, needs planning:ember-data,
 6 |   needs planning:learning
 7 | assignees: ''
 8 | 
 9 | ---
10 | 
11 | ## [RFC #0000](https://github.com/emberjs/rfcs/blob/master/text/0000-ABCDE.md) - Tracking for {{RFC Description}} 
12 | 
13 | Champion: {{@-champion-}}
14 | 
15 | ---
16 | 
17 | <details>
18 |   <summary>Expand for Instructions</summary>
19 |   
20 | All teams need to consider a merged RFC to plan any required work. Each team should comment on or edit this with links to issues for the work (or a note to the effect of "No work required"). 
21 | 
22 | See [the README](https://github.com/emberjs/rfc-tracking/blob/master/README.md) for more information
23 | See https://github.com/emberjs/rfc-tracking/issues/3 for an example
24 | 
25 | Under each team, for each repo requiring work for the RFC under that team:
26 | `### [repo name](repo url)`
27 | 
28 | `- [ ] (issue or pr) description, (issue or pr) link` 
29 | 
30 | Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.
31 | </details>
32 | 
33 | ### Ember.js Team:
34 | 
35 | #### [ember.js](https://github.com/emberjs/ember.js)
36 | 
37 | <!--
38 | 
39 | - [ ] A thing required for this RFC in this repo, https://github.com/emberjs/ember.js/pull/ABCDE
40 | 
41 | -->
42 | 
43 | ### Ember CLI Team:
44 | 
45 | #### [ember-cli](https://github.com/ember-cli/ember-cli)
46 | 
47 | <!--
48 | 
49 | - [ ] A thing required for this RFC in this repo, https://github.com/ember-cli/ember-cli/pull/ABCDE
50 | 
51 | -->
52 | 
53 | ### Ember Data Team:
54 | 
55 | #### [ember-data](https://github.com/emberjs/data)
56 | 
57 | <!--
58 | 
59 | - [ ] A thing required for this RFC in this repo, https://github.com/emberjs/data/pull/ABCDE
60 | 
61 | -->
62 | 
63 | ### Learning Team:
64 | 
65 | #### [guides-source](https://github.com/ember-learn/guides-source)
66 | 
67 | <!--
68 | 
69 | - [ ] A thing required for this RFC in this repo, https://github.com/ember-learn/guides-source/pull/ABCDE
70 | 
71 | -->
72 | 
73 | ### Steering Committee:
74 | 
75 | N/A
76 | 


--------------------------------------------------------------------------------