<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-template">
<p>Dear Mihovil,</p>
<p>do you keep replies with the other emails? I am not using the
Sent folder anymore and but complete threads into specific
folders; at a quick glance, I find it hard to filter out which
of emails in a thread come from myself:<br>
</p>
<p><img src="cid:part1.38B9DFE3.1A651DEC@gmail.com" alt=""></p>
<p>so although I can understand the rationale and possible
advantage of always displaying the "main" correspondent instead
of my own email address I think the implementation is slightly
problematic as, during daily usage, I find that it slows down my
ability to quickly pinpoint one of my own posts. They should
visually stand out more which IMHO should have been part of the
patch and would likely have been flagged during usability
testing. suggestion: make the color of the "mine" arrow
configurable and default it to black rather than light gray -
also add a tooltip over the arrow that explains "from: <full
name + email address>" ; I bet half of the complaints about
the features may go away.</p>
<p>Another interesting thing in the example (mailing list) above:
members of the mailing list are shown but only my own name is
replaced with the list name. Not sure but it has a strange feel
to it - can it be improved?<br>
</p>
<p>just my 2cents,<br>
Axel<br>
</p>
<p></p>
-- <br>
<style type="text/css">
.myName:hover, .myName a:hover { font-size:13pt; text-shadow: 3px 3px 4px rgba(200,250,200,0.7);}
.moz-signature {opacity: 1.0 !important;}
.myName a { cursor: pointer !important; transition:font-size 0.5s;}
.myLogo {
transition: all .4s ease-out;
}
.myLogo:hover {
transform: scale(3) translate(-30px,-5px);
}
</style>
<div id="mySignature" style="width: 65%; padding: 0.8em 1.2em;
font:x-small verdana; color: #444; box-shadow: 4px 4px 9px -2px
rgba(0,0,0,0.65); border-radius: 1em; padding: 0.4em 2em;
border: 1px dashed #444; background: rgb(230,240,163);
background: linear-gradient(to bottom, rgba(230,240,163,1)
0%,rgba(210,230,56,1) 50%,rgba(195,216,37,1)
51%,rgba(219,240,67,1) 100%);">
<b class="myName" style="text-shadow: 1px 1px 2px #DDD;
transition:font-size 0.5s;"><a
href="mailto:axel.grude@gmail.com">Axel Grude</a></b>
<br>
Software Developer
<br>
Thunderbird Add-ons Developer
<span style="color:#666666; font-size:xx-small">(QuickFolders,
quickFilters, QuickPasswords, Zombie Keys, SmartTemplate4)</span>
<br>
AMO Editor <img style="margin-top: 1em; float: right;
box-shadow: 1px 1px 2px rgba(20, 20, 20, 0.4);"
moz-do-not-send="false" class="myLogo"
src="cid:part3.F1F2EE14.FAF62BF1@gmail.com" alt="Get
Thunderbird!" height="15" width="94">
</div>
</div>
<br>
<div id="smartTemplate4-quoteHeader">
<style type="text/css" scoped="">
#newHeaderAG1 b { font-weight:bold; color: #990033; min-width: 4.5em; max-width:none; display:inline-block;}
</style><br>
<blockquote type="cite" style="margin-bottom: -20px !important;
padding-bottom:20px !important;">
<div id="newHeaderAG1" style="font-size: x-small; padding:1em;
background-color:rgba(220,220,240,0.4); border-radius:3px;"> <b>Subject:</b>Re:
Changes to review policy<br>
<b>From:</b>Mihovil Stanić<br>
<b>To:</b>Tb-planning <br>
<b>Sent: </b>Thursday, 28/04/2016 10:05:43 10:05 GMT ST +0100
[Week 17]<br>
</div>
</blockquote>
</div>
<blockquote class=" cite"
id="mid_6fa02dd1_2c08_8255_7125_19d5dedd60eb_miho_im"
cite="mid:6fa02dd1-2c08-8255-7125-19d5dedd60eb@miho.im"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<p><font size="-1"><font face="Arial">Not really sure what's all
fuss around correspondents column?</font></font></p>
<p><font size="-1"><font face="Arial">I receive about 15.000
emails a year on work email, handled by TB, and didn't
notice anything different in TB behaviour except column
isn't named "From", it's now "Correspondents".</font></font></p>
<p><font size="-1"><font face="Arial">I'm not using inbox for
received and sent email, those are two different folders, so
maybe that's why I don't have problems with it.</font></font></p>
<p><font size="-1"><font face="Arial">Mihovil</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">28.04.2016 u 07:33, Jim Porter je
napisao/la:<br>
</div>
<blockquote class=" cite"
id="mid_d56a7633_10d9_6151_1ba0_19c39a9886de_gmail_com"
cite="mid:d56a7633-10d9-6151-1ba0-19c39a9886de@gmail.com"
type="cite">
<pre wrap="">Given the user outcry around the upgrade from the From/Recipients column
to the Correspondents column (see
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1152706"><https://bugzilla.mozilla.org/show_bug.cgi?id=1152706></a> for example), I'd
like to propose some new guidelines to our review policy to prevent this
from happening again. To be rather blunt, I don't think we're upholding
the minimum standards of quality that people should be able to expect
from us.
It's an especially stark contrast when you compare the Correspondents
column issue to another change in 45.0: the new default in composition
to create new <p> elements every time you hit enter. A number of people
have also been dissatisfied with the latter, but the fix for that is to
uncheck a single checkbox.
Undoing the Correspondents column upgrade, on the other hand, involves
setting a hidden pref and then fixing all the folders that were
"upgraded". Worse, we can't automatically roll the column state back
because we've actually destroyed data! If a user had *both* the From and
Recipient columns shown, the upgrade code hides them[1], and there's no
way I know of to look at the current state to determine this.
Therefore, I'd like to propose the following: any change to
Thunderbird's defaults should have a super-review before landing.
Super-reviewers would be especially focused on making sure that changes
meet most or all the following conditions, in descending order of
importance:
1) No data/program state should be lost.
2) Before changing a default, we should be sure the new default is
fully-operational.
3) Users should have an easy path to roll back to the previous UI/UX if
they don't like the new version. If possible, ask the user *before*
upgrading them.
4) It should be easy for users to find out what's changed, along with
instructions for how to adjust the new behavior to their liking.
Of course, I understand the desire to ship new features, especially if
we think they're better than the old ones, but we need to be very
careful. Email is mission-critical for many people, and as such, we have
a responsibility not to break things. Hopefully with a few more eyes on
changes like this, we can come up with ways to satisfy existing users'
needs while still working to modernize Thunderbird.
Thoughts?
- Jim
[1] Full disclosure: this is based solely on inspection, not actually
running the code.
_______________________________________________
tb-planning mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tb-planning mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a>
<a class="moz-txt-link-freetext" href="https://mail.mozilla.org/listinfo/tb-planning">https://mail.mozilla.org/listinfo/tb-planning</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>