On 12 Jun 2015 at 11:00:30, [email protected] ([email protected](mailto:[email protected])) wrote:
Hi Caleb,
On 12 Jun 2015 at 10:28:23, Caleb James DeLisle ([email protected](mailto:[email protected])) wrote:
I think I can say without justification that changing a term which is in the XWiki developer's lexicon is going to inflict pain, however I don't see the real pain in keeping it. Certainly other names could be better and I might have chosen "root" to keep with unix standards of "Global Administrator Right" to explain that it's global to a farm.
But I don't think the self-explanitory nature of these names over "programming right" is adaquate reason to change.
Standard gage railroad track is 4 feet 8 and a half inches wide, certainly not the *best* width and indeed somewhat of an insane number, but the people who built the first trains were wagon makers and that was the width of the wagon axles because if they were not that width, they would break when running in the rutted stone roads left by the Romans, indeed that width dates all the way back to the width of a Roman war chariot... or so the story goes.
The point is that as much as existing standards might suck, "programming rights" is carved into every XWiki developer's mind just as "4 feet 8 and a half inches" is written in the ties, tunnels, switches and bridges all over the world and to propose a change to that you need a *really* good reason.
While I understand what you’re saying (however this would be just a name change!!), based on your logic we would never change anything: - we would still call “web” the notion of spaces - we wouldn’t be able to drop the concept of spaces for nested documents - etc
Now I agree that every change should be motivated, maybe I failed to explain the motivation properly.
Reason 1: "programming right” doesn’t have much to do anymore with programming ;) (it never has but that’s another matter). It’s used for securing lots of other topics. Reason 2: Every day we have people who don’t understand what “programming right” is about. They think it’s the “script” right that we wish to add. Since you’re on IRC I’m sure you’re seeing this too. The latest occurrence was yesterday night but it happens daily.
And of course: Reason 3: With the introdution of the “Script” permissions it’ll increase even more confusion (that was the main initial motivator) Thanks -Vincent
So IMO the pain point is now, not later ;)
Thanks -Vincent
On 06/12/2015 09:02 AM, [email protected] wrote:
Hi devs,
With the intoduction of http://jira.xwiki.org/browse/XWIKI-12171 (Add a script right to manage script macro execution permissions) in 7.2, we should also think about renaming what we call "Programming Right" (PR for short) since "Script" and "Programming" are close. At least to change that in the UI (and possibly even at API level by introducing new methods ands deprecating old ones).
First step would be to find a new name. I can think of: * Privilege Right (nice thing is that PR is still valid ;)) http://dictionary.reference.com/browse/privilege "a right, immunity, or benefit enjoyed only by a person beyond the advantages of most:". This would mean that people with the Privilege Right would be able to use Privileged APIs. * System Right * God Right
My preference goes to "Privilege" or "Privileged".
WDYT about 1) Changing the name 2) The new name to use if you agree with 1) ?
Thanks -Vincent