public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Deferred decision: Forums (specifically OTW)
Date: Wed, 12 Jun 2019 02:42:11 -0700	[thread overview]
Message-ID: <CAAr7Pr8x59YwoZ3aKvLaYcxsCu8_w07RNJWeaJDyf_c65npkkQ@mail.gmail.com> (raw)
In-Reply-To: <b40a953c0eef63fcbb1eb7bf59806992b56b4b78.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 3348 bytes --]

On Tue, Jun 11, 2019 at 8:38 PM Michał Górny <mgorny@gentoo.org> wrote:

> On Tue, 2019-06-04 at 15:05 +0200, Kristian Fiskerstrand wrote:
> > The agenda item "Forums (specifically OTW)" was deferred to further
> > discussion in the mailing lists during the 2019-02-10 council meeting.
> > The agenda for that meeting can be found at [Agenda] and the tracking
> > bug is [Bug 677824].
> >
> > This email aims to re-opens the discussion [which was started in a
> > previous thread] as per the council decision.
> >
> > I ask that the discussion remains civil and respectful, while also
> > allowing for a high bar for the actual discussion.
> >
>
> I don't think OTW is a major problem.  The real problem are *technical*
> forums, and those cause two problems.  The first of them is that
> developers rarely hear of the problems with their packages.  The second
> of them is that Forums tend to breed very bad 'solutions'.
>

I'm curious how this is different from other support forums. Are there no
bad solutions proposed on the wiki? in #gentoo? In other channels?

-A


>
> I don't mind providing multiple support channels as long as problems
> actually reach developers.  However, I don't think it's news to most of
> the developers who don't actively participate in Forums (read: look
> for new threads everywhere) that some problems never leave them.
>
> During my years in Gentoo I've been pinged a few times over expansive
> Forum threads on problems with my packages which never made it to
> Bugzilla or anything else that I actually could've noticed.  It all
> relies on courtesy of accidental developers (who are not Forum
> moderators, I should add).  I can only imagine how many problems were
> never addressed properly because the maintainer never learned of them,
> and cheap hacks proposed on Forums were sufficient for the users.
>
> And no, I don't think that requiring every developer to directly follow
> all Forum feeds is a solution.
>
> A side effect of the former problem is that Forums are home to many
> horrible 'solutions'.  Sadly, those solutions sometimes involve making
> things *much worse* than they were before.  This is problem both for
> users who end up victims of having their systems broken, and developers
> who end up having to help fix the resulting breakage.
>
> Breakage resulting from use of dev-python/pip is the most prominent
> example I know of.  Multiple Forum victims ended up using it to 'fix'
> problems.  As a result, they ended up with obsolete directly installed
> packages overriding Gentoo packages and breaking stuff.  The scale of
> this was so great that I had to actually patch dev-python/pip to block
> installing packages system-wide.  Which is a technical hack to a social
> problem.
>
> I'm not saying Forums is the only source of the problem, people can
> figure out how to break systems themselves.  However, Forums is
> frequently a source of bad information that is mistakenly trusted
> and is not properly verified and rejected.
>
> To summarize, I think the two major problems with the Forums are:
> 1) not passing information properly to package maintainers,
> and 2) lack of proper Q/A.  If you can solve them, I don't have any
> problem with the Forums.


> --
> Best regards,
> Michał Górny
>
>

[-- Attachment #2: Type: text/html, Size: 4224 bytes --]

  reply	other threads:[~2019-06-12  9:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 13:05 [gentoo-project] Deferred decision: Forums (specifically OTW) Kristian Fiskerstrand
2019-06-04 13:15 ` Dirkjan Ochtman
2019-06-04 13:30   ` Kristian Fiskerstrand
2019-06-06  4:39     ` desultory
2019-06-12 10:04     ` Alec Warner
2019-06-12 11:13       ` Rich Freeman
2019-06-12 13:00         ` Alec Warner
2019-06-12 14:09           ` Rich Freeman
2019-06-13  2:36             ` Alec Warner
2019-06-15  3:53               ` desultory
2019-06-15 11:17                 ` Rich Freeman
2019-06-15 11:20                   ` Michael Everitt
2019-06-16  4:52                   ` desultory
2019-06-16 10:36                     ` [gentoo-project] Various IRC Discussions (was Deferred decision: Forums) Rich Freeman
2019-06-17  3:03                       ` desultory
2019-06-15 16:39                 ` [gentoo-project] Deferred decision: Forums (specifically OTW) Raymond Jennings
2019-06-12  3:38 ` Michał Górny
2019-06-12  9:42   ` Alec Warner [this message]
2019-06-12 12:16     ` Michał Górny
2019-06-12 12:32       ` Rich Freeman
2019-06-12 13:40   ` Jimi Huotari
2019-06-14 16:04 ` [gentoo-project] " Kristian Fiskerstrand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAr7Pr8x59YwoZ3aKvLaYcxsCu8_w07RNJWeaJDyf_c65npkkQ@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox