#bookbrainz

/

      • yvanzo
        BinyaminGreen[m]: you can sign up for Jira using your GitHub account.
      • BrainzGit joined the channel
      • reosarevok
        And for discussion, we can use IRC :)
      • CatQuest
        ya
      • Mr_Monkey
        BenOckmore: That whole writeToDisk was basically a hack that theoretically shouldn't be needed. I tried removing it completely and it seems to work on Webpack 5 for me. Will check again in case I missed something.
      • BinyaminGreen[m] has quit
      • BinyaminGreen[m] joined the channel
      • Yes, I can confirm the HMR middleware is working fine without the need to write the files. It's the same reason we don't need that `WriteAssetsWebpackPlugin` anymore.
      • BinyaminGreen[m]
        reosarevok: I don't want to move the discussions. Just open up something on GitHub, as well. Is there a danger to using GH discussions?
      • meaning, opening up discussions on github, with the intent that this is just for passersby.
      • reosarevok
        Generally, having discussions in several places means many people only ever see half of it :)
      • That's the main worry
      • (we used to have forums and mailing lists, for example, and ended up in a situation where we had "forum people" and "list people")
      • (for MusicBrainz, that is, BookBrainz never had mailing lists)
      • BinyaminGreen[m]
        Oh, wait! You can customize the issues tab. I think you can make it so that you can only click on external links. That would make me very happy.
      • reosarevok
        For discussion we have IRC for live talk and https://community.metabrainz.org/ for forum stuff :)
      • (that one does require an account, but it's the same account as BB itself, so)
      • BinyaminGreen[m]
        I meant that you wouldn't be able to open an actual issue.
      • reosarevok
        Oh, so just saying "Hi! To report issues, please go to our Jira tracker (link). You can log in with your Github account there!" ? :)
      • BinyaminGreen[m]
        Yep. https://github.com/b3u/issues-testing/
      • shivam-kapila
        this looks good
      • BinyaminGreen[m]
        it still works if you go directly to "/issues/new", but a GitHub action could deal with that. Lock them, direct the user to Jira, etc.
      • go to https://github.com/b3u/issues-testing/issues/new/, and try to open an issue
      • Mr_Monkey
        BinyaminGreen[m]: I'm not sure exactly what that achieves, other than creating another discussion medium. Coudl you explain the benefits you see with having those auto-closing issues?
      • There is a link in the readme pointing to the jira issue tracker; maybe if that link was much more visible and at the top it would make it clearer that issues are tracked through jira?
      • yvanzo
        BinyaminGreen[m]: Last time I looked at it (a long time ago), it was not possible to redirect the issues to an external tracker. I think we would be happy to make clearer that issues can be openly created/read/self-assigned through the Issues tab even though it is already documented in most README files (as Mr_Monkey just mentioned).
      • Mr_Monkey
        I think it can definitely be made a lot clearer. I'll touch up the project readme accordingly, at the very least