I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.

  • nutomic@lemmy.ml
    11·
    1 year ago

    You kept posting offtopic comments which added nothing to resolving the issue. So I gave you a seven day ban, hopefully it will teach you a lesson.

    • Chefdano3@lemm.eeEnglish
      1·
      1 year ago

      You want to teach a lesson? The only lesson you’re teaching here is that you’re a twat. You get some hardheaded opinion on someone’s suggestion, refuse to listen to anything else, and ban them for explaining themselves. Grow up.

      • nieceandtows@programming.dev
        1·
        1 year ago

        Yeah this guy is acting as if he’s a programming god who created something nobody could. This instance is called programming.dev, filled with programmers who know a little something about this programming thing. I’m a 15yoe self taught data engineer, and if I understand one thing, it is that anybody can learn programming and become great at it. I’m always proud of my code, but I never think my code is perfect. Programming and technology as a whole is constantly evolving, and what was clever/genius/wizardry yesterday is obsolete tomorrow. The only asset to a programmer is to be able to always learn new stuff, because there is always new stuff and better ways to do what you did in the past. I don’t even give detailed directions to my interns because I want to see if they do things in a different way that is better than the way I usually do things.

    • August27th@lemmy.ca
      1·
      1 year ago

      You demonstrated that you are unaccountable. It’s a lesson for anyone considering investing in this project, indeed.

    • dudinax@programming.dev
      1·
      1 year ago

      The comments read like you banned the dev for making a telling point in favor of reopening the ticket.

      The lesson I take away is that your ego is more important to you than improving Lemmy.

      • nutomic@lemmy.ml
        11·
        1 year ago

        The issue was already open. I gave a temporary ban for posting pointless complaints which added nothing to resolving the issue.

    • Joe@feddit.uk
      1·
      1 year ago

      Quite the ego you have there, I bet you’re fun at parties.

      Projects fail when developers alienate their contributors. Grow up and act like an adult.

    • ByteWizard@lemm.eeEnglish
      1·
      1 year ago

      hopefully it will teach you a lesson.

      Egos are terribly ugly. Please put yours away.

      • August27th@lemmy.ca
        1·
        1 year ago

        They’d point you at the code of conduct link found in the very GitHub repo this incident concerns, but then you would realize how many of their own rules they’ve violated.

        • TragicNotCute@lemmy.worldEnglish
          1·
          1 year ago

          I admit I didn’t look before asking to see if they had one. Just took a look and good god. How can Lemmy devs be so crunchy and inclusive with how they want the community to operate and yet be so abrasive on GitHub? Wild shit.

      • mormund@feddit.de
        0·
        1 year ago

        Reopening the same issue multiple times after it getting closed is a dick move. The contributer was pretty clear about the reasoning why. You are just wasting people’s time with feature requests like that.

        • snowe@programming.devOPM
          1·
          1 year ago

          you’re misreading the situation. Dessalines (one of the creators of lemmy) opened an issue asking for feedback on a feature. Nutomic (the second creator of lemmy) immediately closed the issue, with no feedback and no discussion. Dessalines opened it again (for good reason, there was no discussion on the topic) and then nutomic closed it again. This continued several times. I then commented about why the feature was useful, and also gave feedback as to why the issue shouldn’t be closed. This was then marked off topic so that my comment wouldn’t be seen (since it made nutomic look bad). I commented again and was immediately banned, no warning, explanation, or discussion, continuing the trend of one of the main lemmy devs not knowing how to work on a major OSS project.

    • snowe@programming.devOPM
      01·
      1 year ago

      My first comment directly discusses the issue at hand. It wasn’t off topic. It’s clear you didn’t want any feedback on the issue because it makes you look bad. I explicitly talked about how client side scheduling is a bad idea that does not accomplish the goal of scheduling. And then I gave feedback directly concerning the exact issue I was commenting on of how your conduct was unfitting of lead devs of a major software project, where you squabbled in public in a really weird way, and you refused to even think about discussing the topic (closing the issue over and over again when your coworker had opened it and asked for discussion? Really dude?). Then you finally banned me without any warning or discussion of why.

      And no, it’s not going to teach me any lesson, all it did was teach the entire community you have no clue how to run an open source software project. No warning, no explanation, just juvenile marking of comments as off topic (they weren’t), closing of the issue your main dev opened and then boom banned.

      • mark@programming.dev
        11·
        1 year ago

        This isnt the first time Nutomic has reacted in such a egotistical way, especially when someone points out a flaw in the software. I’ve seen a few issues that were actual issues with the software–not feature requests–that he’s closed and dismissed. One of the issues were mine. He definitely needs help with maintaining the software but I dont know how he expects anyone to help with the way he’s been acting.

      • nutomic@lemmy.ml
        11·
        1 year ago

        My comment about scheduling in clients was from January and that option was already discarded by dessalines on the next day. No use in rehashing the same thing ten months later. All you are doing is creating pointless notifications for everyone. I know its not ideal to close and reopen an issue, but really why is it a big deal? We closed hundreds of issues recently which were outdated, invalid or already fixed. I accidentally closed one that still needs to be implemented and dessalines reopened it, so everything is fine. Certainly not a “squabble”, and your comments added nothing at all.

        Its true that I shouldnt have given a warning first, but most likely you would have responded with another offtopic complaint so I didnt see any use in that. If you want to complain then do it somewhere else, not on the issue tracker which is meant for getting work done.