Fedora Present and Future: a Fedora.next 2014 Update (Part I, "Why?")

[Patrick O'Callaghan]

On Mon, 2014-03-24 at 14:36 +0000, Liam Proven wrote:
> On 24 March 2014 01:33, Patrick O'Callaghan <pocallaghan at gmail.com> wrote:
> > On Sun, 2014-03-23 at 18:24 +0000, Liam Proven wrote:
> >> On 22 March 2014 18:25, Ed Greshko <ed.greshko at greshko.com> wrote:
> >> > Make sure you file a bugzilla.
> >>
> >> How/why? It's not a bug.
> >
> > If it doesn't work as it's supposed to, it's a bug.
> 
> An intentional design feature that causes a problem in an unexpected
> or unconsidered use-case is not what I'd call a bug, but hey, have it
> your own way. :-)

I think you're reaching if you *don't* think that's a bug. It's not a
question of me having my own way, but of following the usage on this
list.

> >> > Talking about it on this list will not result in any action.
> >>
> >> Won't it? Why not? Are there multiple non-overlapping user communities
> >> for Fedora, then? A problem is a problem; where it is reported
> >> shouldn't matter, should it?
> >
> > Seriously? Yes, there are multiple partially-overlapping communities.
> 
> Yes seriously. I'm new here. I have no idea who does or does not read this.

Fine, then take on board the fact that the Users list is for discussing
the current and previous release of Fedora, and naturally that includes
the problems people have with it, but if the outcome of a discussion is
to identify a bug it's not enough to just leave it at that. To not have
it forgotten about then you need to use Bugzilla.

> > Many of the developers don't read this list. Many of the people on this
> > list don't read the Test list. If you want to document a bug then use
> > Bugzilla.
> 
> As I have said, I don't think that I /can/ document it well enough to
> be of any use.

"Document" simply means "describe with as much detail as possible".

poc