GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Admiral Snackbär (admsnackbar@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:09 JST Admiral Snackbär Admiral Snackbär
    in reply to
    • Jeff Geerling
    • darix

    @darix @geerlingguy

    That's why you should have some sort of "work in progress" flag/tag/state. There's a difference between an issue being worked on without being updated and an issue being ignored/not worked on.

    Ideally, you'd put the issue id in the commit message, so it's clear what's going on.

    But I have to admit, splitting discussing an issue and working on an issue into two different places is not ideal.

    In conversation about 7 days ago from mastodon.social permalink
    • Embed this notice
      Jeff Geerling (geerlingguy@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:09 JST Jeff Geerling Jeff Geerling
      in reply to
      • darix

      @AdmSnackbar @darix my stale bot configuration has a pass for bug and "planned" labels.

      But I apply those labels sparingly. I don't close bugs, but I often close feature requests. The projects are first and foremost for me, if others benefit from my code that's great.

      In conversation about 7 days ago permalink
      Johnny Peligro likes this.
    • Embed this notice
      darix (darix@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:10 JST darix darix
      in reply to
      • Jeff Geerling

      @geerlingguy There is a distinct difference between a timeout based stale bot and saying no to an issue. With the former you ensure I will probably never contribute to your things again, with the latter I am still happy to help

      From a fellow opensource maintainer and contributor.

      In conversation about 7 days ago permalink
    • Embed this notice
      Jeff Geerling (geerlingguy@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:10 JST Jeff Geerling Jeff Geerling
      in reply to
      • darix

      @darix fine by me!

      I often post a PR to a project with zero expectations whatsoever.

      The only reason I post it is so (a) I can incorporate that into my own documentation or fork, and (b) so others who use the project can benefit.

      If anyone on the project ever decides to merge my code, that's just icing on the cake.

      In conversation about 7 days ago permalink
    • Embed this notice
      darix (darix@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:10 JST darix darix
      in reply to
      • Jeff Geerling

      @geerlingguy Naw. I will work happily with upstream to get the fixes in. provide more details if needed. so having to reopen something every X days because some stupid timer ran out is really a chore after a while.

      In conversation about 7 days ago permalink
    • Embed this notice
      Jeff Geerling (geerlingguy@mastodon.social)'s status on Tuesday, 13-May-2025 21:47:11 JST Jeff Geerling Jeff Geerling

      Pet peeve: People complaining about the way I maintain my open source projects under MIT license (particularly my decision to use stale bot, since I don't like seeing literal thousands of open issues across my repos).

      Just fork it! No skin off my back. https://www.jeffgeerling.com/blog/2022/just-say-no

      In conversation about 7 days ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: www.jeffgeerling.com
        Just Say No | Jeff Geerling

Feeds

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

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.