The image is a large 8 so the whole thing needs changed. The background behind
the 8 image would be best to update but I don't suppose anyone is too fussed.
The 'Plasma 5.8 LTS' text is just text which is changed in a json file.
Jonathan
On Wed, Feb 28, 2018 at 10:59:52AM -0700, Andy Betts
On 28 February 2018 at 16:04, Ilmari Lauhakangas <
ilmari.lauhakan...@libreoffice.org> wrote:
> On 28.02.2018 16:21, Jaroslaw Staniek wrote:
>
>> My story is, more rules, more scared users ignore the BKO. A single thing
>> worth having is not too many rules but editing feature for *wrong* or
>>
Like I said. Are we ok if we just change the version number and keep the same
background?
Thank you,
Andy
On 2/28/2018 10:51:39 AM, Ben Cooksley wrote:
On Thu, Mar 1, 2018 at 5:17 AM, Andy Betts wrote:
> I was approached to work on a banner for the page, but I haven't had
On Thu, Mar 1, 2018 at 5:17 AM, Andy Betts wrote:
> I was approached to work on a banner for the page, but I haven't had the
> time to make anything. I think that maybe an easy change is to simply change
> the text to show the right version but maybe not change the
I was approached to work on a banner for the page, but I haven't had the time
to make anything. I think that maybe an easy change is to simply change the
text to show the right version but maybe not change the wallpaper behind it.
Bushan seemed to have access.
Thank you,
Andy
On 2/28/2018
I can do it for Plasma if nobody from VDG is available.
Ch
--
KDE, ivan.cu...@kde.org, http://cukic.co/
gpg key fingerprint: 292F 9B5C 5A1B 2A2F 9CF3 45DF C9C5 77AF 0A37 240A
It needs an artist to make a new 5.12 banner. Same for the slimbook.
Jonathan
On Wed, Feb 28, 2018 at 05:09:48PM +0100, Ivan Čukić wrote:
> Hi all,
>
> Can someone (who has the permissions to do so) update www.kde.org -
> the scrolling banner thingie shows Plasma 5.8 LTS instead of 5.12 LTS.
Hi all,
Can someone (who has the permissions to do so) update www.kde.org -
the scrolling banner thingie shows Plasma 5.8 LTS instead of 5.12 LTS.
Cheers,
Ivan
--
KDE, ivan.cu...@kde.org, http://cukic.co/
gpg key fingerprint: 292F 9B5C 5A1B 2A2F 9CF3 45DF C9C5 77AF 0A37 240A
On 28.02.2018 16:21, Jaroslaw Staniek wrote:
My story is, more rules, more scared users ignore the BKO. A single
thing worth having is not too many rules but editing feature for *wrong*
or outdated bug comments that make understanding the report so hard.
Many years have passed since the first
From experience, priority & severity are nice-to-haves most of the
time. In LibreOffice, they are the most useful in the case of crashes or
hangs, where we use high/highest & major/critical.
Ilmari
On 28.02.2018 16:25, Scott Harvey wrote:
As the former manager of an IT help desk (back in the
As the former manager of an IT help desk (back in the olden days), my input
on some of this. I'm only a junior developer who's offered up a few minor
patches thus far and have done a bit of bug triaging.
We need to back up and remember the definition of the word triage:
(in medical use) the
On 28 February 2018 at 12:35, Ilmari Lauhakangas <
ilmari.lauhakan...@libreoffice.org> wrote:
> I am personally convinced that users do not know bug triaging is a thing
> and certainly not how much they could help developers by doing it. It would
> be very useful to test this by running a poll on
I would argue this is not the most important thing, at least not before
recruiting a proper QA team for your application. It does help with
noticing duplicate reports, but it is quite work-intensive. In
LibreOffice we currently have 657 meta reports to categorise everything.
Yet, we also have
Hi,
Instead to start to talk with users about bugzilla, I recommend to separate
well the project with bugzilla sub-components.
In digiKam, i pass a lots of time to create sub-sections. This is the most
important task to do before triaging.
Remember that users are not developers. Some sections
I am personally convinced that users do not know bug triaging is a thing
and certainly not how much they could help developers by doing it. It
would be very useful to test this by running a poll on
https://blogs.kde.org/ or somewhere.
Questions could be something along the lines of
"Did you
On Wednesday, 28 February 2018 08:58:51 CET Ilmari Lauhakangas wrote:
> What you need to focus on right now is not bikeshedding about statuses
> etc., but to recruit more and more QA/triagers. The QA team is Martin's
> "second level support". This is the primary solution.
Yeah, I guess this is
On 28.02.2018 12:01, Luigi Toscano wrote:
On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote:
On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote:
On bugzilla.redhat.com some teams use the Triaged keyword. I think it
would
be a good solution.
I've been trying that,
On Wednesday, 28 February 2018 11:01:22 CET Luigi Toscano wrote:
> I disagree and I think it makes sense as keyword, as general attribute of
> the bug (something happened according a triaging process). It is a modifier
> of the "NEW"/initial state that is brought around later.
Yours is, of
On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote:
> On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote:
> > On bugzilla.redhat.com some teams use the Triaged keyword. I think it
> > would
> > be a good solution.
>
> I've been trying that, and it just doesn't work for
On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote:
> On bugzilla.redhat.com some teams use the Triaged keyword. I think it would
> be a good solution.
I've been trying that, and it just doesn't work for me, like I said in my
first mail to this thread. It doesn't work because it's
20 matches
Mail list logo