Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Nate Graham
On Tue, 18 Sep 2018 13:23:19 -0700 Albert Astals Cid wrote > El dilluns, 17 de setembre de 2018, a les 20:01:15 CEST, Andrew Crouthamel > va escriure: > Unless we can check if there has been no comment after the comment that > changed the status to NEEDSINFO, it that's

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Nate Graham
On Tue, 18 Sep 2018 13:23:19 -0700 Albert Astals Cid wrote > El dilluns, 17 de setembre de 2018, a les 20:01:15 CEST, Andrew Crouthamel > va escriure: > Unless we can check if there has been no comment after the comment that > changed the status to NEEDSINFO, it that's

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Albert Astals Cid
El dilluns, 17 de setembre de 2018, a les 20:01:15 CEST, Andrew Crouthamel va escriure: > 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

Re: How to become a distribution?

2018-09-18 Thread A. Wilcox
On 09/12/18 18:23, Ben Cooksley wrote: > On Thu, Sep 13, 2018 at 11:19 AM Nate Graham wrote: >> >> + kde-community for greater visibility > > Hi Nate, > > Just wondering why you forwarded this when I responded to A. on the > same day he sent this? http://foxkit.us/ My pronoun is

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Nate Graham
Thanks for taking the initiative on this, Andrew. I think everything you've laid out makes sense, and I like those messages. +1. Nate On Tue, 18 Sep 2018 12:56:09 -0700 Andrew Crouthamel wrote > Thanks Harald, > > I've spoken with buovjaga and x1sc0 regarding their

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Andrew Crouthamel
Thanks Harald, I've spoken with buovjaga and x1sc0 regarding their LibreOffice QA procedures: https://wiki.documentfoundation.org/QA/Bugzilla/Gardening#Task:_Cleaning-out_NEEDINFO Linked there are some scripts that are run either automated or manually. The NEEDSINFO one is manual right now.

Re: pseudonymous contributions to KDE

2018-09-18 Thread Adriaan de Groot
Based on memory, not actual policy: On Tuesday, 18 September 2018 19:38:35 CEST Jos van den Oever wrote: > What is the KDE policy on accepting code contributions under pseudonym? I've > gotten review requests on Rust Qt Binding Generator under a pseudonym. Now > I wonder if I can accept the

pseudonymous contributions to KDE

2018-09-18 Thread Jos van den Oever
Hi all, What is the KDE policy on accepting code contributions under pseudonym? I've gotten review requests on Rust Qt Binding Generator under a pseudonym. Now I wonder if I can accept the contribution. The contributor has, under pseudonym, a KDE account. Can one sign a Fiduciary License

Re: New KDE.ru website

2018-09-18 Thread Adriaan de Groot
On Tuesday, 18 September 2018 17:39:37 CEST Ilya Bizyaev wrote: > Today the Russian-speaking KDE community proudly launches its updated > website, KDE.ru. Вот очен хорошо! And so, having exhausted all the Russian I can produce at the drop-of-a-hat, congratulations on having created a slick and

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Ilmari Lauhakangas
Ilmari Lauhakangas kirjoitti 18.9.2018 klo 14.13: Harald Sitter kirjoitti 18.9.2018 klo 13.40: Anywayyy... I can throw together some automation so long as someone tells me what exactly the process should be :P Wait a bit as I have just been in contact with Andrew about re-using the

New KDE.ru website

2018-09-18 Thread Ilya Bizyaev
Today the Russian-speaking KDE community proudly launches its updated website, KDE.ru. The new website serves as the main page for the Russian-speaking community. It provides localized information about KDE, product download links and the list of social network pages we maintain. It is also

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Luigi Toscano
Harald Sitter ha scritto: On Tue, Sep 18, 2018 at 12:59 PM Boudewijn Rempt wrote: Would it also be possible to automatically remove the needinfo status if the reporter adds a comment after it's set to needinfo? Yes. I know that this proposal was rejected in the past, but if the needinfo

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Harald Sitter
On Tue, Sep 18, 2018 at 12:59 PM Boudewijn Rempt wrote: > > Would it also be possible to automatically remove the needinfo status if the > reporter adds a comment after it's set to needinfo? Yes.

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Ilmari Lauhakangas
Harald Sitter kirjoitti 18.9.2018 klo 13.40: Anywayyy... I can throw together some automation so long as someone tells me what exactly the process should be :P Wait a bit as I have just been in contact with Andrew about re-using the automation LibreOffice already has for this. I need to ask

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread David Edmundson
> One of the areas I've found that could use improvement IMHO it's really not a huge problem*. If a reporter doesn't answer back, then they clearly don't care. If its marked as needsinfo it's not in my lists, it doesn't affect me as a dev in the slightest. They're filtered out by default, I have

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Boudewijn Rempt
Would it also be possible to automatically remove the needinfo status if the reporter adds a comment after it's set to needinfo? On dinsdag 18 september 2018 12:40:09 CEST Harald Sitter wrote: > On Mon, Sep 17, 2018 at 8:25 PM Nate Graham wrote: > > +1, in favor, especially if we can close them

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Harald Sitter
On Mon, Sep 17, 2018 at 8:25 PM Nate Graham wrote: > +1, in favor, especially if we can close them in an automated fashion. > Closing bugs isn't as frustrating for filers as it used to be anyway, since > if they ever show up again with new information, they can just re-open them. Should be

Re: Public report of the Community Working Group

2018-09-18 Thread Jonathan Riddell
On Sat, 11 Aug 2018 at 16:53, Valorie Zimmerman wrote: > * Case: conflict between Plasma release manager and Promo team in > public (KDE Community list) > Outcome: Open This has now been resolved and the team has reverted back to it's previous state as a community team where all can play a full