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.
"There's no reason to ever have anything non-open in your FOSS project's infrastructure."
Except, that it is easier to set up? What you describe sounds reasonable. But someone needs to set all that up and host it and needs to be trusted etc.
So I guess if many people get involved and do set this up, they would convince the rest of the team to join them. But right now it is just a demand for more work for them.
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.
If I had a serious interest in the project (more than, say, maybe sending a patch here and there to fix my pet peeve), I would definitely volunteer for something like that if there was a demand. That's something I quite enjoy, and am reasonably good at, I think.
And as for me being there for years to come, who can say that for sure? I would absolutely try to. For that matter, will Discord still be here next year?
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.
"There's no reason to ever have anything non-open in your FOSS project's infrastructure."
Except, that it is easier to set up? What you describe sounds reasonable. But someone needs to set all that up and host it and needs to be trusted etc.
So I guess if many people get involved and do set this up, they would convince the rest of the team to join them. But right now it is just a demand for more work for them.
2 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.
If I had a serious interest in the project (more than, say, maybe sending a patch here and there to fix my pet peeve), I would definitely volunteer for something like that if there was a demand. That's something I quite enjoy, and am reasonably good at, I think.
And as for me being there for years to come, who can say that for sure? I would absolutely try to. For that matter, will Discord still be here next year?
5 replies →