On Sat, Feb 16, 2013 at 6:04 AM, Jonathan Aquilina <[email protected]> wrote: > If I am understanding the current situation correctly the issue is the size > of the images in terms of uploads and size allowed on the wiki. Think of it > this way using version control would allow us to evolve the images as the > website changes etc., but not only that it will build up a nice repository > in terms of media that can be used on other aspects of website projects at > the TDF.
One of the issues with git is that one can't commit to a shallow clone, or grab just a piece of the working tree. We could do all kinds of fun, hackish things with git filter-branch, but then we'd be adding all kinds of work and merge questions. That being said, I don't know how much media we actually work with each year. With disk space so cheap, perhaps it's not unreasonable to require a couple of GB free to grab the repo. We could always provide a copy of the repo online, and we could also break history at some point, if necessary. I haven't taken a look at TortoiseGit in a while, but I think it's working decently well. Same for the mac Git gui stuff. Of course, we still need to consider the best way to get people up and running on this type of system. The big benefit for us is that the current alternative is the wiki, so people might be happy to deal with a bit of a learning curve if git gives them the flexibility that the wiki doesn't! :-) It would be helpful to know what tools we've tried out so far (e.g. Alfresco or a WebDAV server), and why a particular tool failed to meet our needs. --R -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
