dygear[m] has quit [Quit: Idle timeout reached: 172800s]
jannic[m] has quit [Quit: Idle timeout reached: 172800s]
milan[m] has quit [Quit: Idle timeout reached: 172800s]
ivmarkov[m] has joined #rust-embedded
<ivmarkov[m]>
<JamesMunns[m]> "This is very good but not what I..." <- I can't keep but wondering whether the "cleanup/refactor-post-commit" strategy does work for keeping around contributors though. As in - it can be misinterpreted as "oh well, I'm tired explaining and providing feedback, it is just easier for me to just re-code it my way" which is not exactly motivating either.
morfertaw[m] has quit [Quit: Idle timeout reached: 172800s]
sirhcel[m] has quit [Quit: Idle timeout reached: 172800s]
<JamesMunns[m]>
<ivmarkov[m]> "I can't keep but wondering..." <- Yep, I'm sure it's more subtle than a single blog post. That being said, there are likely a lot of projects that end up not merging drive by commits that could be useful, but the submitter never came back to address review comments
<ivmarkov[m]>
JamesMunns[m]: ...which shifts the whole load back to the maintainer, which is not the desired state either...
<ivmarkov[m]>
ivmarkov[m]: I think in the end, this could only work if indeed some of the maintainers are paid and have like 8 hours per day to review/merge stuff.
<JamesMunns[m]>
<ivmarkov[m]> "I think in the end, this could..." <- 100% agree there is no "one size fits all" approach. I think Aleksey's approach worked really well for RA (where he was largely a paid maintainer for many years!), where there were a lot of PRs that fit that profile.