5 ms·
The attach and upload part, and figuring out how the discussion went on the mailing list if changes are requested.
by rocqua 8y ago
The attach and upload part, and figuring out how the discussion went on the mailing list if changes are requested.
- colbyrussell 8y agoWhat makes either of those things harder than what you have to do to use github.com?
- jyrkesh 8y agoIt's hard when you have lots of folks jumping into a code review, and you don't want to duplicate effort or you want to rapidly iterate on your code. You know those email chains that just continue to fork? Where people reply to the original (or the first couple replies) with their wall of text after a couple other replies have already trickled through? That's what a collaborative, stateful PR solves.
- colbyrussell 8y agoEveryone is trying to get me to defend mailing lists. I have no idea why. I haven't said anything about them. In fact, I hate mailing lists.
- chinhodado 8y ago> I haven't said anything about them. > # now attach/upload bugfix.patch Where do you "attach" your patch file? Also, if it's not GitHub/GitLab/gerrit/reviewboard/etc. and not mailing list, what other workflow for code contribution are you talking about then?
- colbyrussell 8y agoI'm not going to be strawmanned for the third time in this conversation. I didn't say it wasn't GitHub/GitLab/gerrit/reviewboard/etc and not a mailing list. I said it's not a mailing list. This message board is a cesspool.
- chinhodado 8y agoIf you have never contributed to a project before, the "attach patch and upload/send mail" part is a significant hurdle. You have to figure out which mailing list to use, which is not always easy to find, then find out the person/group to address it to. That alone already discouraged many people from even bother.