On onsdag 5. september 2018 04.28.05 CEST Andrew Crouthamel wrote:
> Hello,
>
> As part of the "Streamlined onboarding of new contributors" goal from 2017
> (https://phabricator.kde.org/T7116), Nate, myself, Julian, and others have
> been working on ways to clean up Bugzilla, as well as the bug re
I'm fine with this as well.
On woensdag 5 september 2018 04:28:05 CEST Andrew Crouthamel wrote:
> Hello,
>
> As part of the "Streamlined onboarding of new contributors" goal from 2017
> (https://phabricator.kde.org/T7116), Nate, myself, Julian, and others have
> been working on ways to clean up B
New/confirmed are more about before/after triage than focussing on
reproducible or not.
Reproducible or not isn't really a particularly useful thing to know from a
dev side. I regularly fix things I can't immediately reproduce. If we want
that information a flag solves it better.
What's important
Andrew Crouthamel kirjoitti 5.9.2018 klo 5.28:
d. If bug is not fixable due to technical limitations, or expected
behavior, set to RESOLVED + ASDESIGNED.
WONTFIX is also typically used to refuse to implement features that are
out of scope or not aligned with a product vision. Just wanted
On 09/04/2018 10:01 PM, Christoph Feck wrote:
I still oppose to name a status NEW (again). It only attracts "how is
this NEW? this is already [random timespan here] OLD!" comments.
There will always be products/components that have no active maintainer
to look for bugs in a limited timeframe.
On 05.09.2018 04:28, Andrew Crouthamel wrote:
Hello,
As part of the "Streamlined onboarding of new contributors" goal from 2017
(https://phabricator.kde.org/T7116), Nate, myself, Julian, and others have been working on ways to
clean up Bugzilla, as well as the bug reporting and triaging system
+1 from me, needless to say. :)
Nate
On 09/04/2018 08:28 PM, Andrew Crouthamel wrote:
Hello,
As part of the "Streamlined onboarding of new contributors" goal from
2017 (https://phabricator.kde.org/T7116), Nate, myself, Julian, and
others have been working on ways to clean up Bugzilla, as w
Hello,
As part of the "Streamlined onboarding of new contributors" goal from 2017
(https://phabricator.kde.org/T7116), Nate, myself, Julian, and others have been
working on ways to clean up Bugzilla, as well as the bug reporting and triaging
system in the "Improvements to Bugzilla - Making it e
Hello sysadmin!
In https://phabricator.kde.org/T6832, we seemed to reach general
agreement that products closed to new bugs shouldn't appear on the
Browse page in bugzilla (https://bugs.kde.org/describecomponents.cgi).
Is this a feasible change to make?
Thanks,
Nate
On 2018-09-04, Eike Hein wrote:
> In the debrief, I think we were quite happy with how things went and
> concluded if we get another chance, we'd try to do it again. The Qt
> Company feels the same way, as they've reached out and offered similar
> accomodations for this year as well.
I think we s
Hi Eike
I want to be there, i miss last time event and should not miss this one.
[]'s
On Tue, 4 Sep 2018 at 11:32, Eike Hein wrote:
>
> Hi,
>
> Qt World Summit 2018 is coming soon - this year it'll be a
> smaller-scale, single-day event. Again in the bcc in Berlin, on December
> 6th.
>
> Last
Hi,
Qt World Summit 2018 is coming soon - this year it'll be a
smaller-scale, single-day event. Again in the bcc in Berlin, on December
6th.
Last year we managed to significantly raise the bar of KDE's presence at
the event, with a coordinated visual theme backed by assets such as crew
shirts,
12 matches
Mail list logo
