Re: [Bodington-developers] Quotas Implementation

[Jon M. <jo...@te...>]

I think that's neat way of doing it. Better than quotas for people 
because it means that an individual who contributes to a course area for 
example is not using their own personal quota but if that person has a 
"my suite of rooms" resource which only they create personal stuff in, 
the scheme works just like a personal quota.
It might be nice if people with 'manage' access saw a prominent 'out of 
quota' message. Can people really, really delete uploaded files now 
(rather than mark them as deleted)? That would be essential to be able 
to recover space and get under quota again.

Although sysadmins should be allowed to go over quota they ought to be 
warned that they have done so because they may make it impossible for 
the managers of the resource to upload any files at all.

Jon


Matthew Buckett wrote:
> Request for Comment.
>
> I'm currently looking at implementing basic quotas for Bodington as we 
> are hoping to allow everyone in Bodington to be able to create their 
> own resources and this needs some management.
>
> It would be difficult to follow the traditional model of file system 
> quotas where each file has a principal owner and quotas are placed on 
> users. The reason being that Bodington doesn't have an idea of one 
> owner and implementing this isn't trivial or maybe right.
>
> The route I am probably going to take is allowing for a quota to be 
> placed on a resource and it applies to all child resources unless a 
> child has its own quota defined.
>
> I am going to initially only allow quotas to be set on a resource at 
> creation time although later on quotas should be able to be applied 
> after creation.
>
> Quotas will be able to be adjusted after they have been initially set.
>
> Sysadmin will be exempt from quotas.
>
> Quotas will apply to resources (eg you can create a total of 20 
> resource) and uploaded files (eg you can only upload 5MB of files).
>
> No hard/soft quotas in version 1 they may come at a later date.
>
> To see the quotas you need manage permission. If you have create 
> permission you can see the resource quota. If you have upload 
> permission you can see the uploaded file quota.
>
> Exceeding quota will throw a BuildingServerException subclass. Nice 
> error handling will be done at most places.
>