Default new bug state to UNCONFIRMED (split from Use of CLOSED in Bugzilla)

[David Edmundson]

>What also needs to change is the fact that all developers
>automatically have their submitted bugs marked as NEW, even if they
>are not necessarily involved with that particular project and might
>simply not have a clue if their bug report is complete. That is
>reported here:

>https://bugs.kde.org/show_bug.cgi?id=183217

Any bug that has sat there since 2009 will continue to stay unchanged
until someone kicks it into action again.
We don't need the bugzilla 4 workflow to make this happen, nor do we
_need_ the wording to change.

We do, however, need some action not just talk on our ML.
If I was a sys-admin I wouldn't make a change that affected everyone
on KDE on the basis of one comment from a single person.

A very brief look/google showed the actual change is a simple single
line change in bugzilla code.

I suggest we:
 - make a list of people who support this change
 - write a proposal of why this change is the correct thing to do.
Benefits/drawbacks
 - write a RFC to kde-core-devel
 - chase the inevitable conclusion up.

Any volunteers for any of this? If not I'll start drafting something next week.

Dave