Re: FOSDEM booth box
Take a pinebook too? It has always taken lots of conjoling to get people organised for fosdem nothing new there. Although I always prepared stuff for the stall it was often overlooked. And nobody wants to organise saturday evening until saturday evening comes and everyone asks what's happening. Jonathan On Thursday, 1 February 2018, Aleix Pol wrote: > On Wed, Jan 31, 2018 at 5:31 PM, Adriaan de Groot wrote: > > So, for the booth box, today I picked up: > > > > - duct tape 50m > > - steel cables, clamps, some kensington locks for tying stuff to the > table to > > discourage casual wandering-off > > - tie wraps, various lengths and sizes > > - i've got a 4x Schuko and a 3xSchuko + 4x narrow EU power block > > - 3 5V USB chargers, varying from 100ma to 10A > > > > I'll update the wiki. > > > > Note that: > > - we don't have t-shirts or much swag to sell. > > - i'll print up nametags for people who are on the wiki for booth-duty > > - i need to get some padlocks to lock the steel cables > > > > > > We don't have a "social experiment" lined up. Usually Lydia is the > creative > > one there. > > > > > > [ade] > > Brilliant! > I'll be bringing a KDE Slimbook and a Nexus 5X with Plasma to display! > > Aleix >
Re: FOSDEM booth box
On Wed, Jan 31, 2018 at 5:31 PM, Adriaan de Groot wrote: > So, for the booth box, today I picked up: > > - duct tape 50m > - steel cables, clamps, some kensington locks for tying stuff to the table to > discourage casual wandering-off > - tie wraps, various lengths and sizes > - i've got a 4x Schuko and a 3xSchuko + 4x narrow EU power block > - 3 5V USB chargers, varying from 100ma to 10A > > I'll update the wiki. > > Note that: > - we don't have t-shirts or much swag to sell. > - i'll print up nametags for people who are on the wiki for booth-duty > - i need to get some padlocks to lock the steel cables > > > We don't have a "social experiment" lined up. Usually Lydia is the creative > one there. > > > [ade] Brilliant! I'll be bringing a KDE Slimbook and a Nexus 5X with Plasma to display! Aleix
Re: bugzilla, it's products, how they relate to projects. it's a mess...
I want to add something: one intimidating thing is that a new contributor needs to request editing rights to Bugzilla. Perhaps this was enforced when someone got fed up with reporters toggling statuses, but I think having such a fence is the wrong way to deal with this. People typically need to hunt for the right person to ask, be patient etc. It is the opposite of streamlined onboarding. In LibreOffice, we only restrict priority and severity and even those upwards from medium/normal. We monitor messy stuff with a script: https://gerrit.libreoffice.org/gitweb?p=dev-tools.git;a=history;f=esc-reporting/qa-tools.py Ilmari On 31.01.2018 19:25, Nate Graham wrote: Yes, I plan to do a big overhaul soon. But don't let that stop others who want to have a go, too. Nate On 01/31/2018 10:24 AM, Boudewijn Rempt wrote: On Wednesday, 31 January 2018 16:19:25 CET Luigi Toscano wrote: For the record, we have documentation about this. We just don't have an active BugSquad team around as it was before: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging https://community.kde.org/Bugsquad Yes, Nate linked to that as well -- but that's a seriously intimidating document! And even I had trouble reading it to the end.
Re: bugzilla, it's products, how they relate to projects. it's a mess...
Yes, I plan to do a big overhaul soon. But don't let that stop others who want to have a go, too. Nate On 01/31/2018 10:24 AM, Boudewijn Rempt wrote: On Wednesday, 31 January 2018 16:19:25 CET Luigi Toscano wrote: For the record, we have documentation about this. We just don't have an active BugSquad team around as it was before: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging https://community.kde.org/Bugsquad Yes, Nate linked to that as well -- but that's a seriously intimidating document! And even I had trouble reading it to the end.
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On Wednesday, 31 January 2018 16:19:25 CET Luigi Toscano wrote: > For the record, we have documentation about this. We just don't have an > active BugSquad team around as it was before: > > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > https://community.kde.org/Bugsquad Yes, Nate linked to that as well -- but that's a seriously intimidating document! And even I had trouble reading it to the end. -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
FOSDEM booth box
So, for the booth box, today I picked up: - duct tape 50m - steel cables, clamps, some kensington locks for tying stuff to the table to discourage casual wandering-off - tie wraps, various lengths and sizes - i've got a 4x Schuko and a 3xSchuko + 4x narrow EU power block - 3 5V USB chargers, varying from 100ma to 10A I'll update the wiki. Note that: - we don't have t-shirts or much swag to sell. - i'll print up nametags for people who are on the wiki for booth-duty - i need to get some padlocks to lock the steel cables We don't have a "social experiment" lined up. Usually Lydia is the creative one there. [ade] signature.asc Description: This is a digitally signed message part.
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On Wednesday, 31 January 2018 16:15:41 CET Boudewijn Rempt wrote: > On Wednesday, 31 January 2018 15:44:01 CET Nate Graham wrote: > > >> As Nate has now attained demigod status with his usability blog posts, > > >> I > > >> think it would be good to take advantage of all the positive attention > > >> and tie it into one of the other goals "Streamlined onboarding of new > > >> contributors". The point has to be hammered home: "If you love some > > >> dev, > > >> set them free of the burden of bug triage". > > > > > > Yes, that would be very good! > > > > Working on it now! "Demigod status," I like that... > > And I've started a short how-to-triage-a-bug manual draft: > > https://phabricator.kde.org/T7842 For the record, we have documentation about this. We just don't have an active BugSquad team around as it was before: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging https://community.kde.org/Bugsquad -- Luigi
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On Wednesday, 31 January 2018 16:18:44 CET Nate Graham wrote: > > We actually already have a centralized page with that information: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging, which is > linked to from https://community.kde.org/Get_Involved, which is now > linked to on kde.org. > Yes, this is very specific to how we work. I'll link to that document as well. > It probably needs some cleanup, and IMHO we should try to keep this page > as central and up-to-date possible. The Krita-specific page is good for > Krita, but if you could migrate any generally-applicable information to > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging, that would > be fantastic. > Do we want to keep the name KDE Bug Squad? As an institution it wasn't a runaway success... > Nate -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On 01/31/2018 08:15 AM, Boudewijn Rempt wrote: On Wednesday, 31 January 2018 15:44:01 CET Nate Graham wrote: As Nate has now attained demigod status with his usability blog posts, I think it would be good to take advantage of all the positive attention and tie it into one of the other goals "Streamlined onboarding of new contributors". The point has to be hammered home: "If you love some dev, set them free of the burden of bug triage". Yes, that would be very good! Working on it now! "Demigod status," I like that... And I've started a short how-to-triage-a-bug manual draft: https://phabricator.kde.org/T7842 We actually already have a centralized page with that information: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging, which is linked to from https://community.kde.org/Get_Involved, which is now linked to on kde.org. It probably needs some cleanup, and IMHO we should try to keep this page as central and up-to-date possible. The Krita-specific page is good for Krita, but if you could migrate any generally-applicable information to https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging, that would be fantastic. Nate
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On Wednesday, 31 January 2018 15:44:01 CET Nate Graham wrote: > >> As Nate has now attained demigod status with his usability blog posts, I > >> think it would be good to take advantage of all the positive attention > >> and tie it into one of the other goals "Streamlined onboarding of new > >> contributors". The point has to be hammered home: "If you love some dev, > >> set them free of the burden of bug triage". > > > > Yes, that would be very good! > > Working on it now! "Demigod status," I like that... > And I've started a short how-to-triage-a-bug manual draft: https://phabricator.kde.org/T7842 -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
Re: bugzilla, it's products, how they relate to projects. it's a mess...
As Nate has now attained demigod status with his usability blog posts, I think it would be good to take advantage of all the positive attention and tie it into one of the other goals "Streamlined onboarding of new contributors". The point has to be hammered home: "If you love some dev, set them free of the burden of bug triage". Yes, that would be very good! Working on it now! "Demigod status," I like that... Nate
Re: bugzilla, it's products, how they relate to projects. it's a mess...
On Wednesday, 31 January 2018 14:33:07 CET Ilmari Lauhakangas wrote: > On Monday, 29 January 12:16:07 UTC Boudewijn Rempt wrote: > >> On Monday, 29 January 2018 12:25:24 CET Harald Sitter wrote: > >> I don't like going to our bugzilla. > > > > Me neither... But that's more because I have to triage about a 1000 bug > > reports a year, and many of them are not bug reports at all, but > > support > > questions. > > This sounds horrifying and should absolutely not be the case. Over at > LibreOffice, an average full-time dev triages at most a 100 bugs per > year from scratch (number pulled from my hat). Nearly all of the reports > are first attacked by a ruthless gang of non-developers, numbering about > 20-30. Sure, there are some hybrid QA/dev beings, but they have usually > "grown up" inside the tracker and started to lean more and more towards > submitting patches. And then I'm also answering users on Reddit and Twitter and the Forum... There are some people who help out -- but it's a very small group of three, and only one of them is not a developers. This person is pretty good, especially considering the extremely low quality of most reports we get, but cannot manage this stream of bugs on their own, of course. And so I'm kind of the buffer between bugzilla and Dmitry, who I'm paying to work on Krita full-time, and who should be insulated from bugzilla even more than me. > As Nate has now attained demigod status with his usability blog posts, I > think it would be good to take advantage of all the positive attention > and tie it into one of the other goals "Streamlined onboarding of new > contributors". The point has to be hammered home: "If you love some dev, > set them free of the burden of bug triage". Yes, that would be very good! > Non-dev users often express themselves like they have an inferiority > complex, "sadly I don't know C++ so I can't help" etc. They need to > understand their amazing potential in something that is quite frankly a > direct energy transfer to developers. Yet, compared to other non-dev > tasks, QA does not require much to get started. You don't have to be > able to express yourself in eloquent ways, it is enough to blurt out > "Repro" or "No repro" in a hoarse voice every now and then. It's a bit more complicated, though -- there are three operating systems involved, the vagaries of all the different graphics tablets and drivers, multi-monitor issues. But I might be able to just put the usual suspects in a document, like "if a user complains about offsets, ask whether they have a multi-monitor setup", as well as instructions on which class of bugs can be reproduced. But people will need to know enough about Krita so they know how to ask for clarification. -- Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
bugzilla, it's products, how they relate to projects. it's a mess...
On Monday, 29 January 12:16:07 UTC Boudewijn Rempt wrote: On Monday, 29 January 2018 12:25:24 CET Harald Sitter wrote: I don't like going to our bugzilla. Me neither... But that's more because I have to triage about a 1000 bug reports a year, and many of them are not bug reports at all, but support questions. This sounds horrifying and should absolutely not be the case. Over at LibreOffice, an average full-time dev triages at most a 100 bugs per year from scratch (number pulled from my hat). Nearly all of the reports are first attacked by a ruthless gang of non-developers, numbering about 20-30. Sure, there are some hybrid QA/dev beings, but they have usually "grown up" inside the tracker and started to lean more and more towards submitting patches. As Nate has now attained demigod status with his usability blog posts, I think it would be good to take advantage of all the positive attention and tie it into one of the other goals "Streamlined onboarding of new contributors". The point has to be hammered home: "If you love some dev, set them free of the burden of bug triage". Non-dev users often express themselves like they have an inferiority complex, "sadly I don't know C++ so I can't help" etc. They need to understand their amazing potential in something that is quite frankly a direct energy transfer to developers. Yet, compared to other non-dev tasks, QA does not require much to get started. You don't have to be able to express yourself in eloquent ways, it is enough to blurt out "Repro" or "No repro" in a hoarse voice every now and then. Ilmari
