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

The docs do not make it clear what features should go in Tutor core vs plugins #683

Open
regisb opened this issue Jun 7, 2022 · 0 comments
Labels
documentation In order to close this issue, some documentation should be improved

Comments

@regisb
Copy link
Contributor

regisb commented Jun 7, 2022

@fghaas made a comment here:

It looks like your policy is, by and large, "don't add new configuration settings to Tutor, use a plugin instead." That's all fair and good but please make that policy explicit. Currently, the contributor documentation does not mention any of this. It's not at all self-evident that people should default to not adding new configuration parameters.

We need to make it clearer to external contributors which changes should go in Tutor core, and which ones should go in plugins.

@regisb regisb changed the title The docs does not make it clear what features should go in Tutor core vs plugins The docs do not make it clear what features should go in Tutor core vs plugins Jun 7, 2022
@regisb regisb moved this to Backlog in Tutor project management Sep 8, 2022
@regisb regisb added the documentation In order to close this issue, some documentation should be improved label Mar 9, 2023
@regisb regisb moved this from Backlog to In Progress in Tutor project management May 18, 2023
@regisb regisb moved this from In Progress to Backlog in Tutor project management May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation In order to close this issue, some documentation should be improved
Projects
Development

No branches or pull requests

1 participant