gmane.comp.web.zope.plone.devel

Supermodel, Dexterity Content types,named relations between content types

matthew lange — 2013-05-21T22:36:28

Returning to Plone after a bit of hiatus...I have been playing with
the supermodel schema, and I think it is really cool. I have two
questions about the way Plone is moving forward with dexterity content
types, and how they work with each other.
First, I am trying to use the titles of instances of one Dexterity
content type (dctA) to fill the choice parameters for a field in
another content type (dctB).
I see that I can iterate over the instances of  dctA, register these
titles as a vocabulary, and then use the <vocabulary > tag within
supermodel..but the latter part seems to require filesystem level
access.  I would rather not give this access to my
students--preferring to have them focus on the generation of portable
xml models.  Am I missing another more straightforward way that allows
me to call dctA titles as choices for the field directly?  I do see
from supermodel's docs that  "...we can import a choice field with a
source, provided that source can be specified via an importable dotted
name..." But I don't fully understand where my new TTP-created
dexterity content type reside in the dotted-name hierarchy. Am I
missing something simple?

Second, I would like to model via supermodel, the types of
relationships in which specific dexterity content types are capable of
engaging. It seems as though I need plone.app.relationfield for this,
but I wasn't able to find a working example of how this can (now, or
in the future) be modeled within supermodel.

If these features aren't currently possible,are they path for core
Plone/Dexterity/Supermodel development ?

Thanks,
mateolan

------------------------------------------------------------------------------
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_may

Re: enhanced collections views

Martin Aspeli — 2013-05-20T18:51:11

Hi,

(Small request: can we avoid giant images to a mimum, please? The
horizontal width of my Gmail has gone haywire ;-)

On 20 May 2013 16:22, Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/w< at >public.gmane.org> wrote:

I can buy that. It does mean the bar for usability and "future
proofing" is pretty high, though. Once something goes into core, it's
hard to take out.

So, to check that I understand: without this, it provides
UI-configurable views for folders, content items, portlets or
collections where the administrator can choose what gets rendered
(from schema or catalogue fields) and how (e.g. pagination)

That's a good start, indeed.

I think that's quite powerful. It does, however, create a dependency
between a theme and things in content space (layout of folders, items,
collections; assignments of portlets; assignments of custom views).
This makes it somewhat harder to package and propagate themes (e.g.
from dev to test to production). It may be worth thinking about how we
solve this, probably by using the plugin points in plone.app.theming
and packaging settings in the theme manifest (there's infrastructure
for this already).

First of all, the thinking here is that you configure the listing in
the tile settings, rather than referencing something that's persisted
elsewhere. Because (transient) tiles (i.e. the good kind of tile) are
configured entirely through the query string of the href that invokes
them, this is lightweight and robust: if a theme or registry setting
makes reference to a tile, the reference itself carries all the
information requires to render it correctly and there is no need to
sync up the reference to separate persistent configuration.

Again in thinking-out-loud mode, it may be interesting to experiment
with something like an overlay in the theming control panel that lets
you add/remove/change tiles associated with theme. These tiles would
then be rendered in the content (probably just one after the other in
a viewlet at the bottom of the page) for use by a Diazo rule (which
you could build using the point-and-click editor). The list of tiles
itself could be saved into portal_registry (a list-of-strings field
storing tile urls including query string parameters) or perhaps even
be kept entirely in the manifest.cfg file (against as a list of
strings in a section read by plugin configuration). With a bit more
config, the tiles could be tied to specific content types or
locations.

Not necessarily. I'm trying to think of a way to make this
configuration lightweight and isolated enough that it is predictable,
doesn't depend on infrastructure that may or may not go away in the
future, and allows for a modular style of configuration. If all we are
doing is providing 5-7 common use cases as tiles that can be inserted
and managed in a user-friendly way for use in a theme, it feels more
likely to be accepted than if we're building a bunch of new
infrastructure. I haven't looked closely at the listingviews code (at
least not for a while) to know if this is already the case, but
smaller, more precise things are more likely to end up in the core.

I think it's potentially confusing to expect people to walk around the
content space and add portlets to things for their themes to work as
expected. It feels more appropriate for this to be done in the context
where you are managing the theme (i.e. the theme editor).

Again, I'd try to make the number of concepts and moving parts as low
as possible. So, if a use case involves adding a collection, setting
up some stuff in the control panel (the listing view), setting a
property on the collection (e.g. through the 'display' menu) and then
building a Diazo rule, then that's potentially four places to go to
get to the result you want. It works, absolutely, and it's a great
tactical solution for a lot of sites right now. However, for this to
be in the core of Plone, we'd likely want it to be something you do in
only one place. My thinking above was that this "one place" is the
theme editor (presuming the primary use case is theme building). This
would suggest that you instantiate tiles from within that UI and that
all the configuration required to render the thing you want (e.g. the
query parameters for a search) live inside the configuration of that
tile, not in some other extant UI construct (a collection) that you
then reference.

That still stands, by the way. This is a fairly complex problem to
solve and there are many moving parts inside Plone that have to align.
I'm sure I haven't thought of all of them. Again why smaller, more
precise changes are preferable to sweeping ones. My first reaction
seeing http://pypi.python.org/pypi/collective.listingviews is that
"this thing does four or five different things". Of course they're all
related. And of course they're all useful to a lot of people. It's
just much harder to swallow one such thing, which potentially has
dependencies on "legacy" stuff or perhaps slightly suboptimal
engineering decisions, into the core of Plone at a time when people
are pining for a lighter core.

Martin

Re: enhanced collections views

Dylan Jay — 2013-05-20T15:22:19

On 20/05/2013, at 11:40 PM, Martin Aspeli <optilude+lists-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

because it's tightly linked to theming and collections. You can create much better themes with something like listingviews.
Although I think a way to create forms in the core to replace PFG (based on dexterity schema editor) would be a good idea I think PFG doesn't have that many interactions with other components.

good question. The custom fields is meant to be an advanced option. listing views is still very useful without using them.
It could be improved with some inline documentation or common api and by having many of the commonly used expressions preset for use in listing views (which we've already started doing)

hence why I'm bringing it to this list.
I'm very open to how to improve it and know that anything in the core has very well thought out and easy to use and that isn't hard.

It's a themer tool. Since it requires daizo changes to make it look like you want it's tightly liked to your diazo theme. The themer creates a series of views which the content editors can apply to their content.

Can you explain more what the integration with the theme editor does in the above? (there is already a listing tile that lets you pick a list template and listingviews will integrate with this).
Which problem are you trying to solve with what listing views already does? Is it that you don't want a "naked" listingview to ever be visible to an editor?

are you just talking about the part of deco which replaces portlets? or maybe there is a difference I'm missing.
Note that listingviews already works like this with portlets (since tiles and deco isn't there yet) and it works quiet well.
You create listingview template, pick a view and choose either to make it relative (uses current context) or pick a specific item to show attributes + contents of.
Make it trivial to the equivalent of a last published viewlet, or a news portlet that includes images, or a featured item portlet/time, or a carousel from a collection.

or for items (which I didn't show before)

but with deco it would more like portlets (except they'd be tiles).... and you'd just use the query building directly in the tile rather than point to a collection. Actually I should do the querybuilder part now in the existing listingview portlet since deco isn't coming anytime soon.

I'm missing something about what your idea is I'm sure. It would be great to understand your idea more.

------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: enhanced collections views

Martin Aspeli — 2013-05-20T13:40:36

Hi


On 20 May 2013 08:27, Dylan Jay <djay-n0pU0XVUApFWk0Htik3J/w< at >public.gmane.org> wrote:


It would be useful to articulate "why", i.e. why is it better for this to
be in core than in an add-on? I wonder if c.listingviews is analogous to
PloneFormGen: perhaps a "must have" add-on for a lot of sites, but not
something necessarily appropriate for core (either because it is confusing
to a casual end user, as opposed to the type of power-user [but
non-developer] you describe, or because of concerns around maintainability
and technology choice, or simply to allow more rapid innovation). That's a
genuine question, though, not an attempted put-down.



One question: How do people not familiar with the internals of Plone figure
out what to put in the 'TAL expression' boxes?



I am a bit sceptical when people say things like "some more UI love" or
"all that remains is some UI" as if that was the easy part. I think for
this kind of thing to be part of making Plone more user friendly and not
less, the UI needs to be pretty obvious. The model above is quite complex.
I think it's great for the kind of non-developer power user you're
targeting, but it may be scary to more traditional site administrators.



Yes, I agree.

One thing that strikes me is that in plone.tiles/plone.app.tiles we have a
means of building lightweight, embeddable "snippets" that can have optional
forms-driven configuration. These can then be included in themes by href
(if plone.app.blocks or at least one of its transform is enabled), or
perhaps be pulled in automatically via a ZPT looking up some configuration
(say, a viewlet looking for config stored in portal_registry).

I wonder if there's a way to extend the plone.app.theming theme editor
and/or provide a control panel to allow admins to configure one or more
tiles and embed them into a theme or assign them to a type's default view
for incorporation via a Diazo rule.

For example:

 - Go to the list of "theme tiles"
 - Click "add tile"
 - Choose "custom listing" or something else
 - Configure (ideally, we should have a small number of common use cases in
multiple tiles rather than a single uber-tile to do everything)
 - Save: stores a reference to the tile's URL in portal_registry (with
parameters embedded in the query string)
 - A viewlet (e.g. below the footer) fetches all tiles applicable to the
current page and renders them, each contained with a <div /> with a unique
id that makes it easy to target in a theme
 - In a Diazo theme, you can pull the relevant stuff through

Some variants:

 - Choose a content item where the tile is going to be shown (as opposed to
globally)
 - Allow the tile to be inherited by children if the content item is a
folder (note: the big mistake we made with portlets is that they opt-out
inherit rather than opt-in)

This has some advantages:

 - Tiles are lightweight and simple (portlets would be too awkward for this
use case, I think)
 - Add-ons can add more tiles to be used like this
 - Configuration can be managed via registry.xml (especially for transient
tiles, which 99% of tiles should be if we build them right)
 - plone.app.tiles has UI and hooks that can be used to manage tiles with
only a small bit of integration required

I'm still not 100% convinced this wouldn't be better in an add-on than in
the core - at least at first - but it feels like something worth exploring.

(Disclaimer: I've not spent a huge amount of time thinking about this, so
there may be some fatal flaw in what I'm suggesting)

Martin
------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: Tagging RF tests

Timo Stollenwerk — 2013-05-20T08:32:14

Hi Gil,

not sure if this is useful (since you can use tags if you want) but I 
use zope.testrunner's layers to group my robot tests:

https://pypi.python.org/pypi/zope.testrunner/4.3.3#test-grouping

I usually assign all my robot tests to level 2, so they are not run by 
default when calling "bin/test". I use robot tests only for acceptance 
testing and I usually end up with quite a few tests, so I don't want to 
run those tests locally (at least not all of them). Before I commit I 
don a "bin/test" to test everything except the robot tests and then run 
the robot acceptance test I'm currently working on with "bin/test -t 
1778 --all" (1778 in this example is the issue tracker number of the 
single acceptance test I want to run and part of the name of this test, 
e.g. test_acceptance_1778.robot).

This way works quite well for me, Jenkins makes sure all my 
(robot)-tests still pass (just run "bin/jenkins-test --all" on Jenkins) 
and I don't have to run them all locally.

Here is my testing.py to set the test level to "2" for all my robot tests:

testing.py
----------

from my_product.policy.testing import MY_PRODUCT_ROBOT_TESTING
from plone.testing import layered

import os
import unittest
import robotsuite


def test_suite():
     suite = unittest.TestSuite()
     current_dir = os.path.abspath(os.path.dirname(__file__))
     acceptance_dir = os.path.join(current_dir, 'acceptance')
     acceptance_tests = [
         os.path.join('acceptance', doc) for doc in
         os.listdir(acceptance_dir) if doc.endswith('.robot') and
         doc.startswith('test_')
     ]
     for acceptance_test in acceptance_tests:
         robottest = robotsuite.RobotTestSuite(acceptance_test)
         robottest.level = 2
         suite.addTests([
             layered(
                 robottest,
                 layer=MY_PRODUCT_ROBOT_TESTING,
             ),
         ])
     return suite

--

Timo

Am 17.05.2013 12:52, schrieb Gil Forcada Codinachs:


------------------------------------------------------------------------------
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

enhanced collections views

Dylan Jay — 2013-05-20T07:27:41

Hi,

I'm looking for advise on how to get something like collective.listingviews into the plone core.

- Collections is a powerful tool that lets users choose what items they want to show.
- Page templates is a powerful tool that lets plone developers create new custom views for folders, collections and items
- Diazo is a powerful tool to for a themer with control panel access to change the layout of collections

Until now there hasn't been much in between.
ie, if I'm not a plone developer but a themer or site administrator and I want to display more info about items in a collection, what can I do?
There is the table view for collections but to me it has always seemed a bit of a hack.

This is why we created collective.listingviews was created (In fact we went beyond collection views and made it so you can display a lot more info about on any content item in plone.)
So far we've found it to be very useful and have ended up using it on 4-5 different sites. Since we find it so useful, we think this with some more work, or something very similar would be a useful core feature.

For example the following page was made just using eea.facetednavigation, collective.listingviews and plone.app.theming.
- http://mhcs.nswgov.pretacloud.com/publicationsandresources#b_start=0

I realise this might not seem that useful to many of you because anyone on this list knows and loves ZPT. You might ask why do it in a more indirect and roundabout way?
The main reason is that we believe the learning curve is much lower and the chance of the user creating a view that breaks the site is less since less code is involved.
For some more UI love this could be easier and less error prone still. (note the custom expression above are an optional part).
The other reason is that separating the definition of the what attributes to list (listingview) vs how this should be laid out (diazo) allows for diazo patterns to be reused between different views and different sites (e.g. a sortable table layout). ZPT on the other hand combines presentation and attribute definition into the same file making reuse harder.

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

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

Dylan Jay — 2013-05-20T03:42:36


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.






------------------------------------------------------------------------------
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

Re: Tagging RF tests

Asko Soukka — 2013-05-17T11:45:28

Hi Gil,

filtering tests by tags _is_ supported (also for robotsuite-wrapped 
zope.testrunner compatible test suites).


Try

   bin/test --lists-tests

RF test cases with "[Tags]  firsttag  secondtag" are displayed like

   Test Name (testfile.robot) #firsttag #secondtag

Then you can run tests with #firsttag by

   bin/test -t \#firsttag

Or exclude all tests with #firsttag by

   bin/test -t \!\#firsttag


Best Regards,
Asko

Gil Forcada Codinachs wrote:

------------------------------------------------------------------------------
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

Tagging RF tests

Gil Forcada Codinachs — 2013-05-17T10:52:44

Hi all,

Robot Framework allows to tag tests in a free text way[1]. That allows you
to group tests together, run just some, exclude others, allow some tests to
fail but not others...


As I see right now, this can not be used with our plone.app.testing
infrastructure and more importantly with our integration with Jenkins.

Would be welcomed a pull request to work on this? What would you like to be
on that pull request? A way to tell the test runner which are the tags to
exclude/include which are the critical ones...?

Did anyone take a look at that so we don't step into each other?


Cheers,
Gil Forcada


[1]
http://robotframework.googlecode.com/svn/tags/robotframework-2.1/doc/userguide/RobotFrameworkUserGuide.html#tagging-test-cases
------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: coding style: ignore case when orderingimports?

Héctor Velarde — 2013-05-16T19:19:06

HV> +1

------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: coding style: ignore case when orderingimports?

Timo Stollenwerk — 2013-05-16T18:00:45

Am 16.05.2013 19:55, schrieb David Glick (Plone):

+1

Timo

------------------------------------------------------------------------------
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

Re: coding style: ignore case when orderingimports?

David Glick (Plone — 2013-05-16T17:55:38

I'm for case-sensitive, since that's what most tools probably do by 
default when you tell them to sort.
David

On 5/16/13 10:52 AM, Nejc Zupan wrote:


------------------------------------------------------------------------------
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

Re: coding style: ignore case when orderingimports?

Nejc Zupan — 2013-05-16T17:52:29

I'm for "alphabetically, regardless of case". 

z.

On 15 May 2013, at 16:58, Kees Hink wrote:


Nejc Zupan

M: +386 (0)40 730 735
E: nejc.zupan-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org

www.niteoweb.com | www.mladipodjetnik.si | www.eestec.net 


------------------------------------------------------------------------------
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

Re: Ready for merge: configurable image scaling

Kees Hink — 2013-05-16T15:53:08

Merged.

On 05/15/2013 07:42 PM, Kees Hink wrote:



------------------------------------------------------------------------------
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

Ready for merge: configurable image scaling

Kees Hink — 2013-05-15T17:42:39

Hi,

I worked on a way to make the quality of scaled images a setting in the 
image handling controlpanel.

I'd be grateful if someone could take a look at it: 
https://dev.plone.org/ticket/13337

Cheers,

Kees


------------------------------------------------------------------------------
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

coding style: ignore case when ordering imports?

Kees Hink — 2013-05-15T14:58:42

The example on 
http://developer.plone.org/reference_manuals/external/plone.api/contribute/conventions.html#grouping-and-sorting 
made me think that imports should be ordered alphabetically, regardless 
of case, so plone.api before Products.CMFCore.

To some, sorting alphabetically seems to imply capitalized modules 
first, so Products.* before plone.*.

What style shall we adopt?


------------------------------------------------------------------------------
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

Re: Git commit message convention

Jean-Michel FRANCOIS — 2013-05-15T12:09:05

Thanks for this link !

This convention is for general purpose and it don't conflict with the
angularjs one.

What I like in the angularjs convention is the first line:

type(location): subject

We will have far more information while using git log if we use this
convention.



Regards / Cordialement,
JeanMichel FRANCOIS
Find me on Twitter <http://twitter.com/toutpt> / Retrouvez moi sur
Twitter<http://twitter.com/toutpt_nantes>



2013/5/15 Kees Hink <keeshink-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>

------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: Git commit message convention

Kees Hink — 2013-05-15T11:47:40

There is one:
http://developer.plone.org/reference_manuals/external/plone.api/contribute/conventions.html#git-commit-message-style

On 05/15/2013 01:43 PM, Jean-Michel FRANCOIS wrote:



------------------------------------------------------------------------------
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

Git commit message convention

Jean-Michel FRANCOIS — 2013-05-15T11:43:59

Hi,

I have just read the git commit message convention of the AngularJS project
at http://goo.gl/iJ3E3
and I just fall in love with it.

Why not apply this to the plone core packages ? Is there already a
plone-core convention for this ?

Regards / Cordialement,
JeanMichel FRANCOIS
Find me on Twitter <http://twitter.com/toutpt> / Retrouvez moi sur
Twitter<http://twitter.com/toutpt_nantes>
------------------------------------------------------------------------------
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
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers

Re: Will you attend Ploneconf 2013?

Johannes Raggam — 2013-05-15T07:40:23

so there is something wrong with the dns servers from the two biggest
providers in austria: upc.at (primary: 195.34.133.21, secondary:
195.34.133.22) and a1.net (primary: 213.33.99.70, secondary:
80.120.17.70)

however, with a third, small, uncommercial and overall better provider
(mur.at) it works. maybe it just takes some time for the others to
synchronize.

tnx,
johannes

On Mit, 2013-05-15 at 09:30 +0200, Malthe Borch wrote:

Re: Will you attend Ploneconf 2013?

Johannes Raggam — 2013-05-15T07:26:51

hi,

i cannot connect to 
http://2013.ploneconf.org/

unknown host...

cheers, johannes

On Die, 2013-05-14 at 15:32 -0300, Marcio Mazza wrote: