Ticket #7852 (closed Feature Request: fixed)

Opened 6 years ago

Last modified 2 years ago

Promote Deliverance as the branding/"corporate ID" mechanism

Reported by: limi Owned by: zopepaul
Priority: major Milestone: Ongoing
Component: General Version: 4.1
Keywords: focusarea Cc: grahamperrin, optilude, reinout, nateaune, garbas

Description


Change History

comment:1 Changed 6 years ago by grahamperrin

  • Cc grahamperrin added

comment:2 Changed 6 years ago by optilude

  • Cc optilude added

comment:3 Changed 6 years ago by reinout

  • Cc reinout added

comment:4 Changed 6 years ago by nateaune

  • Cc nateaune added

We can share our experience using deliverance for Plone.tv. It worked but had its share of challenges.

comment:5 Changed 6 years ago by garbas

  • Cc garbas added

comment:6 Changed 6 years ago by zopepaul

Conversation for this has been going on primarily on the Deliverance mailing list, with pieces also done on the Repoze list.

In a nutshell, here is the status:

1) Handling multiple themes (as well as no-theme) was the big unmet need at the summit. This is currently working, although you have to write middleware that makes the decision.

2) Several projects have used Deliverance and funneled their needs back into a collated list.

3) Based on this, a spec for a new Deliverance has been drafted by Ian. Paul has been working on an implementation.

Most likely the biggest question mark is whether this is targeted at Plone running as part of Repoze, or using some other kind of middleware-enabler. I believe that Repoze is the target, based on conclusions from the summit. Thus, we can presume that Plone is running in a proper WSGI context.

The second biggest question mark is where configuration (e.g. choosing themes for certain Plone sites or different parts of a Plone site) should be done. For WSGI, that smells like the Paste INI file (or zope.conf). However, some people might want a configlet in the site setup.

comment:7 Changed 6 years ago by zopepaul

My writeup of the ticket says: "Thus, we can presume that Plone is running in a proper WSGI context."

While WSGI is generally endorsed for Plone (some +1, some -1, more of the former), it isn't officially endorsed. As has been made clear, the PSPS was simply information gathering, not decision making. Thus, work on this ticket will be postponed until the Plone 4 framework team is assembled and vets the tickets.

Work on Deliverance itself, and Plone-WSGI, will continue, just not under the aegis of this ticket.

comment:8 Changed 2 years ago by eleddy

  • Status changed from new to closed
  • Version set to 4.1
  • Resolution set to fixed
  • severity set to Normal

comment:9 Changed 22 months ago by davisagli

  • Component changed from Infrastructure to General
Note: See TracTickets for help on using tickets.