Bobinas P4G
  • Login
  • Public

    • Public
    • Groups
    • Popular
    • People

Conversation

Notices

  1. muesli (fribbledom@mastodon.social)'s status on Wednesday, 30-Mar-2022 22:04:19 UTC muesli muesli

    Open source "pro tip": stop asking questions like "any updates on this?!" in tickets. It's annoying, spammy, and sometimes even passive-aggressive.

    If there were updates, the system would have directly linked them to the ticket and you wouldn't have to ask.

    In conversation Wednesday, 30-Mar-2022 22:04:19 UTC from mastodon.social permalink
    • Wolf480pl (wolf480pl@mstdn.io)'s status on Thursday, 31-Mar-2022 00:23:03 UTC Wolf480pl Wolf480pl
      in reply to
      • muesli
      • Baloo Uriza

      @BalooUriza @fribbledom
      counterpoint: at $dayjob, we (SRE team) rely on people asking multiple times if they still care about something. If we end up not doing it immediately, and a few weeks pass since the initial request without anyone asking again, we will assume it's no longer needed.

      In conversation Thursday, 31-Mar-2022 00:23:03 UTC permalink
    • Baloo Uriza (baloouriza@social.tulsa.ok.us)'s status on Thursday, 31-Mar-2022 00:23:07 UTC Baloo Uriza Baloo Uriza
      in reply to
      • muesli

      @fribbledom Related: Stop doing this to your IT department, too, especially if your ticket is not SLA bearing.

      In conversation Thursday, 31-Mar-2022 00:23:07 UTC permalink
    • jollyrogue@social.tulsa.ok.us's status on Thursday, 31-Mar-2022 00:23:15 UTC jollyrogue jollyrogue
      in reply to
      • muesli
      • Wolf480pl
      • Baloo Uriza

      @wolf480pl @BalooUriza @fribbledom So true. It’s an accurate way to gauge how invested a person is in getting a solution.

      If a person asks twice, it’s important, and we need to prioritize it.
      If a person asks once, it might be important, and we should triage it.
      If a person doesn’t ask, it’s probably not important, and we’ll ask about it when we get around to it. 😆

      In conversation Thursday, 31-Mar-2022 00:23:15 UTC permalink
    • Joe :dnd: (popekingjoe@mastodon.social)'s status on Thursday, 31-Mar-2022 01:06:13 UTC Joe :dnd: Joe :dnd:
      in reply to
      • muesli

      @fribbledom It'll be ready when it's ready and not a moment sooner.

      In conversation Thursday, 31-Mar-2022 01:06:13 UTC permalink
    • Sasha Sorokin 🏳‍🌈 (sasha_sorokin@mastodon.social)'s status on Thursday, 31-Mar-2022 03:47:53 UTC Sasha Sorokin 🏳‍🌈 Sasha Sorokin 🏳‍🌈
      in reply to
      • muesli

      @fribbledom

      This issue is stale. It will be closed if there's no further activity...

      In conversation Thursday, 31-Mar-2022 03:47:53 UTC permalink
    • Acesabe (acesabe@mastodon.social)'s status on Thursday, 31-Mar-2022 07:56:21 UTC Acesabe Acesabe
      in reply to
      • muesli

      @fribbledom this is an interesting one, depending on your angle, I've worked on IT customer support and although ideally all tickets should be updated within X time, in reality this doesn't happen unless it's chased by customer, in dev world it's often impossible for end user to know whether the issue/project is too busy, uninterested or just dormant/dead, issues need to be visible in the queue of all issues/requests so people don't have to ask. I've dropped using many apps due to dormancy.

      In conversation Thursday, 31-Mar-2022 07:56:21 UTC permalink
    • muesli (fribbledom@mastodon.social)'s status on Thursday, 31-Mar-2022 13:56:53 UTC muesli muesli
      in reply to
      • Matthias Schmidt
      • Daniel Gibson

      @Doomed_Daniel @_xhr_

      Yeah agreed, a bot deciding if something is considered stale is pretty ridiculous.

      In conversation Thursday, 31-Mar-2022 13:56:53 UTC permalink
    • Daniel Gibson (doomed_daniel@mastodon.technology)'s status on Thursday, 31-Mar-2022 13:56:54 UTC Daniel Gibson Daniel Gibson
      in reply to
      • Matthias Schmidt
      • muesli

      @fribbledom @_xhr_
      Unfortunately there are projects that enforce this kind of behavior by automatically closing tickets with no activity after some time. I fucking hate it.

      In conversation Thursday, 31-Mar-2022 13:56:54 UTC permalink
    • muesli (fribbledom@mastodon.social)'s status on Thursday, 31-Mar-2022 13:59:18 UTC muesli muesli
      in reply to
      • Sasha Sorokin 🏳‍🌈

      @sasha_sorokin

      That's a red flag for me.

      In conversation Thursday, 31-Mar-2022 13:59:18 UTC permalink
    • muesli (fribbledom@mastodon.social)'s status on Thursday, 31-Mar-2022 17:27:46 UTC muesli muesli
      in reply to
      • allo

      @allo

      Yeah, that kind of bot is a red flag for me.

      In conversation Thursday, 31-Mar-2022 17:27:46 UTC permalink
    • allo (allo@chaos.social)'s status on Thursday, 31-Mar-2022 17:27:48 UTC allo allo
      in reply to
      • muesli

      @fribbledom counterpoint: "Bug Bot closed the issue due to inactivity"

      A bug doesn't vanish, just because nobody added something to the bugreport. Still, some projects think it's a good idea to automatically close tickets.

      In conversation Thursday, 31-Mar-2022 17:27:48 UTC permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • Privacy
  • Source
  • Version
  • Contact

Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.