On Sun, 1 Dec 2013 11:55:07 +0100
Michal Hrusecky
Rajko - 16:09 29.11.13 wrote:
On Fri, 29 Nov 2013 11:22:53 +0100 Richard Brown
wrote: ... * Version control. ... ownCloud can somehow do that, although not real revisions like git and probably old revisions will be visible only on web. Haven't tested.
Can you test it? I would do that, but my time constrains work against. I have convincing experience that taking sizable obligations like this without being previously exposed to similar problems can delay project and frustrate everybody, including me. The basic need is a very simple version control, just to prevent destruction of old work in case of file name collision, but ability that admin can remove old files. Nothing fancier then MediaWiki provides for files. ...
* GUI as management tool. Artists are visual minds and giving them CLI will work with very few of them. - we don't have visual tool (?) + some people look for YaST modules to work on, or to create new ones. If we act fast to get their attention, then we can use their enthusiasm to fix one long standing problem for more contributions.
ownCloud has official GUI client, but being webdav, there are other GUI/CLI clients available.
While freedom to use whatever works best for you is precious, having unified solution helps documentation writers, online helpers and packagers.
* to prevent configuration problems later when you want to expand your interest to other art repos, directory structure on the web server is replicated in full, but only current interest is populated, or synchronized.
No. But you can always add another directory to be synchronized.
It seems to me that it is just ownCloud configuration. If it works for instance as SpiderOak, then it is just configuration option that can be packaged as default for artists version of ownCloud.
* included instructions, or binary, to create desktop links to populated repos which will allow to have your artwork at hand.
Not sure what you mean by that. Desktop links to directories you have on your disk? Depends on DE, but definitely independent of solution used.
Yes they are DE dependant, but we have to provide help how to create them, or have packaged some that everybody needs as a part of artwork team package. Template desktop link to directory is one of them.
* server layout (directory structure ?) ** User space for individual experiments with ability to link, or copy file to official ones. Per topic directories, like: ** system startup ** GNOME ** KDE ** Applications ** scripts and binaries
Independent of solution used.
Independent of server side solution, but it has to be provided. User space where other have restricted access and the only admin is user. Public space where even web side admins can't remove stuff permanently, like in a wiki. Articles in a wiki can be permanently deleted only by manipulating database, not from web interface.
* Any more? Please expand.
This is still what we need. Tell about your workflow and your vision how ownCloud can help you. Write with as many details as you can, including use of public services like Dropbox, Photobucket, Flickr, paste sites, git, svn, applications in use, problems with applications. I think that all of this can help us to create solution that will work for everybody with minimum compromises and need to rework infrastructure later. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org