I've been spending a lot of time browsing, searching, and filtering our bugs in
Bugzilla. One of the areas I've found that could use improvement, are the
NEEDSINFO bugs. Often, bugs are placed into this status, either awaiting
additional information or backtraces, never to be updated again. We h
On Monday, 17 September 2018 20:01:15 CEST Andrew Crouthamel wrote:
> This is already a policy at many other projects such as The Document
> Foundation, Chromium, and Fedora. Additionally, several of our developers
> within KDE are already doing this.
This depends on the state change *to* NEEDSINF
On Mon, 17 Sep 2018 11:19:59 -0700 Adriaan de Groot wrote
> This depends on the state change *to* NEEDSINFO having a comment or other
> message that is sufficiently directive: "we need in order to
> do
> anything with this bug". Or, in general, we'd need to keep in mind th
Can Bugzilla be configured to add boilerplate to the email that goes out
with a NEEDSINFO that reads "This bug report will be closed after 30
days unless blah blah blah"?
At worst case, we could edit bug/create/user-message.html.tmpl which is the
text that shows at the top of the bug creation page.
Andrew Crouthamel
‐‐‐ Original Message ‐‐‐
On Monday, September 17, 2018 2:38 PM, Scott Harvey wrote:
> Can Bugzilla be configured to add boilerplate to the
I would definitely have a warning message posted when this is about to
happen. I have no objection as.long is clear what information is needed. I
would be inclined to do this manually even if the system doesn't.
On Mon, Sep 17, 2018, 2:39 PM Scott Harvey wrote:
> Can Bugzilla be configured to ad
No problem, I can make that part of the procedure until we figure out an
automated method. After two weeks, send out a reminder, then two weeks later
close if no activity.
Andrew Crouthamel
‐‐‐ Original Message ‐‐‐
On Monday, September 17, 2018 3:10 PM, Michael Reeves
wrote:
> I woul
Hi everyone,
there popped up an interview with Linus and one question was how to
successfully run an open source project and build a sustainable community.
The answer boils down to "being responsive", i.e. answer mails/review
requests/... quickly.
You can watch the video yourself:
https://video.g
