Re: GSOC git push pull to plone.app.theming

> That's not really the use case. Some users edit their theme inside plone and
> some don't. Some edit it on a production server or across many production
> servers. Currently we manage this by constantly exporting a theme via a zip and
> checking it in and merging into a repo all the time, which is a pain. Imagine
> how nstead you could push and pull directly with plone like you can with
> heroku.

then just write a git plugin which creates zip and pushed it to plone. like
they did for heroku. i guess that can be done in an evening. i'm definatly
going to do it when working on next plone theme.

i know it sounds nice to have whole git server implemented on top of zodb, but
seriusly you really want to maintain that? well everybody has their own ideas
i guess. I hope we(Plone) could focus more on better document management, since
thats whole thing what plone is.


--
Rok Garbas - http://www.garbas.si

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk