I am actually about to setup my own XMPP server. But I also think, an integrated way would be nice, and I can see, that we could create simply one 'discussion' issue, and talk on that.

Or simply one repo, that is called 'forums'

For discussion, just create issue of discussion type. Put in a separate repo will make search and linking harder

I am actually about to setup my own XMPP server. But I also think, an integrated way would be nice, and I can see, that we could create simply one 'discussion' issue, and talk on that.

Or simply one repo, that is called 'forums'

I was not speaking about creating more repositories. The issue currently is a lot of issues are being created, and the important ones are being outweighed with simple questions, which other community members could be able to solve without having to take time from Robin.

Also, you really do seem to be in there with trying to host as much as possible as quick as possible.

For discussion, just create issue of discussion type. Put in a separate repo will make search and linking harder

I was not speaking about diverting how to create issues, I was speaking about having a more relaxed community based conversation which does not need to be concise, designed to take the load off discussion issues and first seek support from community members before having to ask you the same questions over and over again.

It would also be useful for outreach, people are more likely to use something if they know there is a quick channel they can join to complain about all the issues they are encountering, just for you to tell them they forgot to open a port or something (Happens a lot, I am in a lot of other community channels for other software).

Yeah, I agree. I just like an integrated solution, something that is accessible within OneDev.

Yeah, I agree. I just like an integrated solution, something that is accessible within OneDev.

That would however defeat the purpose.

Within Onedev, you can always open a "Discussion" issue, which Robin will most likely to respond to when he finds time, but the issue is if people open too many Discussion issues to ask the same questions, or constantly asking for support in which the community might be able to give, it might waste time which could otherwise be saved, bare in mind Robin is a solo developer and probably does not have time to reply to 101 issues saying "It don't work" or "It broken" when some people are trying to host an instance, often there is a very simple fix which just asking another community member could have fixed.

It also provides more rapid support, some people within the community have a lot more time than Robin does and thus could respond with a solution much faster, and if the community cant help ,then there is still the discusssion issues which can be used to ask Robin for support.

Hope this makes sense :)

Discussions happen here does not prevent anyone from help, like already happen in many threads.

Also there is not too many discussions each day yet. No need to optimize too early.

It feels like you dislike making things easier for yourself. But its your choice.

If you don't want to make things easier for yourself maybe give me some hints on how to make the Arch Linux package better :)

---

This really confuses me. I don't have the ability to make your Arch Linux package better as I've mentioned again and again.

It feels like you dislike making things easier for yourself. But its your choice.

Discussing here actually make things easier for me:

1. I don't need to be bothered by chat messages from time to time.
2. All discussions here can be indexed and searched together with issues and other contents.

I explained this to you previously, and you still think that I am not going to take a easy way for discussion, 😕