GSOC git push pull to plone.app.theming

classic Classic list List threaded Threaded
29 messages Options
12
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

GSOC git push pull to plone.app.theming

Hi,

Just wanted to highlight one of the ideas I posted up for GSOC on http://plone.org/events/summer-of-code/2013/ideas-list
The nice thing about it, is it doesn't require a lot of Plone knowledge but would be hugely helpful to Plone I think.

Summary
Currently there are two ways to develop themes for plone. Using eggs which requires full access the filesystem so has security implications for shared environments, or via zip files, which makes it hard to track versions and tedious to move to and from development, staging and production.

Implementation
The end result of this task would be to allow a developer to push a git repo with the same format as a diazo zip and have to appear in the theming control panel. Any changes they push happen to the theme live. If they decide to edit the theme via the theme editor then those changes are recorded back in git and can be pulled. If possible, the user should be able to switch branches easily in the theme editor and checkout multiple braches into different themes so they can test different branches at the same time.

The system should work with zeo, should be easy to install but doesn't have to be implemented using python inside Zope.

Skills
Knowledge of Git, a fair amount of Python and some basic Zope

Mentors
Dylan Jay, or any core developer

Aims
Probably a pull request to the theme editor for inclusion in a later version of Plone

---
Dylan Jay
Technical Solutions Manager
PretaWeb: Multisite Performance Support
P: +612 80819071 | M: +61421477460 | twitter.com/pretaweb | linkedin.com/in/djay75




------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
johannes raggam johannes raggam
Reply | Threaded
Open this post in threaded view
|

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

Hi,

nice idea and great to have github repos integrated like Dropbox.

I've did this for some projects with Dropbox, which worked out quite
nicely. The designer got immediate feedback about changes to styles and
templates. We did that with plone.app.theming too. See this blog post
for some info:
http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance

Regarding automatic pushing and pulling to/from github repos as if they
were Dropbox folders, Sparkleshare is a programm, which does it:
http://sparkleshare.org/


Cheers,
Johannes


On Sam, 2013-04-27 at 09:35 +1000, Dylan Jay wrote:

> Hi,
>
> Just wanted to highlight one of the ideas I posted up for GSOC on http://plone.org/events/summer-of-code/2013/ideas-list
> The nice thing about it, is it doesn't require a lot of Plone knowledge but would be hugely helpful to Plone I think.
>
> Summary
> Currently there are two ways to develop themes for plone. Using eggs which requires full access the filesystem so has security implications for shared environments, or via zip files, which makes it hard to track versions and tedious to move to and from development, staging and production.
>
> Implementation
> The end result of this task would be to allow a developer to push a git repo with the same format as a diazo zip and have to appear in the theming control panel. Any changes they push happen to the theme live. If they decide to edit the theme via the theme editor then those changes are recorded back in git and can be pulled. If possible, the user should be able to switch branches easily in the theme editor and checkout multiple braches into different themes so they can test different branches at the same time.
>
> The system should work with zeo, should be easy to install but doesn't have to be implemented using python inside Zope.
>
> Skills
> Knowledge of Git, a fair amount of Python and some basic Zope
>
> Mentors
> Dylan Jay, or any core developer
>
> Aims
> Probably a pull request to the theme editor for inclusion in a later version of Plone
>
> ---
> Dylan Jay
> Technical Solutions Manager
> PretaWeb: Multisite Performance Support
> P: +612 80819071 | M: +61421477460 | twitter.com/pretaweb | linkedin.com/in/djay75
>
>
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers



------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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


On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:

> Hi,
>
> nice idea and great to have github repos integrated like Dropbox.
>
> I've did this for some projects with Dropbox, which worked out quite
> nicely. The designer got immediate feedback about changes to styles and
> templates. We did that with plone.app.theming too. See this blog post
> for some info:
> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance

Hey thats a neat trick.
In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

>
> Regarding automatic pushing and pulling to/from github repos as if they
> were Dropbox folders, Sparkleshare is a programm, which does it:
> http://sparkleshare.org/
>
>
> Cheers,
> Johannes
>
>
> On Sam, 2013-04-27 at 09:35 +1000, Dylan Jay wrote:
>> Hi,
>>
>> Just wanted to highlight one of the ideas I posted up for GSOC on http://plone.org/events/summer-of-code/2013/ideas-list
>> The nice thing about it, is it doesn't require a lot of Plone knowledge but would be hugely helpful to Plone I think.
>>
>> Summary
>> Currently there are two ways to develop themes for plone. Using eggs which requires full access the filesystem so has security implications for shared environments, or via zip files, which makes it hard to track versions and tedious to move to and from development, staging and production.
>>
>> Implementation
>> The end result of this task would be to allow a developer to push a git repo with the same format as a diazo zip and have to appear in the theming control panel. Any changes they push happen to the theme live. If they decide to edit the theme via the theme editor then those changes are recorded back in git and can be pulled. If possible, the user should be able to switch branches easily in the theme editor and checkout multiple braches into different themes so they can test different branches at the same time.
>>
>> The system should work with zeo, should be easy to install but doesn't have to be implemented using python inside Zope.
>>
>> Skills
>> Knowledge of Git, a fair amount of Python and some basic Zope
>>
>> Mentors
>> Dylan Jay, or any core developer
>>
>> Aims
>> Probably a pull request to the theme editor for inclusion in a later version of Plone
>>
>> ---
>> Dylan Jay
>> Technical Solutions Manager
>> PretaWeb: Multisite Performance Support
>> P: +612 80819071 | M: +61421477460 | twitter.com/pretaweb | linkedin.com/in/djay75
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Try New Relic Now & We'll Send You this Cool Shirt
>> New Relic is the only SaaS-based application performance monitoring service
>> that delivers powerful full stack analytics. Optimize and monitor your
>> browser, app, & servers with just a few lines of code. Try New Relic
>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>> _______________________________________________
>> Plone-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
johannes raggam johannes raggam
Reply | Threaded
Open this post in threaded view
|

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

On Sam, 2013-04-27 at 10:08 +1000, Dylan Jay wrote:
> On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:

> > http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance

> Hey thats a neat trick.
> In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

i understand... thats quite interesting!
in that case my suggestions won't help you much.
 
> > Regarding automatic pushing and pulling to/from github repos as if they
> > were Dropbox folders, Sparkleshare is a programm, which does it:
> > http://sparkleshare.org/




------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
David Glick (Plone) David Glick (Plone)
Reply | Threaded
Open this post in threaded view
|

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

In reply to this post by Dylan Jay
On 4/26/13 5:08 PM, Dylan Jay wrote:

> On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:
>
>> Hi,
>>
>> nice idea and great to have github repos integrated like Dropbox.
>>
>> I've did this for some projects with Dropbox, which worked out quite
>> nicely. The designer got immediate feedback about changes to styles and
>> templates. We did that with plone.app.theming too. See this blog post
>> for some info:
>> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance
> Hey thats a neat trick.
> In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

The git idea is cool, but wouldn't it be simpler to just arrange fs
permissions so a TTW editor can make changes to stuff on the filesystem?
Your proposal seems suboptimal for the editing-on-the-filesystem case
since you have to remember to commit and push before you can see the
effect of your changes in Plone.

Martin and Franco started something along these lines at the ploneconf
2012 sprint, but I can't remember what it's called.
David

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Martin Aspeli Martin Aspeli
Reply | Threaded
Open this post in threaded view
|

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




On 27 April 2013 19:40, David Glick (Plone) <[hidden email]> wrote:
On 4/26/13 5:08 PM, Dylan Jay wrote:
> On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:
>
>> Hi,
>>
>> nice idea and great to have github repos integrated like Dropbox.
>>
>> I've did this for some projects with Dropbox, which worked out quite
>> nicely. The designer got immediate feedback about changes to styles and
>> templates. We did that with plone.app.theming too. See this blog post
>> for some info:
>> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance
> Hey thats a neat trick.
> In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

The git idea is cool, but wouldn't it be simpler to just arrange fs
permissions so a TTW editor can make changes to stuff on the filesystem?
Your proposal seems suboptimal for the editing-on-the-filesystem case
since you have to remember to commit and push before you can see the
effect of your changes in Plone.

I also worry that making a ZODB-backed Git could be very difficult to do. It feels more complex than any other GSoC project we've had, which makes me sceptical.
 
Martin and Franco started something along these lines at the ploneconf
2012 sprint, but I can't remember what it's called.


It would be cool to get some traction on this again. There's quite a lot that could be done, I think.

Martin 

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Kevin Kalupson-2 Kevin Kalupson-2
Reply | Threaded
Open this post in threaded view
|

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

Putting git aside for the moment, what about  "Install Theme from Remote Server" as an idea?

On Apr 27, 2013 2:58 PM, "Martin Aspeli" <[hidden email]> wrote:



On 27 April 2013 19:40, David Glick (Plone) <[hidden email]> wrote:
On 4/26/13 5:08 PM, Dylan Jay wrote:
> On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:
>
>> Hi,
>>
>> nice idea and great to have github repos integrated like Dropbox.
>>
>> I've did this for some projects with Dropbox, which worked out quite
>> nicely. The designer got immediate feedback about changes to styles and
>> templates. We did that with plone.app.theming too. See this blog post
>> for some info:
>> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance
> Hey thats a neat trick.
> In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

The git idea is cool, but wouldn't it be simpler to just arrange fs
permissions so a TTW editor can make changes to stuff on the filesystem?
Your proposal seems suboptimal for the editing-on-the-filesystem case
since you have to remember to commit and push before you can see the
effect of your changes in Plone.

I also worry that making a ZODB-backed Git could be very difficult to do. It feels more complex than any other GSoC project we've had, which makes me sceptical.
 
Martin and Franco started something along these lines at the ploneconf
2012 sprint, but I can't remember what it's called.


It would be cool to get some traction on this again. There's quite a lot that could be done, I think.

Martin 

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
David Glick (Plone) David Glick (Plone)
Reply | Threaded
Open this post in threaded view
|

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

On 4/27/13 12:03 PM, Kevin Kalupson wrote:
>
> Putting git aside for the moment, what about "Install Theme from
> Remote Server" as an idea?
>
>
You mean like https://github.com/enfold/ploud.themegallery ?

I'm a bit leery of encouraging people to install 3rd-party themes from
arbitrary sources, since they could be used to inject cross-site
scripting attacks.
David

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Kevin Kalupson-2 Kevin Kalupson-2
Reply | Threaded
Open this post in threaded view
|

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

and providing a list of known good / safe themes could be a bit of a burden, i suppose. someone would have to manage it.
On Apr 27, 2013 3:08 PM, "David Glick (Plone)" <[hidden email]> wrote:
>
> On 4/27/13 12:03 PM, Kevin Kalupson wrote:
>>
>>
>> Putting git aside for the moment, what about "Install Theme from Remote Server" as an idea?
>>
>>
> You mean like https://github.com/enfold/ploud.themegallery ?
>
> I'm a bit leery of encouraging people to install 3rd-party themes from arbitrary sources, since they could be used to inject cross-site scripting attacks.
> David


------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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

In reply to this post by Martin Aspeli


On 28/04/2013, at 4:57 AM, Martin Aspeli <[hidden email]> wrote:




On 27 April 2013 19:40, David Glick (Plone) <[hidden email]> wrote:
On 4/26/13 5:08 PM, Dylan Jay wrote:
> On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:
>
>> Hi,
>>
>> nice idea and great to have github repos integrated like Dropbox.
>>
>> I've did this for some projects with Dropbox, which worked out quite
>> nicely. The designer got immediate feedback about changes to styles and
>> templates. We did that with plone.app.theming too. See this blog post
>> for some info:
>> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance
> Hey thats a neat trick.
> In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.

The git idea is cool, but wouldn't it be simpler to just arrange fs
permissions so a TTW editor can make changes to stuff on the filesystem?

Your proposal seems suboptimal for the editing-on-the-filesystem case
since you have to remember to commit and push before you can see the
effect of your changes in Plone.

I'm thinking of a hosted server that's in production, not developing locally on a single instance. Supporting the local development case could be done too but is less important. 




I also worry that making a ZODB-backed Git could be very difficult to do. It feels more complex than any other GSoC project we've had, which makes me sceptical.

I agree a zodb backed git would be way to hard to implement. What I'd suggest is doing it like heroku and others do. Push to a server, use post commit hooks and WebDAV to sync the head into zope. 
In the reverse direction we implement events on resource items (which are currently missing) and on any change in zodb resources use something like zeromq to write that as a commit to the single git repo on the hosted server. 
Obviously not ideal in terms of infrastructure setup requirements but achievable. 

 
Martin and Franco started something along these lines at the ploneconf
2012 sprint, but I can't remember what it's called.


It would be cool to get some traction on this again. There's quite a lot that could be done, I think.

Martin 

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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

In reply to this post by Kevin Kalupson-2
On 28/04/2013, at 5:03 AM, Kevin Kalupson <[hidden email]> wrote:

> Putting git aside for the moment, what about  "Install Theme from Remote Server" as an idea?

One possibility is to allow remote theme browsing built into the theme editor.
ie, you could select which themes in the theming control panel you want public. Then you can give out your url of the Plone theming control panel to others.
They then go into their theming control panel and add that url into the list of remote theme repositories. Then they can browse remote themes just as they would local themes.
Basically theme gallery is merged into plone.app.theming.
It would make it very easy to move themes between staging and production as well as setup a public theme repositories such as on Plone.org.
If themes could be pushed to a remote repository instead of pulled (ie by entering credentials as well as the url) then you could push a theme from your local development plone instance to your public server.

However this still doesn't help with managing different versions of the same theme. currently most people keep creating dated copies which becomes confusing fast.
For that I think you still need some method of easily synching to source control.

A ZODB backed Git might not be difficult to do. Dulwich is a mature pure python implementation of git and here is their implementation of the git smart http protocol
https://github.com/jelmer/dulwich/blob/master/dulwich/web.py

Also, note that Acquia already has this type of functionality for drupal for both content and code.




>
> On Apr 27, 2013 2:58 PM, "Martin Aspeli" <[hidden email]> wrote:
>
>
>
> On 27 April 2013 19:40, David Glick (Plone) <[hidden email]> wrote:
> On 4/26/13 5:08 PM, Dylan Jay wrote:
> > On 27/04/2013, at 9:55 AM, Johannes Raggam <[hidden email]> wrote:
> >
> >> Hi,
> >>
> >> nice idea and great to have github repos integrated like Dropbox.
> >>
> >> I've did this for some projects with Dropbox, which worked out quite
> >> nicely. The designer got immediate feedback about changes to styles and
> >> templates. We did that with plone.app.theming too. See this blog post
> >> for some info:
> >> http://bluedynamics.com/articles/johannes/drop-dead-dropbox-doings-with-deliverance
> > Hey thats a neat trick.
> > In this case however we wanted it to go both ways, so the theme has to be in the ZODB not just the filesystem. That allows designers the choice of using the TTW theme editor or using git/fs/dropbox on a live server. Currently you have to choose between TTW or fs based development which is a pain in the neck.
>
> The git idea is cool, but wouldn't it be simpler to just arrange fs
> permissions so a TTW editor can make changes to stuff on the filesystem?
> Your proposal seems suboptimal for the editing-on-the-filesystem case
> since you have to remember to commit and push before you can see the
> effect of your changes in Plone.
>
> I also worry that making a ZODB-backed Git could be very difficult to do. It feels more complex than any other GSoC project we've had, which makes me sceptical.
>  
> Martin and Franco started something along these lines at the ploneconf
> 2012 sprint, but I can't remember what it's called.
>
> I guess you're thinking about https://github.com/collective/collective.customizationseditor
>
> It would be cool to get some traction on this again. There's quite a lot that could be done, I think.
>
> Martin
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr_______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
krishnatejaperannagari krishnatejaperannagari
Reply | Threaded
Open this post in threaded view
|

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

In reply to this post by Dylan Jay
Hi sir,

          My name is krishna teja perannagari(krishnatejaperannagari@gmail.com). I am studying Computer science in JNTU college of Engineering,Hyderabad.If you want to know about me this is my linkedin profile(http://www.linkedin.com/pub/krishna-teja-perannagari/73/914/339).

          I learnt how to use Zope and plone recently for this project.When i was browsing for a good way of implementing this i found these two things:
1.How to use github as host provider(http://alexcican.com/post/guide-hosting-website-dropbox-github/)
2.How to use the power of github in our app etc (http://developer.github.com/v3/)

        Is this possible to implement in the plone too.Since i dont know much about the internal code implementation of github i am asking you.We can refer to git hub folders for theme and then add the github api to see how changes to theme are recorded back to the git hub

      Please send me a reply to my mail address(krishnatejaperannagari@gmail.com) or post it in this thread.Looking forward to hear from you.
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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

On 4 Mar 2014, at 12:47 am, krishnatejaperannagari <[hidden email]> wrote:

> Hi sir,
>
>          My name is krishna teja
> perannagari([hidden email]). I am studying Computer
> science in JNTU college of Engineering,Hyderabad.If you want to know about
> me this is my linkedin
> profile(http://www.linkedin.com/pub/krishna-teja-perannagari/73/914/339).
>
>          I learnt how to use Zope and plone recently for this project.When
> i was browsing for a good way of implementing this i found these two things:
> 1.How to use github as host provider(
> http://alexcican.com/post/guide-hosting-website-dropbox-github/
> <http://alexcican.com/post/guide-hosting-website-dropbox-github/>  )
> 2.How to use the power of github in our app etc (
> http://developer.github.com/v3 <http://developer.github.com/v3>  /)
>
>        Is this possible to implement in the plone too.Since i dont know
> much about the internal code implementation of github i am asking you.We can
> refer to git hub folders for theme and then add the github api to see how
> changes to theme are recorded back to the git hub
>
>      Please send me a reply to my mail
> address([hidden email]) or post it in this thread.Looking
> forward to hear from you.


Hi,

I think you fundamentally misunderstand how Plone works, and how git integration with plone would work. I think you would need to go back and understand a how CMS's work, how python and the ZODB works before tackling this tasks.

https://github.com/collective/plone.gitpush


>
>
>
> --
> View this message in context: http://plone.293351.n2.nabble.com/GSOC-git-push-pull-to-plone-app-theming-tp7564752p7570382.html
> Sent from the Core Developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
krishnatejaperannagari krishnatejaperannagari
Reply | Threaded
Open this post in threaded view
|

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

This post was updated on .
Thanks for the information sir. Just wanna ask you few questions:

1.When we make changes to the theme are those changes saved to the rules.xml, html, css files that are present in the theme folder  or are they stored in the zodb files like data.fs that can be opened only by zope interface.

2.the main objective is to use git instead of the file-system and to provide all the functionality that are provided by the normal filesystem along with the additional git features.

3.If i am not wrong u are using dulwich to interact with git.can we use dulwich to send authenticate send and receive data from git.cant we use the git api to serve this purpose instead of dulwich because it provides many features.

looking forward to hear from you.,
 
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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


On 5 Mar 2014, at 8:50 pm, krishnatejaperannagari <[hidden email]> wrote:

> Thanks for the information sir. Just wanna ask you few questions:
>
> 1.When we make changes to the theme are those changes saved to the
> rules.xml, html, css files that are present in the theme folder  or are they
> stored in the zodb files like data.fs that can be opened onlt by zope
> interface.

I'm not sure what you mean. Any changes you make via the plone.app.theming web interface are already saved to the ZODB not to files on a disk. The goal here is to also save them as a commit in a ZODB git repository that can then be pulled from and also pushed to.

>
> 2.Went through the code you sent me.Git hub provides an api
> http://developer.github.com/v3/ <http://developer.github.com/v3/>  that uses
> the http protocol to interact with the files and it canbe  used with
> python.I guess using this api to send and receive data from git would be a
> good idea. What is your opinion regarding this.

I'm curious why do you think github has relevance to this task?

>
> looking forward to hear from you.,
>
>
>
>
> --
> View this message in context: http://plone.293351.n2.nabble.com/GSOC-git-push-pull-to-plone-app-theming-tp7564752p7570404.html
> Sent from the Core Developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Guido Stevens Guido Stevens
Reply | Threaded
Open this post in threaded view
|

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

On 05/03/14 13:22, Dylan Jay wrote:
>
> On 5 Mar 2014, at 8:50 pm, krishnatejaperannagari <[hidden email]> wrote:
>> 2.Went through the code you sent me.Git hub provides an api
>> http://developer.github.com/v3/ <http://developer.github.com/v3/>  that uses
>> the http protocol to interact with the files and it canbe  used with
>> python.I guess using this api to send and receive data from git would be a
>> good idea. What is your opinion regarding this.
>
> I'm curious why do you think github has relevance to this task?

Krishnatejaperannagari, you should use the git protocol directly to
interact with and replicate git respositories. Not a http API wrapper
around the git protocol.

:*CU#
--
     Guido Stevens  |  +31.43.3618933  |  http://cosent.nl

     s o c i a l   k n o w l e d g e   t e c h n o l o g y


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
krishnatejaperannagari krishnatejaperannagari
Reply | Threaded
Open this post in threaded view
|

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

This post was updated on .
In reply to this post by Dylan Jay
CONTENTS DELETED
The author has deleted this message.
Guido Stevens Guido Stevens
Reply | Threaded
Open this post in threaded view
|

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

On 07/03/14 04:08, krishnatejaperannagari wrote:
> Sorry sir,i got some misconceptions regarding the idea,So i am
> sending this mail to see if i got the idea right.its a bit lengthy
> because i want to check if i am correct or not:

There's a few issues with your approach. Especially:

> 5.Git also uses the object based storage approach and hence it
> doesnt  create any problems when used in combination with zodb or zeo.

This is a "heroic assumption" i.e. very likely untrue.

Git is a file-based object store. Dulwich uses that file-based object
store. Plone uses ZODB which is also a file-based object store, but it's
a *different* object store. Incompatible.

You cannot manipulate Data.fs as if it was just a file in git. Well you
can but that doesn't make sense. You cannot manipulate git files in the
ZODB.

The most sane route would be possibly to manipulate the git trees
outside of the ZODB. And maybe use git replication, not ZEO replication,
at a later stage.

:*CU#
--
     Guido Stevens  |  +31.43.3618933  |  http://cosent.nl

     s o c i a l   k n o w l e d g e   t e c h n o l o g y


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Martin Aspeli-3 Martin Aspeli-3
Reply | Threaded
Open this post in threaded view
|

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

Not sure I've grokked all of the use cases here, but maybe it would be better to allow manipulation of file system files (eg resources/theme/*) in the theme editor (which would be pretty easy but will require careful security considerations) and use dulwch on those?

Trying to implement the git protocol with zodb blobs as backing storage sounds inanely complicated and error probe and unlikely to remain maintainable. git talks files :)

Martin

Sent from Mailbox for iPhone


On Fri, Mar 7, 2014 at 4:14 PM, Guido Stevens <[hidden email]> wrote:

On 07/03/14 04:08, krishnatejaperannagari wrote:
> Sorry sir,i got some misconceptions regarding the idea,So i am
> sending this mail to see if i got the idea right.its a bit lengthy
> because i want to check if i am correct or not:

There's a few issues with your approach. Especially:

> 5.Git also uses the object based storage approach and hence it
> doesnt create any problems when used in combination with zodb or zeo.

This is a "heroic assumption" i.e. very likely untrue.

Git is a file-based object store. Dulwich uses that file-based object
store. Plone uses ZODB which is also a file-based object store, but it's
a *different* object store. Incompatible.

You cannot manipulate Data.fs as if it was just a file in git. Well you
can but that doesn't make sense. You cannot manipulate git files in the
ZODB.

The most sane route would be possibly to manipulate the git trees
outside of the ZODB. And maybe use git replication, not ZEO replication,
at a later stage.

:*CU#
--
Guido Stevens | +31.43.3618933 | http://cosent.nl

s o c i a l k n o w l e d g e t e c h n o l o g y


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers



------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
Dylan Jay Dylan Jay
Reply | Threaded
Open this post in threaded view
|

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

In reply to this post by Guido Stevens


On 8 Mar 2014 02:12, "Guido Stevens" <[hidden email]> wrote:
>
> On 07/03/14 04:08, krishnatejaperannagari wrote:
> > Sorry sir,i got some misconceptions regarding the idea,So i am
> > sending this mail to see if i got the idea right.its a bit lengthy
> > because i want to check if i am correct or not:
>
> There's a few issues with your approach. Especially:
>
> > 5.Git also uses the object based storage approach and hence it
> > doesnt  create any problems when used in combination with zodb or zeo.
>
> This is a "heroic assumption" i.e. very likely untrue.
>
> Git is a file-based object store. Dulwich uses that file-based object
> store. Plone uses ZODB which is also a file-based object store, but it's
> a *different* object store. Incompatible.

Actually dulwich has two storage models , file based and memory based. The memorystore is very similar to how zodb works so I'd suggest implementing based on that.
The existing code is based on that idea.

>
> You cannot manipulate Data.fs as if it was just a file in git. Well you
> can but that doesn't make sense. You cannot manipulate git files in the
> ZODB.
>
> The most sane route would be possibly to manipulate the git trees
> outside of the ZODB. And maybe use git replication, not ZEO replication,
> at a later stage.
>
> :*CU#
> --
>      Guido Stevens  |  +31.43.3618933  |  http://cosent.nl
>
>      s o c i a l   k n o w l e d g e   t e c h n o l o g y
>
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Plone-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/plone-developers


------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
12