[bisq-network/bisq] Trying out GitHub Discussions (#5163)

[chimp1984]

I think the feature is getting used already and seems to have been accepted by the contributors. 
I am wondering if there is a tool / way to limit noise. A general problem not only at Bisq is that too much content gets produced and it becomes difficult to find the valuable out of the noise, and of course everyone will have a different opinion about that. Twitter does it well with making each user his own "censor"/filter by following those who have built up reputation from the users perspective. 
I never really used the "Follow" feature in Github and I assume that is not the right solution here.

One option could be that we use a moderator who closes discussions when they reach a certain number of down-votes from contributors who have earned some reputation. We could use the DAO merits but that is not accessible here, but I think the moderator would know which contributors are around the project since long and have earned some considerable amount of BSQ by adding value to Bisq. Is not a perfect solution and makes the moderator a problematic role, but Github is not decentralized anyway, mergeing code is also based on similar reputation based authority. But it would help to keep the Discussions panel clean and new potential contributors don't get lost in noise and get a bad impression of low-quality input/discussions.
I see this a real problem in all our channels. GH issues are a mess, proposals are better but still too polluted and I think the same will happen here. Maybe we can make it a time-limited experiment to choose one moderator who is responsible to keep the panel clean. I would avoid to define too much formal rules here, as those can always be circumverted and do not serve as quality filter (see past projects, where some followed the formal requirements but content was pretty poor and has shown lack of understanding of how Bisq works). I think a reputation based approach is more effective.  
Just my 5 cents, not 100% clear idea how to get the solved best...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5163#discussioncomment-357116
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210210/420201e3/attachment.htm>