Autor: intrigeri Data: A: Tails user experience & user interface design Assumpte: Re: [Tails-ux] Ever-growing blueprint/ directory on the website
Hi,
sajolida wrote (28 Feb 2015 14:06:19 GMT) : > intrigeri:
>> Do we need to enforce this server-side, to forbid pushing large files,
>> possibly with a per-file-extension limit? > Given the fact that blueprints are world writable, if we want to be
> serious about that it should be enforced somehow.
OK --> #8982 (on my plate for 1.3.1) for the web interface side of things.
>> I definitely trust that mistakes will be rare, but one can *not* undo
>> such mistakes, as far as the `.git' directory size is concerned, which
>> is what I'm interested in right now... and I'd like to avoid having to
>> rewrite the Git history again in a few years, sort of. OTOH, I can
>> definitely do more interesting things than setting up Git hooks :) > Could it be low priority and "easy"?
Working on these hooks requires coordination and communication with
root@???, so I'm afraid it cannot be "Easy" --> #8983, on my plate for
1.4.1.
