Programming

17402 readers

144 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

What do y'all think about mailing lists and IRC as sole communication channels? (programming.dev)

submitted 1 year ago by onlinepersona@programming.dev to c/programming@programming.dev

64 comments fedilink hide all child comments

Say you want to contribute to a project and find out the only way to do so is by discussing the issue on IRC or the mailing list, then submitting the patch per email.

you are viewing a single comment's thread
view the rest of the comments

[–] ck_@discuss.tchncs.de 1 points 1 year ago (1 children)

Yes and it depends to both questions.

I participate in projects being developed on Github that have 5k+ open pull requests and the same amount of issues. At that volume of communication, the Github workflow of "clicking through stuff" is way inferior to an efficient email workflow. Essentially, your workflow turns into email anyways because its the only sane way to consume based on push, and yes, I know, you can reply to Github using email, but its not nearly as good as something made for email.

So, in my opinion, email is simpler to use that pull request. It is not easiser because it is not close to what people are used to.

[–] lysdexic@programming.dev 0 points 1 year ago* (last edited 1 year ago)

At that volume of communication, the Github workflow of “clicking through stuff” is way inferior to an efficient email workflow. Essentially, your workflow turns into email anyways because its the only sane way to consume based on push (...)

I don't agree. Any conversation on pull requests happens through issues/tickets, which already aggregate all related events and are trivially referenced through their permanent links, including through the Git repo's history.