Skip to content

Show active feature flags in project admin at readthedocs.org #5046

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

Closed
dojutsu-user opened this issue Dec 28, 2018 · 3 comments
Closed

Show active feature flags in project admin at readthedocs.org #5046

dojutsu-user opened this issue Dec 28, 2018 · 3 comments
Labels
Needed: design decision A core team decision is required

Comments

@dojutsu-user
Copy link
Member

Users can open an issue to request for the feature flags.
I think it would be good to just show them the list of active feature flags for their project. It will avoid confusion that whether it is active or not or how many are active.

Related #5044

@dojutsu-user
Copy link
Member Author

I am a little confused on this.
Will this be okay to implement it or not?

@humitos
Copy link
Member

humitos commented Jan 2, 2019

I'm not sure, but at first sight, I'd say that we shouldn't show the Features to the end user since this is something we use internally to hack or change the normal workflow in some way.

Although, we are about to expose them in a document (#5043) for the user to know they do exist. So, I'm not sure.

I'd ask for more opinions here.

In case we do finally expose them, we should also consider the case for corporate site and if we do to expose them there also.

@humitos humitos added the Needed: design decision A core team decision is required label Jan 2, 2019
@agjohnson
Copy link
Contributor

I also don't think we want to surface this. We use feature flags as an internal mechanism, it's not a user mechanism we need to communicate to the uesrs. Further, we do automatic sampling and I'm not sure we need to, or want to, alert the user to some of these.

I'll close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants