https://bugzilla.wikimedia.org/show_bug.cgi?id=49494

--- Comment #17 from Nemo <[email protected]> ---
(In reply to comment #15)
> (In reply to comment #14)
> > "shellpolicy" is not only about "community consensus needed"
> 
> What else? (I can imagine a little bit, but your descriptive words might
> simply
> be helpful to improve this.)

See comment 1, comment 7 and follow links; e.g. [[m:Limits to configuration
changes]].

> >, moreover the new
> > name is too broad and vague (despite being so long) and is already causing
> > disruption (see bug 56346). I suggest reverting.
> 
> How was the old name clearer? Or any other proposal you have in mind?

The old name was clearer because it had a clear prefix, shell-, which clearly
connected this keyword to its sibling (and opposite) "shell". I suggest to keep
"shell" (or shell's new name) as prefix.
If "policy" is not a clear word, we could use "on hold". So shell-onhold for
instance.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to