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.

  • @[email protected]OPEnglish
    1•1 year ago

    Do you find mailing lists easier to use than pull requests / merge requests? And how do you find following a discussion in a mailing list?

    • @hperrin
      3•1 year ago

      For newer/inexperienced users mailing lists are definitely easier. Everyone can send an email.

    • @[email protected]English
      1•1 year ago

      From a contributor point of view, mailing lists are definitely easier than pull/merge requests - you just send a patch which you can create in any way you want to an email address.

      Following a discussion is easy - it’s just a list of messages. In fact, it is easier for me since I use Gnus as my email client, which gives me a threaded view of discussions on the list.

      • @[email protected]English
        0•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.