Comment on What does Lemmy think of Daniel Supernault or on mastodon?

• solidheron@lemmy.world ⁨6⁩ ⁨days⁩ ago

  I’ll hear you out can you explain with only the context I’ve given you btw I only told two people the entire story. Why calling him out is the issue. Let’s put you on the spot and watch you crumble

  source

  • PhilipTheBucket@ponder.cat ⁨6⁩ ⁨days⁩ ago

    Are you asking me to explain why chasing after someone who’s writing a bunch of software for you for free, because they didn’t meet your expectations, to the point that they block you, is wrong?

    Like I say, I honestly think you just need to grow up a certain amount before you interact directly with people who develop fedi software, because you clearly just think this is okay and are genuinely surprised at the unanimous crowd of people telling you that it is not.

    Dan, like a lot of people, is a human being. He’s allowed to miss deadlines or make angry posts on social media that he then feels bad about after. You’re not allowed to chase after him and treat him like you’re in some kind of position to be judging how well he’s performing. I have stopped working on projects before, because of people interacting with me in a way that rubbed me the wrong way and I just didn’t feel like subjecting myself to it. Having ingrates like you squalling at the fedi developers about how they need them to start meeting all the deadlines or they’re going to “call them out a lot” is going to drive people away from developing free software. Don’t do that. I keep telling you: I do not care about the further context. You are already wrong, when you are demanding anything at all in the manner that you’ve described.

    source

    • solidheron@lemmy.world ⁨6⁩ ⁨days⁩ ago

      Nope not at all. Hint read my post

      source
  • actionjbone@sh.itjust.works ⁨6⁩ ⁨days⁩ ago

    Calling him out his criticizing him. Full stop.

    I don’t even know who he is, and I can tell he isn’t the issue.

    You seem unable to recognize that you are not owed anything.

    Anything he said is irrelevant.

    source

    • solidheron@lemmy.world ⁨6⁩ ⁨days⁩ ago

      “Calling him out his criticizing him”

      Run your shit shit through an ai and let it pick something something coherent. You can’t even make a case why calling him out is an issue

      source

      • PhilipTheBucket@ponder.cat ⁨6⁩ ⁨days⁩ ago

        Sure thing.

        Hey, what’s your take on this thread? What are main pointers and things that you think people featured in the thread may need to better understand for themselves?

        After analyzing this thread, here are the key observations and points for reflection:

        Communication Dynamics and Expectations:

        • The OP repeatedly “called out” a FOSS developer (Daniel Supernault) for perceived lack of progress and unfulfilled promises about releasing source code
        • Many community members pointed out that public criticism and repeated confrontation isn’t a constructive approach, especially with volunteer developers

         

        Understanding of FOSS Development:

        • There’s a fundamental misunderstanding about the nature of free/open source software development
        • Several experienced developers in the thread explained that FOSS developers:
        • Are not beholden to user-imposed deadlines
        • Can work at their own pace
        • Don’t owe users specific deliverables, even if previously promised
        • May have multiple projects and personal commitments

         

        Areas for Growth:

        • For the OP:

        • Need to understand the difference between constructive feedback and harassment
        • Could benefit from learning about FOSS culture and etiquette
        • Might need to reflect on their approach to communication and expectations management

        • For Daniel (the developer):

        • Could improve communication around timelines and manage expectations better
        • Might benefit from being more careful about making specific promises about release dates

         

        Community Response:

        • The community showed strong unity in defending FOSS developers’ right to work at their own pace
        • Demonstrated clear boundaries about acceptable behavior in the FOSS community
        • While firm, many responses tried to be educational rather than purely confrontational

         

        Broader Lessons:

        • The importance of maintaining constructive dialogue even when frustrated
        • The value of understanding the volunteer nature of most FOSS work
        • The need to balance enthusiasm for projects with respect for developers’ time and autonomy
        • The significance of managing expectations in open source communities

         

        This situation reflects common tensions in FOSS communities between user expectations and developer capacity/priorities. Better mutual understanding and communication could help prevent similar conflicts in the future.

        source

        • -> View More Comments