search

lento / spam

Spark Project & Asset Manager
GNU General Public License v3.0
7 stars 2 forks source link

permission for assets #43

Open MrPetru opened 12 years ago

MrPetru commented 12 years ago

all assets in SPAM are owned by spam-user and when an asset is created, this are the write permission only for owner, in this situation by spam-user.

this is good ...

the problem is that we now use a mini work space to work on assets on we need the write permissions on this "mini work space" - is intended as: when a user check out an asset, spam add the write permission to this asset folder for current user. when a user release the asset is push all relevant data to repository and clear all irrelevant such as backup copy, cache, and temp file, test files.

at less we need a write permission for user group for now ... every time when a asset is published to spam.

MrPetru commented 11 years ago

this feature was useful inside spark where the same repository was shared on network hard disk. can we now ignore this modifications or can we keep this?