1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • They're saying the gitlab is now the slow way to IRC

    From Deucе@1:103/705 to GitLab issue in main/sbbs on Mon Feb 1 14:16:49 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/213

    I'm wondering if too much gitlab stuff is being pushed into #Synchronet... maybe a new #Synchronet-devel channel or something so Synchronet can be fore chats, but people who care can get the gitlab updates?The commits are still good to have in there I think, and *maybe* bug reports, but bug replies, code reviews, and other gitlab conversations seem to be a bit much.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 14:30:21 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1441

    I was thinking exactly the same thing when I was writing my last bug report. Of course, sometimes it's the only catch the attention of some devs ;) I don't mind them so much. If you don't want them, it's easy to block in the IRC client.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michael Long@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 15:24:32 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1442

    i think a separate channel isn't a bad idea
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 16:18:57 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1446

    I wouldn't want *all* the gitlab notifications to go to a separate channel (instead of #synchronet). I think it's helpful when someone initiates a bug report in #synchronet, that they also see any follow-up git activity notifications in #synchronet. Otherwise, we'll be frequently repeating "yeah, I/we fixed that right after you reported it, aren't you monitoring #synchronet-devel?"
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Deucе@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 16:28:28 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1448

    Well, as I said I think that commits being in #Synchronet are good to have, and possibly bug reports... it's the comments and code review stuff I think may be too verbose.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michael Long@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 16:37:55 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1449

    I think commits and merges to master are also good to have in main channel as it lets users know when to update and what may have changed or broken
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 18:24:49 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1450

    Okay, here's a comment just to see if it goes to #synchronet-devel (or not). --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 18:51:31 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1451

    Here's a comment that should go both to #synchronet-devel and #synchronet-gitlab
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Mon Feb 1 18:52:47 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/213#note_1452

    Try that again.
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Mon Feb 1 20:28:22 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/213
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)