Create Task
Maniphest T13537

Write definition of what is "Noteworthy"
Closed, ResolvedPublic
Actions

Description

We need clear guidelines on which Merge Requests and Issues should be tagged as "Noteworthy". Of course, all MR's and commits are noteworthy and important - but only some are promotable by KDE Promo.

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

Examples of changes not considerent 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
xyquadrat created this task.Aug 26 2020, 2:18 PM
xyquadrat triaged this task as Normal priority.
paulb updated the task description. (Show Details)Aug 26 2020, 4:05 PM
paulb added a subscriber: paulb.Aug 26 2020, 4:17 PM

"Minor changes to tools and backends used in development process"? Like when a project changes from one CI workflow with a specific set of tools, to another or one bugtracking system to another.

Note that I do think that things like migrating the whole of KDE to GitLab is newsworthy. I also think that it is important existing and potential contributors now about it, of course, but it is an internal thing. Not news.

What do you think?

paulb added a comment.Aug 26 2020, 4:18 PM

I would suggest we revise past documents we have compiled to write the announcements and categorise or even grade the entries from less to more newsworthy.

ngraham added a subscriber: ngraham.Aug 26 2020, 7:55 PM

JFYI "all KCMs rewritten in QML" is probably too big for "noteworthy". That's the kind of thing that takes 5 years to do and trickles in a little at a time. That's a different scale from "Cool new user-facing feature was added".

xyquadrat added a comment.Aug 26 2020, 8:06 PM

Sorry, I meant "whenever a KCM is rewritten, that's a cool new user-facing feature" (e.g. the Bluetooth one that is currently being worked on). That isn't very clear from the description though, I see that now.

paulb added a comment.Aug 26 2020, 11:41 PM
In T13537#238270, @ngraham wrote:

JFYI "all KCMs rewritten in QML" is probably too big for "noteworthy". That's the kind of thing that takes 5 years to do and trickles in a little at a time. That's a different scale from "Cool new user-facing feature was added".

Maybe "Finishing all KCMs rewritten in QML" is the newsworthy thing

ngraham added a comment.EditedAug 28 2020, 8:35 PM

"Finishing all KCMs rewritten in QML" is the same thing as "all KCMs rewritten in QML"

xyquadrat updated the task description. (Show Details)Sep 13 2020, 5:03 PM
xyquadrat updated the task description. (Show Details)
xyquadrat closed this task as Resolved.Sep 18 2020, 8:08 AM
xyquadrat moved this task from Incoming - All new tasks and ideas go here to Done on the KDE Promo board.

Mail sent to kde-community and kde-devel. If we receive feedback that should be incorporated, we can do that directly in the Commit Policy (or wherever we put it).