Re: I have written a draft for the Reporting Bugs guide

[Walter Lapchynski]

On May 11, 2017 3:17:14 PM PDT, Alberto Salvia Novella  
wrote:

>Men

There's more than just those in the community. 

> on mail I'm just b*.
> put that b*** there.

This is inappropriate language for this community. Please consult the Code of 
Conduct. 

> when I answer in 
>video I know my intentions are well interpreted, and that I'm not
>saying 
>something too stupid that could piss people off.

Your video in response to the angry response you got posting a confusing image 
was far more offensive than anything you said in text. 

I'm convinced you have good intentions. Unfortunately, the road to hell is 
paved with those. I encourage you to stop and think long and hard about how to 
contribute successfully to a community that doesn't always think like you. 
Hint: read the Code of Conduct. 
--
   @wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D
68F6 8B57 A48B C4F2 051A

-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[Brian Burger]

On Thu, May 11, 2017 at 9:29 AM, Alberto Salvia Novella <
es204904...@gmail.com> wrote:

> With you permission I'm going to answer all email on video from now on.
> Simply having to agree with people on text proves to be too tense for me.
>
> Anyway if you are unable to understand spoken English in a private
> conversation, let me know and I will make an exception there.
>
>
You want to answer the emails that people send to these shared lists with
private video calls to people?

What?

No. These lists are the appropriate venue for this discussion.

Brian
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[Brian Murray]

On Thu, May 11, 2017 at 06:29:00PM +0100, flocculant wrote:
> 
> 
> On 11/05/17 17:29, Alberto Salvia Novella wrote:
> >With you permission I'm going to answer all email on video from now on.
> >Simply having to agree with people on text proves to be too tense for me.
> >
> >Anyway if you are unable to understand spoken English in a private
> >conversation, let me know and I will make an exception there.
> >
> >Thank you.
> >
> >
> >
> >
> Please supply written answers - not going to look at videos.

Nor will I after finding a frog boiling in water in one.

--
Brian Murray


signature.asc
Description: PGP signature
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: Bug with SYSLOG

[Brian Murray]

On Tue, May 09, 2017 at 08:06:07AM +, Upadhyay Manas Vijay (PSI) wrote:
> Dear Sir/Madam,
> 
> I am running Ubuntu 14.04 and am facing a weird problem with syslog. I
> found that the kern.log files are exceptionally large compared to
> other files. (there were several kern.log files, I deleted the older
> versions). The latest ken.log file is currently occupying 37.9 GB
> space. This started happening three days ago. I had a user program
> running and I locked my computer screen. After a few hours when I
> logged back in I found that my diskspace was zero. This happened again
> yesterday. In principle, this program shouldn't be the cause of the
> program because I have run the same code without modifications before
> and it didn't generate large amounts of data. I am not sure where the
> problem comes from. Perhaps you could help.

It's probably bug 1630516[1] for which there is currently a package in
-proposed to fix the problem. The bug report's description and some
comments contain detailed information about how to enabled -proposed and
test the package.

[1] https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1630516

--
Brian Murray
Ubuntu Bug Master


signature.asc
Description: PGP signature
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[flocculant]

On 11/05/17 17:29, Alberto Salvia Novella wrote:
With you permission I'm going to answer all email on video from now 
on. Simply having to agree with people on text proves to be too tense 
for me.


Anyway if you are unable to understand spoken English in a private 
conversation, let me know and I will make an exception there.


Thank you.





Please supply written answers - not going to look at videos.
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[Alberto Salvia Novella]

With you permission I'm going to answer all email on video from now on. 
Simply having to agree with people on text proves to be too tense for me.


Anyway if you are unable to understand spoken English in a private 
conversation, let me know and I will make an exception there.


Thank you.


-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[Alberto Salvia Novella]

Flocculant:

What if the things you both agree on - everyone else in the world
disagrees with?


Since I will be showing the same draft to everyone, we will know.


Dario Ruellan:
> I have no problem leaving this in public, in fact, could be nice to
> first gather consensus regarding the actual documentation.

The problem with that is any conversation tends to be super lengthy, and 
when people discusses things in a public manner they tend to be more 
defensive. Then the conversation easily turns spam, and bystanders just 
want it to end.


On the other hand if we agree first on private we will be talking only 
about what that particular person really feels is interesting, with more 
deep, and there won't be any need to defend points of views.


Then the public conversation will be much more easygoing.



-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[Dario Ruellan]

On Wed, May 10, 2017 at 4:16 PM, Alberto Salvia Novella <
es204904...@gmail.com> wrote:


> What if we took advantage of the capability of wikis to abstract pages,
> and we make a guide that is concise, but provides generous amount of detail
> on sub-pages?
>

I think that can be the way to go. Looking at the current documentation, we
can divide the thing into this categories:

Application crash
System crash
Non-crash bugs for apps
Non-crash bugs for system
Translation bugs

and not present but implicit:
non-bugs but actually feature requests

Now, application crash and system crash can have automated reports, so,
this guide is going to be useful only if the user wants to fill a manual
report. Seems that the guide is using three approaches

Manually on Launchpad
Using Apport on an open window
Using Apport on a specific package
Messing with the Apport config file to enable some options that perhaps are
disabled on a stable release.

The last one looks a bit overkill. It is nice to know this if you're
planning to be a regular bug reporter, but for a one-time reporter I don't
think is going to work.

About the manual use of Apport, I don't remember if you need a Launchpad
account to file a bug this way. If NOT, then, I prefer the Launchpad
approach, since otherwise can be difficult to follow up the bug, if you
need more details from the reporter.

So, in the end, this document can be the "advanced" guide, and the simple
or quick guide can be something like:

System freeze -> gather information -> Launchpad -> search for similar bugs
-> report
System bug -> is it really a system bug? -> update -> gather information ->
Launchpad -> search for similar bugs -> report
App bug -> is it really an app bug? -> update -> gather information ->
Launchpad -> search for similar bugs -> report
Missbehaving of system/app -> is it really a bug? -> update -> gather
information -> Launchpad -> search for similar bugs -> report
Translation bug -> determine the app -> update -> Launchpad -> search for
similar bugs -> report
Feature requests -> go somewhere

-- + -- + -- + -- + -- + --

So, the question here is: we need this simplification? The idea is to
gather more bugs from regular users. Alberto is stating that many people
has problems with the current documentation, and after reading the guide, I
can say that can be a bit technical. But that can be actually the point:
filter regular users from the ones that have the knowledge and dedication
for this.

-- + -- + -- + -- + -- + --


> Do in private, so we can keep the conversation as light as possible till
> we finally get it to the public.
>
>
I have no problem leaving this in public, in fact, could be nice to first
gather consensus regarding the actual documentation.
-- 
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality

Re: I have written a draft for the Reporting Bugs guide

[flocculant]

On 11/05/17 00:33, Alberto Salvia Novella wrote:

...

Basically because we are not skipping the public conversation. But 
just agreeing as far as possible first in private, so what's brought 
to public is just the few things that we were unable to agree with.


And what if the things you both agree on - everyone else in the world 
disagrees with?
That way we won't be having long discussions about minimal details, 
and it fact that will allow to dig more into the needs of individual 
persons.







--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality