You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’re using Discussions as a place to connect with other members of our community. We hope that you:
Ask questions you’re wondering about.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we build together 💪.
FAQ
Why are GitHub issues disabled?
I don't want to spend my free time as an unpaid project manager.
I took some inspiration from the encode organization (Tom Christie and friends) when thinking about this. Encode is responsible for great Python packages like HTTPX, Starlette, and Uvicorn. The encode maintainers are implementing "maintainer-driven issues." As described in the encode contribution guidelines:
Taking issues and suggestions to the discussion group, will help allow us to have a more consistent voice in setting the direction and priorities of the project. Over time the issue tracker should more clearly reflect what we feel is important, and pull requests should tend to better reflect active ongoing work.
It’ll also help reduce stress and burnout, particularly important during these difficult times, by ensuring that the project maintainers are able to keep issue trackers nicely limited in scope.
The maintainer-driven issues approach makes sense for an organization like encode. For me as a solo maintainer, I can drive changes to the project myself, so I don't really need GitHub issues at all.
I also think having project management as a paid premium feature could be a useful open-source business model. GitHub should enable this, maybe by allowing access to issues only if the user sponsors the project with GitHub Sponsors. Again, encode does a nice job of this, offering sponsorship tiers and providing monthly reports.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
FAQ
Why are GitHub issues disabled?
I don't want to spend my free time as an unpaid project manager.
I took some inspiration from the encode organization (Tom Christie and friends) when thinking about this. Encode is responsible for great Python packages like HTTPX, Starlette, and Uvicorn. The encode maintainers are implementing "maintainer-driven issues." As described in the encode contribution guidelines:
The maintainer-driven issues approach makes sense for an organization like encode. For me as a solo maintainer, I can drive changes to the project myself, so I don't really need GitHub issues at all.
I also think having project management as a paid premium feature could be a useful open-source business model. GitHub should enable this, maybe by allowing access to issues only if the user sponsors the project with GitHub Sponsors. Again, encode does a nice job of this, offering sponsorship tiers and providing monthly reports.
How can I contribute?
PRs welcome!
How should I behave?
As explained in the code of conduct, we recommend:
Beta Was this translation helpful? Give feedback.
All reactions