At the moment of writing, there are 104 open pull requests to Meteor. Except for very basic pull requests, it is really hard to get any pull requests into the Meteor. Often you get only first comment/feedback from MDG, but after that the pull request stays in the limbo. I can understand that MDG has issues processing all tickets, but pull requests are really important to be processed quickly because otherwise they become obsolete, merging gets harder and harder, and also developers who made them have issues getting back to them if they are done for an old project, in an old context.
Could pull request have a clear pipeline? Could you use labels to label them, to be clear which pull requests are waiting on action of its author, and which pull request are waiting on MDG?
I am commenting here as somebody with many pull requests merged in. It is and was a very painful process. If I would not be so invested into the project, I would probably long gave up on making pull requests.
As an open source project, I think Meteor is failing in this respect. There is a big difference between the “I open source the code and you can see it, but you cannot really be involved in it” vs. “I open source and I welcome the community to contribute and be part of the process”.
I think this is part of a broader issue of community involvement in Meteor planing and development.
It seems that there are some organizational issues with Meteor where it is hard to find anybody to take responsibility for merging a pull request. It feels like everyone from MDG just waits for somebody else to make a call. And then nobody appears. And then nothing happens.
I would suggest that it is really past due time for MDG to give commit bits to community members.
Also, please fix CircleCI tests. They seem to be failing by itself. And the output is completely impossible to read/parse.