[Yanel-dev] permissions for policy edition and view on 'use-cases' realm

[Michael Wechner]

Guillaume Déflache wrote:
> Michael Wechner schrieb:
>> Guillaume Déflache wrote:
> [...]
>>> OK thanks, sorry I forgot about the .policy file.
>>>
>>> That reminds me of a remark memo made during lunch recently: this 
>>> policy file is hidden under Unix and can easily get forgotten,
>>
>> not if it is documented
>
> I'd argue one can still forget about it even then,

yes, but that is no excuse not to document it
> and it is not really "discoverable".

ls -la on UNIX
>
>
>>> maybe we should allow for an alternative name like "policy" without 
>>> the leading dot (or COLLECTION.policy so that there is still an 
>>> extension) so that it can be always visible?
>>> Ditto for .yarep files BTW.
>>
>> The problem is re conflicts. What if you have directory called 
>> COLLECTION? Or ROOT or whatever.
>
> Granted, and making that prefix configurable would complicate things 
> more and may even not be sufficient as one might need different 
> prefixes for different directory levels in case a conflict appears 
> later on.
>
> So maybe 'policy' would be the only sensible alternative?

that's not really consistent, then rather something like

_policy for "directories"

and

FILE_policy for "files"

but I really think with .policy we are fine and anyone who is interested 
how this works and read the documentation
will have no trouble with .policy

You might want to add a bugzilla entry for enhancement if you really 
care for this, such that we can later pick it up.
>
>
>> Btw, SVN and GIT use the same principle.
>
> Sure but in our case we have both a hidden file (.policy) and 
> non-hidden files (*.policy) which leads you to think you see all of 
> them when doing a simple `ls`.

that's why I am doing ls -la as pointed out above ;-)