Hi all,
+1 for text over images whenever possible (for the same reason, it's
convenient to have it indexed by search engines).
+0 for image support, I see the benefits but I am afraid we will see less
and less text/stack traces.
Best regards,
Alessandro
On Wed, 28 Oct 2020 at 01:13, Michael Mior <mm...@apache.org> wrote:
> +1 in favouring text over images where possible, -0 to allowing images
> on the dev list. (If images aren't allowed, I think it would almost be
> preferable if such messages could be rejected to give the author a
> chance to revise.)
>
> --
> Michael Mior
> mm...@apache.org
>
> Le mar. 27 oct. 2020 à 15:12, Julian Hyde <jh...@apache.org> a écrit :
> >
> > There is a growing trend of attaching screenshots of stack traces,
> > code, and debugger sessions to JIRA cases and email threads.
> >
> > I don't like it. I think we should have a policy discouraging
> screenshots.
> >
> > In my opinion, the text is almost always preferable. It can be found
> > by search engines. It can be included in email messages. (ASF email
> > strips image attachments.) And for code, links to a line of code in
> > GitHub are preferable because it allows people to see the context.
> >
> > When someone logs a bug with an attached PNG of a stack trace, we
> > should ask them to replace it with the stack trace in text format
> > (surrounded by {noformat} tags so that JIRA doesn't mangle it).
> >
> > I will acknowledge that sometimes a screenshot of a debugger is useful
> > - if it shows state. Still, it needs to be accompanied by an
> > explanation. ("The code expects to find a key, but the map is empty.")
> > And perhaps the explanation and a test case would suffice.
> >
> > What do people think of this?
> >
> > Julian
>
