• step in and help review a few PRs

  • help the project triage/reproduce bugs

  • if code in the PR looks complicated or is hard to understand, ask for an explanation

  • express your gratitude to the maintainers

  • make your company sponsor projects they depend on

https://mastodon.social/@bagder/112194895793007918

Daniel is the creator of cURL : https://daniel.haxx.se/blog/2021/03/30/howto-backdoor-curl/

  • twei@discuss.tchncs.de
    ·
    7 months ago

    is "step in and help review a few PRs" really that helpful? like... oh great, now this one person that i don't trust is telling me that the other person that i don't trust made some code that i should merge

    • solarvector@lemmy.ml
      ·
      7 months ago

      How does one become trusted? If they regularly review and provide feedback that you agree with it can really speed up the process, even if you're still double checking.

  • abeorch@lemmy.ml
    ·
    7 months ago

    I'd love to help out on Open Source projects but have often just not really known where to start. I guess the challenge is to become a experienced enough user of a specific project first.

    • lemmyreader@lemmy.ml
      ·
      7 months ago

      That one is maybe the easiest to do :

      express your gratitude to the maintainers

      Besides that there is the possibility to donate. And since the xz backdoor incident I would say it makes sense to keep an eye on end users trying to bully or overload developers. If I remember well I read that the developer of uMatrix stopped with that project because of annoying users filing bug reports with unfriendly and demanding discourse, which can be exhausting for a sole developer.

      • abeorch@lemmy.ml
        ·
        7 months ago

        Yeah agree this is the easiest.. I would like to help carry the load somehow. Perhaps filtering /dealing with comments could be a start.