On Mon, 1 Jun 2020 12:09:36 -0500, Roger Heflin wrote:
When the policy is not being followed and/or not enforced it means
nothing. Only someone who is in love with
the policy would say otherwise and actively defend it.
You're still not getting it.
I am going to guess you helped write large parts of the policy
and that is why you defined it.
Yes, lets enforce the policy against
the everyone until you have no community.
See above. You're not getting it. You talk about "enforcing" something,
you preach stagnation. That isn't helpful and not a way forward for Fedora.
Since there are packages going unmaintained it not like they are
It is you as a "insider"
that seems to be denying the "perfect" policy is not functioning as
often as you like and not admitting that it can
be made to work with the staff you had. If the maintainer for the
kernel package is not following it,
I doubt many are following it.
Please stop guessing. It can't generalized like that. Quite obviously,
there are _many_ packages that are much easier to maintain than the kernel
package (with its ticket linked earlier in this thread). There are
different aspects of maintenance. Handling bug reports is just one of many
And while you are calling me an outsider, I have been using what
became fedora for years before the first fedora
version was released, and have been using it almost every version since then.
The question about your "background" was necessary because it becomes
apparent that you comment on things as one who either doesn't know how
things work at the Fedora Project (or how things are supposed to work) or
you deliberately ignore it. You don't seem to care about project policies
and guidelines, and you brush aside what's there as a base. You even ignore
what different levels of maintenance are needed for different packages.
On the fedora side we should probably be directing anyone with
software bugs to upstream.
Should? Probably? And you expect upstream to not be understaffed,
especially not if being flooded with bug reports which may be
Don't get me started about [...]
Thread is closed for me.