[Project]: Not Accepting Community Input #48
Description
Project Name (1 - 3 words)
Not Accepting Community Input
Description
Can we identify projects that aren't accepting input from the community?
An open source project owned and maintained by a single company can sometimes want to control the projects direction and codebase to a large extent such that outside parties issues and pull requests are never closed/merged. Functionally, this means no ability to add features that are important to you.
- Is there a way to recognize repositories that have a minimum number of issues or pull requests that:
- Have not been closed after message added for issue and closed without merge for pull requests.
- The pull requests or issues in step 1 being opened by users who have not approved a pull request or submitted a successful one.
- The number of users who meet both step 1 and step 2 probably needs to be over some threshold of obviousness. Maybe 7 users?
This is often related to Elephant Factor, which refers to too much control by a single company. These negative events in a project’s life that are strongly associated with too much single company control, meaning they are different than what occurs in a project with a diverse community of contributors and maintainers.
Related Links
No response
How would you like to be involved in this project?
I am interested in this project, but do not plan to work on it myself
Additional Notes.
No response