public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Items for Council Agenda, May 14
Date: Thu, 11 May 2017 16:24:05 -0400	[thread overview]
Message-ID: <assp.03044c09a1.20170511162405.7234398d@o-sinc.com> (raw)
In-Reply-To: <CAGfcS_k3PQu49PA4JCuTrSjEkorDcZRqogxeuTYb5GcsPS+i4A@mail.gmail.com>

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

On Thu, 11 May 2017 15:57:52 -0400
Rich Freeman <rich0@gentoo.org> wrote:
>  We don't want people to avoid us.

I myself have been there and done that. I left for many years.
Very few things if anything  improved. I was even accused of not doing
more over those years. Despite how people handicap my ability to
contribute. Which I stopped some time ago.

My recent activity on Github was simply trying to address
contributors that Gentoo Developers were ignoring...

This person ignored for 11 months. Does this guy sound happy? Did
anyone other than me reply to address his concerns?
https://github.com/gentoo/gentoo/pull/1721#issuecomment-300155991

Good reason for me to be blocked from Github right? What does that say
to that guy? I had NOTHING to do with Gentoo Devs ignoring that pull
request.

Why is this one still open? Mgorny has superior skills to my pathetic
ones. Why does he not merge that request? Why has Chewi not?
Anyone even talking to the contributor?
https://github.com/gentoo/gentoo/pull/1358

While that pull request addresses a number of Tomcat bugs. There are
still many more Tomcat related bugs people are reporting.
https://bugs.gentoo.org/buglist.cgi?quicksearch=tomcat&list_id=3530490

What about this guy? Did anyone reach out to him?
He showed in IRC as well....
http://marc.info/?l=gentoo-dev&m=149194941632740&w=2

Those are just a few and all 3 have NOTHING to do with me. That is
Gentoo Developers neglecting their own contributors. Upsetting them and
driving them away. Do you think any of them will contribute more?

I feel bad for all three.... They were not treated right!

>  If  somebody looks at our list archives and see lots of flames, they
> may be discouraged from participating.

Rarely will chaos drive someone away from a superior product and
offering. More so if one is technically superior to another. If such
does they then were not interested in the technical aspects or did not
consider them superior.

Why do I still run Gentoo after how I am treated and seen? For
technical reasons clearly not social.

>  If somebody posts a bug and  somebody replies saying that xyz on
> Gentoo is dead and that you'd be better off on another distro,
> they'll probably take that advice ensuring xyz remains dead.  Etc.

Or when the bug and/or fix for said issue goes ignored for a very long
time. It shows that the Distro is being neglected. That alone will
drive people away. Even if a package is alive, it can be dead on a
given distro.

> It is a bit of "we will not hide problems" vs "not hiding problems
> actually causes those problems."  Suicide by social contract?

People are intuitive and can see problems hidden or not.

Gentoo Developers and people within are creating FAR more problems than
anyone on the outside.... There are 3 clear examples above. Where is
the clear example of say my actions driving another away? Any evidence?

-- 
William L. Thomson Jr.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-05-11 20:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 17:00 [gentoo-project] Items for Council Agenda, May 14 Anthony G. Basile
2017-04-30 13:52 ` Andreas K. Huettel
2017-05-03 21:26   ` Daniel Campbell
2017-05-06 14:34 ` arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) Andreas K. Huettel
2017-05-06 16:35   ` [gentoo-dev] " Michał Górny
2017-05-06 17:36     ` Andreas K. Huettel
2017-05-06 20:23       ` Michał Górny
2017-05-07  2:53         ` Kent Fredric
2017-05-07 20:30       ` Michał Górny
2017-05-08 11:46         ` Andreas K. Huettel
2017-05-13  0:03     ` Andreas K. Huettel
2017-05-13  7:44       ` Michał Górny
2017-05-13 22:48         ` Andreas K. Huettel
2017-05-07 15:47   ` Roy Bamford
2017-05-14 15:38     ` Andreas K. Huettel
2017-05-11  7:17 ` [gentoo-project] Items for Council Agenda, May 14 Matthias Maier
2017-05-11  7:52   ` NP-Hardass
2017-05-11  8:02     ` Michał Górny
2017-05-11  9:16       ` Raymond Jennings
2017-05-11 10:08   ` Kent Fredric
2017-05-11 10:52     ` Rich Freeman
2017-05-11 15:03       ` Gregory Woodbury
2017-05-11 16:45   ` Luis Ressel
2017-05-11 19:57     ` Rich Freeman
2017-05-11 20:24       ` William L. Thomson Jr. [this message]
2017-05-11 20:28       ` Michał Górny
2017-05-13  9:26       ` Kent Fredric
2017-05-14  1:46         ` M. J. Everitt
2017-05-11 18:55   ` Roy Bamford
2017-05-11 19:09     ` Raymond Jennings
2017-05-11 19:54       ` Rich Freeman
2017-05-13  9:14       ` Kent Fredric
2017-05-11 20:25   ` William L. Thomson Jr.
2017-05-11 23:07   ` Daniel Campbell
2017-05-12  8:52     ` Roy Bamford
2017-05-12 10:41       ` Andreas K. Huettel
2017-05-13  9:36         ` Daniel Campbell

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=assp.03044c09a1.20170511162405.7234398d@o-sinc.com \
    --to=wlt-ml@o-sinc.com \
    --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