• it/its

// the deer!
// plural deer therian θΔ, trans demigirl
// stray pet with a keyboard
// i'm 20 & account is 18+!
name-color: #ebe41e
// yeah



iliana
@iliana

i think i’ve decided that for personal projects it’s probably not worth doing code review cycles with contributors. if a pull request is doing something worthwhile you can apply the changes you want on top of that and merge it with your changes.

big thorny 150,000-line 40-contributor work repos are another story for several reasons but my 2,000-line weekend project is not meant to be a shining beacon of software engineering acumen


iliana
@iliana

i think this comes from regularly being the open source contributor who gets asked to make changes before they can be merged. i didn’t really care whether it felt like the maintainer was wasting my time but it just felt like the maintainer was wasting their time trying to get a beautiful sandwich out of someone without a deli slicer

if you know exactly how you want it to look, make it happen


You must log in to comment.

in reply to @iliana's post:

I've been thinking about this a bunch. For me there's a threshold beyond which I'd want the other person to do it (e.g. some sort of fundamental architectural issue), but for minor changes I just amend their commits and push the result. This is pretty common in some open source communities from what I've seen.