[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: Officially adopt "Noteworthy" label into KDE policy
From: Julian / xyquadrat <mail () xyquadrat ! ch>
Date: 2020-09-21 20:11:59
Message-ID: e113b47a-b6fc-6d54-1b59-e96da908bbd1 () xyquadrat ! ch
[Download RAW message or body]
Thank you Nate and Johannes for your positive feedback. If there are no
further complaints / comments, I'll edit the Commit Policy wiki page
tomorrow and add the points I listed below.
Cheers,
Julian / xyquadrat
On 18.09.20 10:05, Julian / xyquadrat wrote:
>
> Hi all,
>
> A few months back I suggested on behalf of the Promo team the
> introduction of a new label for issues and merge requests (see
> https://marc.info/?t=158695327000009&r=1&w=2 for the thread).
> The idea behind this "Noteworthy" label was to make it easier for
> Promo to keep up with all important new changes that are coming up in
> our software and reduce the possibility that something noteworthy gets
> overlooked.
> Since then, the GitLab migration has been completed and such a label
> has actually been introduced (see
> https://invent.kde.org/dashboard/merge_requests/?scope=all&label_name[]=Noteworthy
> for an overview of Merge Requests tagged with "Noteworthy").
>
> Given that the technical challenge is now solved, I'd like to propose
> to make this Noteworthy label official in the sense of adding it to
> the "Special keywords" section of Commit Policy (if there is a more
> appropriate place, please suggest it!) and encourage all contributors
> to start using it.
>
> A few remarks:
> - Of course all contributions are noteworthy and important. Promo does
> not want to discount the work that goes into small and unnoticeable fixes.
> - If you are not sure whether a MR or issue should be "Noteworthy" or
> not, tag it with "Noteworthy" (-> be liberal with the label usage).
> Promo will then consider such edge cases in detail.
> - Not all things tagged might make it into an official announcement.
> This is (usually) not due to us overlooking them, but because we have
> to carefully prioritize what we include. If you think something was
> left out that should definitely have been included, reach out to us on
> #kde-promo and we will be happy to discuss individual cases and solutions.
>
> *Examples of noteworthy changes:*
>
> * User facing feature additions (e.g. /New useful effect added to
> Kdenlive/)
> * Big changes in UI (e.g. /a KCM is rewritten in QML and now looks
> distinctively different/)
> * Long-standing, annoying bugs (e.g. /Rework of the previously
> bug-ridden MTP implementation in KIO/)
> * Large technology shifts (e.g. /Port to Qt 6/)
> * Significant performance improvements (best paired with concrete
> numbers, but not necessary)
>
> *Examples of changes not considered noteworthy: *
>
> * Small UX annoyances and fixes. Whilst those add up to something
> very important, the individual changes (e.g. "more consistent
> padding in dialogs") are not interesting to users.
> * Shifts in technology that do not affect the behavior of the
> product (e.g. /porting from library X version Y to library X
> version Y+1/)
> * Minor changes to tools and backends used in the development process
>
> Feedback and criticism is much appreciated.
>
> Cheers and have a nice day,
> Julian / xyquadrat
>
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thank you Nate and Johannes for your positive feedback. If there
are no further complaints / comments, I'll edit the Commit Policy
wiki page tomorrow and add the points I listed below.</p>
<p>Cheers,<br>
Julian / xyquadrat<br>
</p>
<div class="moz-cite-prefix">On 18.09.20 10:05, Julian / xyquadrat
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:856a1e3c-eb0f-5435-143e-e06e26f79a9e@xyquadrat.ch">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Hi all,</p>
<p>A few months back I suggested on behalf of the Promo team the
introduction of a new label for issues and merge requests (see <a
class="moz-txt-link-freetext"
href="https://marc.info/?t=158695327000009&r=1&w=2"
moz-do-not-send="true">https://marc.info/?t=158695327000009&r=1&w=2</a>
for the thread).<br>
The idea behind this "Noteworthy" label was to make it easier
for Promo to keep up with all important new changes that are
coming up in our software and reduce the possibility that
something noteworthy gets overlooked.<br>
Since then, the GitLab migration has been completed and such a
label has actually been introduced (see
<a class="moz-txt-link-freetext"
href="https://invent.kde.org/dashboard/merge_requests/?scope=all&label_name"
moz-do-not-send="true">https://invent.kde.org/dashboard/merge_requests/?scope=all&label_name</a>[]=Noteworthy
for an overview of Merge Requests tagged with "Noteworthy").<br>
<br>
Given that the technical challenge is now solved, I'd like to
propose to make this Noteworthy label official in the sense of
adding it to the "Special keywords" section of Commit Policy (if
there is a more appropriate place, please suggest it!) and
encourage all contributors to start using it.</p>
<p>A few remarks:<br>
- Of course all contributions are noteworthy and important.
Promo does not want to discount the work that goes into small
and unnoticeable fixes.<br>
- If you are not sure whether a MR or issue should be
"Noteworthy" or not, tag it with "Noteworthy" (-> be liberal
with the label usage). Promo will then consider such edge cases
in detail.<br>
- Not all things tagged might make it into an official
announcement. This is (usually) not due to us overlooking them,
but because we have to carefully prioritize what we include. If
you think something was left out that should definitely have
been included, reach out to us on #kde-promo and we will be
happy to discuss individual cases and solutions.<br>
</p>
<p><strong>Examples of noteworthy changes:</strong></p>
<ul class="remarkup-list">
<li class="remarkup-list-item">User facing feature additions
(e.g. <em>New useful effect added to Kdenlive</em>)</li>
<li class="remarkup-list-item">Big changes in UI (e.g. <em>a
KCM is rewritten in QML and now looks distinctively
different</em>)</li>
<li class="remarkup-list-item">Long-standing, annoying bugs
(e.g. <em>Rework of the previously bug-ridden MTP
implementation in KIO</em>)</li>
<li class="remarkup-list-item">Large technology shifts (e.g. <em>Port
to Qt 6</em>)</li>
<li class="remarkup-list-item">Significant performance
improvements (best paired with concrete numbers, but not
necessary)<br>
</li>
</ul>
<p><strong>Examples of changes not considered noteworthy: </strong></p>
<ul class="remarkup-list">
<li class="remarkup-list-item">Small UX annoyances and fixes.
Whilst those add up to something very important, the
individual changes (e.g. "more consistent padding in dialogs")
are not interesting to users.</li>
<li class="remarkup-list-item">Shifts in technology that do not
affect the behavior of the product (e.g. <em>porting from
library X version Y to library X version Y+1</em>)</li>
<li class="remarkup-list-item">Minor changes to tools and
backends used in the development process</li>
</ul>
<p>Feedback and criticism is much appreciated.</p>
<p>Cheers and have a nice day,<br>
Julian / xyquadrat<br>
</p>
</blockquote>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic