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.

Sign up for GitHub

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

Jump to bottom

Unify reforms and extensions information hierarchy #63

Open

1 of 3 tasks

MattiSG opened this issue Apr 20, 2017 · 0 comments

Open

1 of 3 tasks

Unify reforms and extensions information hierarchy #63

MattiSG opened this issue Apr 20, 2017 · 0 comments

Member

MattiSG commented Apr 20, 2017 •

edited by bonjourmauko

Loading

Reforms are currently presented as part of the “key concepts” while extensions are part of the “contribute” part, and do not link back to reforms.

Make extensions a part of the “key
concepts”.
Make reforms a specific instance of extensions (or the other way around?).
Make it clear for the user in which case she should use which mechanism.

MattiSG added the extensions label

bonjourmauko removed the scope:extension label

fpagnoux added the flow:backlog label

sandcha added flow:next and removed flow:qualified-issues labels

sandcha added flow:qualified-issues and removed flow:next labels

bonjourmauko added kind:documentation and removed flow:qualified-issues labels

MattiSG removed the kind:documentation label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment