#qtox.ml.log

<zetok> Impyy, nurupo: can Tox provide ML(s) for qTox?
<nurupo> zetok: yeah, it's possible to create a mailing list for qtox, we would just need to discusss this during our committee meetings
<nurupo> zetok: but first i would need you to define the use scope of the mailing list
<nurupo> is it for qTox users to ask for support, is it for qTox developers to discuss qTox development, is it just for qTox committe things, or is it something else entirely?
<nurupo> do you want the ml to be public/private, allow people to freely subscribe to it (anyone could registed and write to it), or you want only approved people to be able to write to it
<nurupo> etc.
<zetok> nurupo: well, for support there's a ML already; as for qTox ML – public (rw) for anyone to write, for ~discussion etc related to qTox
<zetok> I mean, if there'd be more people using ML it would be preferable to have `qTox announcements` ML for only qTox maintainers to post on, + qTox general for everyone to post on
<zetok> but I think that qTox general alone will do for now
<zetok> nurupo: oh, and generally `Announcements` ML should be added – with right to write to for all maintainers of projects in Tox ecosystem

= days later =

<nurupo> oh, tux3 is here
<tux3> nurupo, hi
<nurupo> was just writing email to you
<nurupo> will copy-paste it in here instead then
<nurupo> >Hi there, So, zetok has asked us to make a mailing list dedicated solely to qTox at lists.tox.chat (https://lists.tox.chat). 
<nurupo> >I have asked him about the scope of the ml, because it sounds like qTox ml would overlap with the Support ml and Development ml. As a user having issues with qTox and seeing Support and qTox mls, it would be very confusing which one to use, so the qTox ml should have some distinctive scope, such that it could be named qTox-<foo> ml. All I could get out of zetok was that the qTox ml should be for general discussion, which isn't very specific (https://gist.github.com/nurupo/bf2cf7fe51885115b9b6b7d9a36478a7). I mean, it could work, we have to discuss it, but there is some obvious overlap with other mls. So, I was just wonderting if you happen to have any input on that.
<nurupo> tux3: here ^
<zetok> nurupo: "a general ML for qTox that users of other clients may consider a spam"
<tux3> nurupo, As I understood it the qtox ML wasn't mainly for providing support, so users should still go to the Support ML. The qTox ML could be renamed qTox-dev to avoid confusion I suppose

= an hour later =

<nurupo> zetok: so, you are fine with tux3's decision of qTox-dev mailing list?
<zetok> nurupo: dunno, I don't want to make this list feel exclusive to people
<zetok> and naming it -dev would make it so
<nurupo> zetok: well, then maybe you should talk about the mailing list among the qTox committee members and come to some conclusion, if there is uncertainty
<zetok> tux3: ↑ ?
<zetok> DaSpirit: ↑ ?
<nurupo> i will be bringing up the qTox ml during our meetings as qTox-dev, unless you want me to postpond brining it up until you got it sorted out
<tux3> Imho call it qTox-dev and be done with it, it's not the one for user support, and if people just want to chat about their life, they can go on IRC
<tux3> We'll be using this ML for qTox development/meetings so it fits
<zetok> hm
<zetok> ok
<zetok> nurupo: yeah, that's fine with me