Skip to content

Limit creation of new issues and clarify bug report process #9690

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

browniebroke
Copy link
Member

Description

As follow up from #9660, limit new issue creation and clarify process for reporting bugs.

This is how it looks:

image

Copy link
Member

@auvipy auvipy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets have some more eyes on this before we merge

@johnthagen
Copy link
Contributor

First off, thanks for all the great work that has gone into DRF! ❤️

Just wanted to add a viewpoint as user of DRF. It was shocking/worrying when the issues and discussions were hidden wholesale earlier (see some comments here: https://github.com/orgs/encode/discussions/11). It signaled to me not this project wasn't just "done" (the intention) but felt more like "dead". I worried that if new users came to DRF and saw that state, they would be turned away and thus the project would slowly lose relevance and activity.

I'm glad to see that this has been reverted.

I wanted to share my recommendation this insight that whatever state this lands on, that it still allows users to easier report/discuss issues as it has a big impact on how the project is viewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants