-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.triage-policies.yml
91 lines (78 loc) · 3.71 KB
/
.triage-policies.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# This is a set of bugbot commands for issues and merge requests - setting any of the
# bugbot::foo labels will trigger gitlab-triage to run with this ruleset (well, the
# one we have on the main branch at the time)
#
# Note that for adding labels via gitlab-triage, the label must first be created in the project.
################################################################################
# Rules definitions
################################################################################
.template-required: &template-required
name: "Require using a template"
conditions:
labels:
- "bugbot::template-required"
actions:
remove_labels:
- "bugbot::template-required"
comment: |
Hi {{author}}! Thanks for filing this issue/merge request. In order to process your
request more efficiently, please edit it and choose the appropriate template in the
list above your text, then fill in the required information.
.insufficient-motivation: &insufficient-motivation
name: "Require better motivation"
conditions:
labels:
- "bugbot::insufficient-motivation"
actions:
remove_labels:
- "bugbot::insufficient-motivation"
comment: |
Hi {{author}}! Thanks for filing this issue/merge request. We do not have sufficient
information about the *current* user base of the feature you propose. Please provide
neutral and accessible *evidences*[^1] (if possible in English), that this feature is
sufficiently popular in order to be shipped as part of the default xkeyboard-config
keymaps.
Features added to the distribution means we have to maintain these features for years
and decades into the future and we avoid having to do so for features that we expect
have a tiny number of users.
Note that comparing the new feature to one already included in xkeyboard-config is
*not* a sufficient motivation: the focus must be on the *current* user-base of *your*
proposal.
[^1]: Such as: an active community.
You may also install it locally instead; we have
[instructions for Xorg](https://who-t.blogspot.com/2021/02/a-pre-supplied-custom-keyboard-layout.html)
and [instructions for Wayland](https://xkbcommon.github.io/libxkbcommon/doc/current/md_doc_user_configuration.html).
.too-exotic: &too-exotic
name: "Close as too exotic"
conditions:
labels:
- "bugbot::too-exotic"
actions:
remove_labels:
- "bugbot::too-exotic"
comment: |
Hi {{author}}! Thanks for filing this issue/merge request. We think this keyboard
feature is too exotic to be shipped as part of the default xkeyboard-config keymaps.
Features added to the distribution means we have to maintain these features for years
and decades into the future and we avoid having to do so for features that
we expect have a tiny number of users.
As a general rule, we will add layouts that are part of official standards but not
experimental layouts. If this is the case here, please re-open with a comment.
Please install it as a custom layout instead, we have
[instructions for Xorg](https://who-t.blogspot.com/2021/02/a-pre-supplied-custom-keyboard-layout.html)
and [instructions for Wayland](https://xkbcommon.github.io/libxkbcommon/doc/current/md_doc_user_configuration.html).
status: "close"
################################################################################
# Rules
################################################################################
resource_rules:
issues:
rules:
- *template-required
- *insufficient-motivation
- *too-exotic
merge_requests:
rules:
- *template-required
- *insufficient-motivation
- *too-exotic