Description of the problem
Three.js is getting more popular and bigger. Lot of PRs are opened day after day.
I think it leads to a problem. Lately reviewing takes longer. Then many PRs are stacked now. On 2019/05/17 there’re 257 opened PRs. 65 of them are tagged as r105 (next release). Some of them are looking ok to me, or even approved by reviewers, but not merged yet.
Currently only @mrdoob makes the final decision to merge a PR basically. As Three.js is bigger he has a heavier workload for reviewing. And when he has some busy periods, the three.js development slows down.
I’d like to discuss how we the contributors can help him and can speed up Three.js development.
Rough idea in my mind so far is, I think granting merge to some of the contributors and distributing workload may be good. For example
- Grant merging obviously clear and correct PRs, for example just typo or easy bug fix, to some of contributors.
- Grant merging PRs for a certain module to the module author or contributors who mainly maintenance
And also @mrdoob can grant merge to assigned reviewers.
With these ideas, he can focus on only the PRs very depending on his opinion.
And @mrdoob, if you have any ideas to help you, I’d very pleased if you share with us. I’m sure many developers including me are willing to help you.
- All of them
- Internet Explorer
- All of them