First, thanks to all of you for at least being interested in Laravel! I love working on the framework and am glad other people are enjoying it.
One thing that has been bothering me is I have seen a few people say they don't contribute to Laravel because it seems like PRs get closed or shot down without much explanation. It's hard to tell how many people are actually experiencing this issue. However, even a few cases is something that really bothers me and I want to improve. On one hand, any project of significant size will have to turn away issues and PRs, but we want to try to at least make sure everyone feels like they are getting a "fair hearing".
First, if you have had a PR or issue get closed with no explanation or in a rude way, could you please PM me with a link so I could check it out and revisit the issue?
Secondly, I would also be welcome to suggestions on how to manage issues in general. PRs are a little easier to manage because there is actionable code to either merge or not merge. However, sometimes issues don't have an apparent good solution at the time, or maybe me as the maintainer is not sure if it is an edge case, or an installation or configuration issue, or a genuine issue with the framework.
Currently, I am the only one who manages PRs and I can stay on top of them well without getting behind. We often only have 15-20 open PRs across the **entire** Laravel GitHub organization. My biggest challenge is the "Issues" tab on GitHub. It gets a lot of activity and its hard to filter out genuine issues from support requests, configuration problems, general questions, etc. I must admit I rarely visit the issues tab and instead let Graham Campbell try to bubble up important issues to me privately so I can take a look at them. He is sort of serving as issue "curator" if you will and trying to filter through them so I don't have to read each one.
If anyone has better suggestions for how to manage issues and PRs so that it is less frustrating for people please let me know! Would love to discuss!
Thanks for all the detailed and honest feedback. I already have a few ideas for how we can improve things going forward. Quite a few of the complaints have been around Graham Campbell. I think Graham contributes a lot to the framework technically and definitely has a valuable place within the ecosystem. He knows **a lot** about PHP, Composer, and the ecosystem as a whole.
However, I think I am to blame for a lot of the frustration. I have been asking Graham to manage issues when really I think he shines best in other areas of contribution. We can make some changes where Graham can still contribute in a very valuable way, just perhaps not as the only person doing front-line issue support, which is probably better suited for a team of people that is more gifted with "customer support" type skills.
We need to expand the amount of people who are helping review these issues, and I've already reached out to one other person to help out in this area as well. I think when the people reviewing issues are overworked (Graham is a full-time student, intern, etc), we are going to get the short, terse responses that frustrate people. If we can spread the issue team out a little bit I think that will help everyone be in a better mood and not feel like they have to have a mad rush to close or work as many issues as possible.