IRC. And for slow discussions with long messages, you can use NNTP.
(However, GitHub is accessible by git in case you only want to download the repository, regardless of what else they do; however, having multiple mirrors on other services as well can be helpful)
Better but a the real alternative is what we had before: publicly visible forums, mailing lists with an archive, etc. I'm not going to sign up for your discussion group without being able to get a feel for the community first.
Indeed. There can never be just one platform for project communication, because there are different kinds of communication - mostly sorted between synchronous and asynchronous.
So, IRC, Matrix (these can even be interconnected) for synchronous, mailing lists or forums for asynchronous.
And of course issue tracker, where some topical communication can happen as well, but that could completely be covered by mailing lists.
There's no reason to ever have anything non-open in your FOSS project's infrastructure.
Would you volunteer in setting up a forum for ladybird and host it and can you convince Kling and co. that you will be around to host it for the next years to come?
Because that is a project in itself and as much as I despise discord, I understand why they just went with it.
IRC. And for slow discussions with long messages, you can use NNTP.
(However, GitHub is accessible by git in case you only want to download the repository, regardless of what else they do; however, having multiple mirrors on other services as well can be helpful)
While I’d love to agree: many people these days simply don’t want to use IRC.
You can bridge to matrix and use a matrix client. Then you get history even offline.
Matrix is a wonderful alternative
Better but a the real alternative is what we had before: publicly visible forums, mailing lists with an archive, etc. I'm not going to sign up for your discussion group without being able to get a feel for the community first.
Indeed. There can never be just one platform for project communication, because there are different kinds of communication - mostly sorted between synchronous and asynchronous.
So, IRC, Matrix (these can even be interconnected) for synchronous, mailing lists or forums for asynchronous.
And of course issue tracker, where some topical communication can happen as well, but that could completely be covered by mailing lists.
There's no reason to ever have anything non-open in your FOSS project's infrastructure.
3 replies →
Would you volunteer in setting up a forum for ladybird and host it and can you convince Kling and co. that you will be around to host it for the next years to come?
Because that is a project in itself and as much as I despise discord, I understand why they just went with it.
6 replies →
discuss?