Screenshot quality in KDE announcements

Hi,

we once again put out a major release announcement using screenshots
with obvious UI defects (e.g. the kscreen one where the orientation
bar in the display delegate isn't clipped by the rounded rect and the
vertical text alignment is off) - frustratingly, some of which have
already been fixed in the beta (including those).

This is a real problem because it causes negative feedback in venues
where the announcement is discussed every time. It's not a small pro-
blem, either, because visual quality is one of our major reputation
weak spots, so people actively scan our material for defects to con-
firm this widely-held belief.

There is a bigger problem underlying this which starts in our dev
process, but for promo purposes we should try to put our best face
forward and use high-quality screenshots. They show the actual pro-
duct; they're perhaps the most important part of any communication
we do.

Could we discuss some strategies to avoid this problem in the future?

I'm imagining a QA process+checklist:

* Promo puts announcement screenshot package together ahead of time.
* Promo checks those screenshots for obvious rendering and UX
   defects and tries to alert developers to them.
* Promo runs those screenshots by the VDG list to employ the VDG for
   bug spotting as well.
* We try to fix this problem and re-take the screenshots in time.

We already do these things for announcement texts, but screenshots
are often done ad-hoc and last minute, and it shows. They deserve
no less quality control than the text.


Cheers,
Eike

_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.