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

RFC #0431 - Tracking for Restructuring the Guides Table of Contents #29

Open
jenweber opened this issue Feb 14, 2019 · 0 comments

Comments

4 participants
@jenweber
Copy link

commented Feb 14, 2019

RFC #0431 - Tracking for Restructuring the Guides Table of Contents

Champion: @jenweber


Expand for Instructions

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").

See the README for more information
See #3 for an example

Under each team, for each repo requiring work for the RFC under that team:
### [repo name](repo url)

- [ ] (issue or pr) description, (issue or pr) link

Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.

Ember.js Team:

No work required

Ember CLI Team:

No work required

Ember Data Team:

No work required

Learning Team:

Guides-Source Octane issues

Steering Committee:

No work required

@kategengler kategengler added this to Accepted in RFC Tracking Mar 1, 2019

@kategengler kategengler changed the title RFC #431 - Tracking for Restructuring the Guides Table of Contents RFC #0431 - Tracking for Restructuring the Guides Table of Contents Mar 1, 2019

@kategengler kategengler moved this from Accepted to Planning in RFC Tracking May 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.