1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA512
|
3 |
|
4 |
On Mon, 24 Mar 2014 09:32:40 +0200
|
5 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote:
|
6 |
> |
7 |
> Who is going to approve/disapprove tagable attributes and the tags |
8 |
> themselves? How will you resolve disagreements people have? |
9 |
|
10 |
Sounds like a job for QA
|
11 |
|
12 |
> |
13 |
> What about the case of a package maintainer that simply can't be |
14 |
> bothered doing tags at all? |
15 |
> |
16 |
> I'm not against tagging per se, they can be useful. But they do have |
17 |
> to be strictly controlled otherwise things get out of hand very |
18 |
> quickly. Every case I've seen of software that uses a freeform |
19 |
> tagging mechanism fails almost instantly as it becomes very |
20 |
> inconsistent. I have one of these apps in a corporate setting right |
21 |
> now, have you any idea how many ways people can come up with to tag |
22 |
> the concept of "cloud"? |
23 |
|
24 |
Some of these could probably be detected by meeting a treshold in
|
25 |
Levenshtein distance (or some variant of) and making a suggestion to
|
26 |
consider found alternative before doing the commit
|
27 |
|
28 |
- --
|
29 |
Jan Matějka | Gentoo Developer
|
30 |
https://gentoo.org | Gentoo Linux
|
31 |
GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B
|
32 |
-----BEGIN PGP SIGNATURE-----
|
33 |
Version: GnuPG v2.0.22 (GNU/Linux)
|
34 |
|
35 |
iQEcBAEBCgAGBQJTMS9uAAoJEIN+7RD5ejah5bIH/i6dERPVS2i/rd76HQRHjynr
|
36 |
w7C4N5OQi+cN339f2/JusPwxrfBrUiN7ulsgWACMPz4s8/ZA9yrsRRnqvC2P8bnR
|
37 |
25n94z0vUZa3K5V3MIuDugfKa6nwVY9gZHZj6BP8KNnl84ETasxpG5lR3XTqs0az
|
38 |
4pJG18rbwtk22+7q38hXQv9/vRfAZH3Lx5ilG1+F0+I39miXW6ylsS37ovkdrQ97
|
39 |
rUvNasT+5GcB6jd3tXDQuOJs8UgGuBNgTjzZfrk5Y+6+Dqj2oL5ERRONOS6UN5RB
|
40 |
TYGw9KI1Rj7pRWE1gIi/fhoXbugj0DZArRC8fA3D2NEyYFIStopjI0hI3bXljFs=
|
41 |
=Z9+y
|
42 |
-----END PGP SIGNATURE----- |