3 ms·
> The bar to contribute should be high. The issue is things lingering in limbo. It's okay to have a high bar. It's not okay to let things remain unreviewed a
by bsder 4y ago
> The bar to contribute should be high.
The issue is things lingering in limbo.
It's okay to have a high bar. It's not okay to let things remain unreviewed and open.
If your project staff can't handle the volume of changes, then don't pretend you're open. Admit that you have a closed set of developers and stop accepting changes from outside. THERE IS NOTHING WRONG WITH THAT.
- bluenose69 4y agoI always thought that a contribution that lingers in limbo (a great phrase!) has effectively been rejected. I agree that active projects that habitually ignore useful contributions for unreasonable time intervals risk losing favour in the open-source community. But whether Go falls into this category is beyond my ken.