Re: What I'd like to see gsoc achieve: plone distributions
Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
I guess a good next step would be to try an create an example theme with default content. Perhaps an open source blog theme? Depend on one of the bloging plugins and wordpress like site and freeze it? What happens if the GS includes plugins that aren't available to activate? > On 4 Apr 2015, at 8:57 pm, Asko Soukka <[email protected]> wrote: > > David Bain wrote: >> I haven't done much in terms of contributing to the core, so forgive my >> absolute ignorance. >> Is this work solely targeted at Plone 5? > > No. Travis-CI is currently testing both c.themesitesetup and c.themefragments only with 4.3.4, but there should be no reason why they wouldn't work on all 4.x and 5.x. > > p.a.theming master and 1.2.x branches are only for 5.x. (although I've been using also 1.2.x on 4.3.x only with a revert for DL-tag removal) > > p.a.theming 1.1.x branch is for 4.x. (but may not work with jQuery >= 1.8.x). > > I have pending pull requests to fix onEnabled-hook (for c.themesitesetup) for branches 1.1.x, 1.2.x and master. Yet, the c.themesitesetup has now @@import-site-setup view for resource directories, to emulate onEnabled with current releases. > > https://github.com/plone/plone.app.theming/pull/38 > https://github.com/plone/plone.app.theming/pull/39 > https://github.com/plone/plone.app.theming/pull/40 > >> What's the fastest way to get started contributing to this? >> So far I've started the process of building from buildout.coredev using >> git clone -b 5.0 https://github.com/plone/buildout.coredev > > I've not tested this yet on Plone 5, but it this should work. > >> My best understanding from reading so far is: >> 1. Once I get my buildout up I'll have the master branch of >> plone.app.theming on a development Plone 5.0 branch. > > Yes. Or 1.1.x for Plone 4.x. > >> 2. I should create a branch of plone.app.theming and do a pull request >> when pushing changes. > > Yes. The convention seem to be name branches like "username-feature". > > Regards > Asko ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF