Project

General

Profile

Feature #6992

Put it more clearly that most bug reports without an email address are useless

Added by intrigeri almost 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
03/30/2014
Due date:
% Done:

100%

Feature Branch:
feature/6992-whisperback-email-address
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:
WhisperBack

Description

Our Report an error page reads:

Giving us an email address allows us to contact you to clarify the problem. But it also provides an opportunity for eavesdroppers, like your email or Internet provider, to confirm that you are using Tails.

The WhisperBack UI reads:

If you don't mind disclosing some bits of your identity to Tails developers, you can provide an email address to let us ask more details about the bug. Additionally entering a public PGP key enables us to encrypt such future communication.

Anyone who can see this reply will probably infer you are a Tails user. Time to wonder how much you trust your Internet and mailbox providers?

I think it would be good to put it very clearly that most bug reports we receive, that lack an email address, are basically useless.
(And by the way, I would remove the "Time to wonder.." part, that feels a bit too defensive to me.)


Related issues

Related to Tails - Feature #7180: Remove the right pane of WhisperBack Resolved 05/09/2014
Duplicated by Tails - Bug #6855: WhisperBack should explain why providing an email address is useful Duplicate 03/06/2014

Associated revisions

Revision cbd89f16 (diff)
Added by Tails developers over 5 years ago

Put it more clearly that most bug reports without an email address are useless (Closes: #6992)

Revision 1206eaf9 (diff)
Added by Tails developers about 5 years ago

Put it more clearly in WhisperBack that most bug reports without an email address are useless (Will-Fix: #6992).

The documentation part was done already in commit:5439823.

This very commit merely imports the same phrasing into our WhisperBack configuration.

Revision 91fdcdbd
Added by Tails developers about 5 years ago

Merge remote-tracking branch 'origin/feature/6992-whisperback-email-address' into devel

fix-committed #6992

History

#1 Updated by intrigeri almost 6 years ago

  • Assignee set to sajolida

Assigning to sajolida to get his opinion. Please set another kind of work and status = confirmed if you agree, or reject else.

#2 Updated by sajolida almost 6 years ago

  • Status changed from New to Confirmed
  • Assignee deleted (sajolida)

I think the sentence in the documentation is less defensive than the one in WhisperBack, so that could be an easy improvement.

I'm leaving this as a "Discuss" task, but for me that could be made a "Code" task assigned to Alan if we agree on this option.

#3 Updated by intrigeri almost 6 years ago

I'm leaving this as a "Discuss" task, but for me that could be made a "Code" task
assigned to Alan if we agree on this option.

Getting the phrasing right would be better done before sending the ball in Alan's court.
Do we want exactly the same phrasing as in the doc?

#4 Updated by sajolida almost 6 years ago

I'm leaving this as a "Discuss" task, but for me that could be made a "Code" task
assigned to Alan if we agree on this option.

Getting the phrasing right would be better done before sending the ball in Alan's court.
Do we want exactly the same phrasing as in the doc?

Seeing the context, the sentences could be the same on both sides.
Reusing the one currently in the doc would already make it less
defensive. Do you think we should make it more explicit that most
reports without email addresses are useless?

And what about the PGP key option? It's not mentioned in the doc at the
moment. Shall we add it there?

#5 Updated by intrigeri almost 6 years ago

  • Description updated (diff)

#6 Updated by intrigeri almost 6 years ago

sajolida wrote:

Seeing the context, the sentences could be the same on both sides.

OK.

Reusing the one currently in the doc would already make it less
defensive.

This could be a first great step, but it does not fully address the concerns I raised when creating this ticket.

Do you think we should make it more explicit that most
reports without email addresses are useless?

Yes, that's exactly what this ticket is about :)

And what about the PGP key option? It's not mentioned in the doc at the
moment. Shall we add it there?

No idea, and this looks very much off-topic here.

#7 Updated by BitingBird almost 6 years ago

https://tails.boum.org/doc/first_steps/bug_reporting/index.en.html#index4h2 mentions GPG option. It's not very detailed, but it's there :)

#8 Updated by sajolida over 5 years ago

  • Title: Put it more clearly that most bug reports without an email
    address are useless

#9 Updated by u over 5 years ago

yes, this should be mentioned. but i would rephrase a bit. sometimes phrases in the doc are not very clear to me.

"Giving us an email address would allow us to contact you in order to clarify the problem. This is needed for the vast majority of the reports we receive as most reports without any contact information are useless. On the other hand it also provides an opportunity for eavesdroppers, like your email or Internet provider, to confirm that you are using Tails."

#10 Updated by sajolida over 5 years ago

  • Related to Feature #7180: Remove the right pane of WhisperBack added

#11 Updated by sajolida over 5 years ago

  • Subject changed from Put it more clearly that most bug reports without an email address are useless? to Put it more clearly that most bug reports without an email address are useless
  • Assignee set to alant
  • % Done changed from 0 to 50
  • Type of work changed from Discuss to Code

Done in the doc with commit 5439823.

Now has to be done in WhisperBack.

#12 Updated by intrigeri over 5 years ago

  • Category set to 174

#13 Updated by intrigeri over 5 years ago

Alan, if you don't think you can do it, say, by mid-August, please de-assign you this ticket so that other contributors know they can do it. Thanks!

#14 Updated by intrigeri over 5 years ago

  • Duplicated by Bug #6855: WhisperBack should explain why providing an email address is useful added

#15 Updated by BitingBird about 5 years ago

  • Assignee deleted (alant)

#16 Updated by intrigeri about 5 years ago

  • Assignee set to intrigeri
  • Target version set to Tails_1.3

#17 Updated by Tails about 5 years ago

  • Status changed from Confirmed to In Progress

Applied in changeset commit:f98afd380127beeda63b0752a9e364c679393f89.

#18 Updated by intrigeri about 5 years ago

  • Assignee deleted (intrigeri)
  • QA Check set to Ready for QA

#19 Updated by alant about 5 years ago

  • Assignee set to alant
  • Feature Branch set to feature/6992-whisperback-email-address

#20 Updated by Tails about 5 years ago

  • Status changed from In Progress to 11
  • % Done changed from 50 to 100

Applied in changeset commit:4c04683da974c0c47da56568a7ebc0043083a355.

#21 Updated by alant about 5 years ago

  • Assignee deleted (alant)
  • QA Check changed from Ready for QA to Pass

#22 Updated by BitingBird almost 5 years ago

  • Status changed from 11 to Resolved

#23 Updated by sajolida over 4 years ago

Here are some stats across 1.2 and 1.3 releases:

1.2

reply 63 40%
total 157

1.3

reply 94 43%
total 217

Also available in: Atom PDF