• magicsaifa@feddit.de
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I feel like the takeaway here should be that the experience of contributing to the project was not great. That’s it.

    There is value in complaining, even if you don’t have solutions. You can only make people aware of the consequences that their actions have caused by telling them.

    I don’t even take issue with him posting this publicly to his own Dev blog. I think its a perfectly fine piece of on-the-job experience OP has shared. Maybe in a few years he would like to come back to it with a different perspective.

    I do however think that OP posting this here (and apparently other boards) is a choice I don’t agree with. I think OP would have been better served writing a response email to the maintainer, explaining how they felt. Beyond that, what can one do?

    • lysdexic@programming.dev
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      6
      ·
      1 year ago

      I feel like the takeaway here should be that the experience of contributing to the project was not great. That’s it.

      I don’t think this is a valid summary. I think the first-time contributor had a rather self-centered approach to the bugfix, and turned a run-of-the-mill bugfix in a huge drama-riddled personal attack on a FLOSS maintainer for no good reason.

      Only in the OP’s one-sided and vindictive account of the whole ordeal does the project maintainer have questionable behavior. The central theme of the one-sided account is also absurd, as if a kernel maintainer needs to wait around for first-timers to contribute a patch for them to “rob” it to have a commit to show for.

      The whole soap opera is so regrettable, and the OP comes out not looking good at all.