<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework">
    <title>gmane.comp.web.zope.plone.teams.framework</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3846"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3845"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3844"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3843"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3842"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3841"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3840"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3839"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3838"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3837"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3836"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3835"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3834"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3833"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3855">
    <title>Todays FWT meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3855</link>
    <description>&lt;pre&gt;Looks like that todays security patch caused more work than supposed -
we were only three: Andrew, Ross and I.

We canceled the meeting. I suppose to hold the next one next week:
Tuesday, 25th June, again 19:00 UTC.

I'll chair the next one again. The next one after the next one should be
chaired by someone else.

Please review, vote, do the championing work, encourage, read, code,
relax.

Best,
Johannes


&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-18T19:44:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3853">
    <title>Re: Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3853</link>
    <description>&lt;pre&gt;

We are working for the last few weeks on the diazo twitter bootstrap
theme (https://github.com/RedTurtle/diazotheme.bootstrap - a
kagesenshi repo fork)

The goal is to:
 * fix all the UI bugs
(https://github.com/RedTurtle/diazotheme.bootstrap/issues)
 * make sure all Plone base templates are bootstrap compatible
 * make sure most popular Plone add'ons are working correctly
 * make it extensible using less
(https://github.com/RedTurtle/diazotheme.bootstrap/issues/3)

a.


--
Andrew Mleczko - RedTurtle Technology
web site: www.redturtle.it
e-mail: amleczko-yzwUTSi0rH+GzLJY+7CQzQ&amp;lt; at &amp;gt;public.gmane.org
phone: +39 0532 1915958
fax: +39 0532 287070
&lt;/pre&gt;</description>
    <dc:creator>Andrew Mleczko</dc:creator>
    <dc:date>2013-06-18T08:08:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3852">
    <title>Re: reminder for our meeting tomorrow</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3852</link>
    <description>&lt;pre&gt;
hi, it's
https://plus.google.com/hangouts/_/f9f7b5c7a9ad952f1a63c3c350598ffd0badd7b6

the hangout is also linked in the google calendar entry.



&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-18T07:23:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3850">
    <title>Re: reminder for our meeting tomorrow</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3850</link>
    <description>&lt;pre&gt;Hey Johannes, can you send the G+ hangout url ?

Thanks


On Mon, Jun 17, 2013 at 5:32 AM, Johannes Raggam &amp;lt;dev-//MPyowsN087nVVRfYWAjw&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

&lt;/pre&gt;</description>
    <dc:creator>Franco Pellegrini</dc:creator>
    <dc:date>2013-06-17T19:02:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3849">
    <title>reminder for our meeting tomorrow</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3849</link>
    <description>&lt;pre&gt;Dear people of the Framework Team!

This is just a friendly reminder for our meeting tomorrow, 17th June
2013 at 21:00 CET (19:00 UTC).

Despite the security team also postponed the upcoming Plone hotfix
release for tomorrow and the postponement of our meeting last week was a
bit pointless, I propose to have the meeting tomorrow as planned to
follow up our FWT work - unless a fair amount of votes against the
meeting is given.

Have a nice day,
Johannes Raggam


&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-17T08:32:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3848">
    <title>Re: [Plone-developers] Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3848</link>
    <description>&lt;pre&gt;If we didn't have so much !&amp;lt; at &amp;gt;#$ css I think the way people deal with theming would dramatically change. I personally never override, and instead just make stronger selectors in my own css.  This is the right way™... but I know that the use case and skills make people do otherwise. Like you say below, switching to a more modern framework will help immensely. I feel like people are still clamoring for the old school base_properties and we can recreate that "feeling" with different tools. Additionally, a modern theme to begin with should reduce the number of customizations.

FYI, for Plone 5 you will not be required to switch to the new theme at all. This will be the OOB theme for new sites.  

I agree here 100%. We need some serious CSS vision and this is one place where we haven't had a lot of strong opinions step up (mine are mildly spicy). I'd love to see this thread turn into the type of discussion that occurred over javascript. If you (or anyone) thinks they have a grand vision for modernizing the Plone &lt;/pre&gt;</description>
    <dc:creator>Elizabeth Leddy</dc:creator>
    <dc:date>2013-06-15T17:31:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3846">
    <title>Plone 5</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3846</link>
    <description>&lt;pre&gt;So, as you've likely noticed, we spent a lot time of talking about Plone 5 during the recent Plone Symposium Midwest. I think we've reached the point where can really start prioritizing concepts for a major release. Obviously, any changes need to go through the Framework Team for final approval, but I've got a bully pulpit and I'm not afraid to use it. 

Here's how I'd like to see development focused over the near term:

 * Plone 5 ships with Dexterity as its default content type story. 
    * Dexterity versions of plone.app.event and plone.app.collection
    * Better set of widgets (plone.app.widgets)
    * Products.Archetypes, Products.ATContentTypes, archetypes.schemaextender remain available as add-ons for older content
    * Full multilingual story available (plone.app.multilingual)

* Plone 5's UI gets an extensive overhaul.
    * Diazo becomes the default theming story
    * Fewer CSS files makes finding and overriding easier
    * No more !important in its CSS
    * Editing interface is separated fro&lt;/pre&gt;</description>
    <dc:creator>Eric Steele</dc:creator>
    <dc:date>2013-06-14T21:57:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3845">
    <title>Re: Shared Folder on PAM</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3845</link>
    <description>&lt;pre&gt;Ramon Navarro Bosch &amp;lt;ramon.nb-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
writes:


My sense is that plone-devel is better for the brainstorming phase like
this in the sense that you'll get more feedback and more ideas.

Thanks,
Ross


&lt;/pre&gt;</description>
    <dc:creator>Ross Patterson</dc:creator>
    <dc:date>2013-06-13T20:47:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3844">
    <title>Re: Shared Folder on PAM</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3844</link>
    <description>&lt;pre&gt;Hi Ramon, how about marking the "shared content" with a specific interface?
ISharedContent or something... that way, you can filter results from a
catalog query using the "object_provides" index...

Regards,
Franco


On Thu, Jun 13, 2013 at 9:10 AM, Ramon Navarro Bosch &amp;lt;ramon.nb-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

&lt;/pre&gt;</description>
    <dc:creator>Franco Pellegrini</dc:creator>
    <dc:date>2013-06-13T16:47:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3843">
    <title>Shared Folder on PAM</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3843</link>
    <description>&lt;pre&gt;Hey FWT,

There is a use case on multilingual that I can't find a clean solution and
all implementation I do I feel like they are really hacky.

* Introduction *

There is a folder ( language root folder and navigation root ) for each
language where the user stores the different content on each language.

The problem is on shared content. Content that is in a neutral language and
needs to be seen on different language root folders. The desired solution
should allow users to create content that is seen on different languages
and when you see them it looks like you are still on the navigation root
from the language you are browsing.

* Actual solution *

There is a 'shared' folder on the root that is set to neutral language. We
patch the catalog to show it's content on the language root folders.

It leads a lot of problems, for example, we can't order the content on the
shared folder. The patch is not nice to use ( we want to remove all portal
catalog patches ). When we move to the shared content we need to pa&lt;/pre&gt;</description>
    <dc:creator>Ramon Navarro Bosch</dc:creator>
    <dc:date>2013-06-13T12:10:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3842">
    <title>Re: Scheduled meeting on 11.6.2013 and CVE announcement</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3842</link>
    <description>&lt;pre&gt;so, let's cancel it and postpone the meeting to Tue, 18th June, 2013,
21:00 CET.

i'll send out a new invitation.

best, johannes

On Mon, 2013-06-10 at 20:51 +0200, Andrew Mleczko wrote:

&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-11T11:33:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3841">
    <title>Re: Scheduled meeting on 11.6.2013 and CVEannouncement</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3841</link>
    <description>&lt;pre&gt;
+1
I would schedule it for next week.
a.



--
Andrew Mleczko - RedTurtle Technology
web site: www.redturtle.it
e-mail: amleczko-yzwUTSi0rH+GzLJY+7CQzQ&amp;lt; at &amp;gt;public.gmane.org
phone: +39 0532 1915958
fax: +39 0532 287070
&lt;/pre&gt;</description>
    <dc:creator>Andrew Mleczko</dc:creator>
    <dc:date>2013-06-10T18:51:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3840">
    <title>Re: Scheduled meeting on 11.6.2013 and CVEannouncement</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3840</link>
    <description>&lt;pre&gt;I am in favor of cancelling the FWT meeting due to the patch release.  Either 1 or 2 weeks later works for me.

Thanks,
Craig

On Jun 9, 2013, at 5:57 PM, Johannes Raggam &amp;lt;dev-//MPyowsN087nVVRfYWAjw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


--
Craig Haynal
WebLion - http://weblion.psu.edu/
Teaching and Learning with Technology
Information Technology Services
Penn State



&lt;/pre&gt;</description>
    <dc:creator>Craig Haynal</dc:creator>
    <dc:date>2013-06-10T18:30:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3839">
    <title>Scheduled meeting on 11.6.2013 and CVE announcement</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3839</link>
    <description>&lt;pre&gt;Hi FWT members,

We have a meeting scheduled on 11.6.2013, 21:00 CET, but on this day a
security vulnerability patch will be released at 2013-06-11, 15:00 UTC:
http://plone.org/products/plone/security/advisories/20130611-announcement

It's likely that some of us are busy updating their site. If that's the
case, we should consider to cancel the meeting and hold it 1, 2 weeks
later. What's your opinion?

Best, Johannes Raggam


&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-06-09T21:57:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3838">
    <title>Re: Today's meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3838</link>
    <description>&lt;pre&gt;I'm sorry i didn't reply this before, on Tuesday i was running some errands
prior to my trip here to the midwest symposium, sorry...

The time works fine for me too.


On Tue, May 28, 2013 at 4:22 PM, David Glick (Plone)
&amp;lt;david.glick-z4DKO/sx8wnYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

&lt;/pre&gt;</description>
    <dc:creator>Franco Pellegrini</dc:creator>
    <dc:date>2013-05-31T18:12:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3837">
    <title>Re: Today's meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3837</link>
    <description>&lt;pre&gt;
OK for me too.


&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-05-29T08:11:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3836">
    <title>Re: Today's meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3836</link>
    <description>&lt;pre&gt;

OK for me too.


z.
&lt;/pre&gt;</description>
    <dc:creator>Nejc Zupan</dc:creator>
    <dc:date>2013-05-29T07:30:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3835">
    <title>Re: Today's meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3835</link>
    <description>&lt;pre&gt;
I'm OK with the current scheduling, but maybe we can have another
doodle just to check if the rest is fine too?
a.

--
Andrew Mleczko - RedTurtle Technology
web site: www.redturtle.it
e-mail: amleczko-yzwUTSi0rH+GzLJY+7CQzQ&amp;lt; at &amp;gt;public.gmane.org
phone: +39 0532 1915958
fax: +39 0532 287070
&lt;/pre&gt;</description>
    <dc:creator>Andrew Mleczko</dc:creator>
    <dc:date>2013-05-29T06:56:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3834">
    <title>Today's meeting canceled</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3834</link>
    <description>&lt;pre&gt;Hi framework team,
I canceled today's meeting because only Eric, Johannes, and I were 
there. (Ross tried but had technical difficulties.) For those of you who 
weren't present, can we change anything about how we are scheduling 
meetings to make it more possible for you to attend?

Please reply to this message with an update on the PLIPs you are 
currently championing or reviewing.

My update is that I did a review of the plone.app.widgets PLIP: 
https://dev.plone.org/ticket/13476#comment:14. It looks promising to me, 
but still needs some work on refactoring to be in the right places in 
core rather than an add-on, and on documentation. I am +1 on the concept 
of the PLIP but -1 on merging it until that work is done.

I unfortunately did not have time yet to do my other task, which is 
prototyping a more sane way to implement PLIP 13350 (define member 
properties TTW).

Also, a reminder to Nejc, Johannes, Matthew and Martijn that there are 
some PLIPs in the "Submitted" section of the google spreadsheet th&lt;/pre&gt;</description>
    <dc:creator>David Glick (Plone</dc:creator>
    <dc:date>2013-05-28T19:22:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3833">
    <title>Re: PLIPs and jenkins integration</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3833</link>
    <description>&lt;pre&gt;Hey Johannes :

We've been working on a easy way to maintain plips jenkins integration so
my aproach is :

* There is http://jenkins.plone.org/roboto/plips list. Here you can find a
list of configured jenkins jobs. The idea is that for each job is a PLIP
(or some other project like a plip) where you define :
  - The name of the plip
  - The git repos/ branches of plone you want to hook to run tests when a
push is done there
  - The git repo and branch that will be checkout to run the tests
  - The shell command structure that will be run to test. There is a basic
button that pushed an example with coverage and robot.
  - You can check if you want robotframework reports
  - Who should receive mails about this tests
  - And some url to see it
  ( it's secured using a key on the form so nobody who doesn't know the key
can add jobs there )

* When push is done to the repo that has been hook a job is created or
reconfigured on jenkins, runs the test and sends the info to github commit
message and mails of followe&lt;/pre&gt;</description>
    <dc:creator>Ramon Navarro Bosch</dc:creator>
    <dc:date>2013-05-13T08:22:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3832">
    <title>PLIPs and jenkins integration</title>
    <link>http://permalink.gmane.org/gmane.comp.web.zope.plone.teams.framework/3832</link>
    <description>&lt;pre&gt;Hi Timo!

At the last FWT meeting I brought up your request to get a viewpoint
from the Framework Team on having Jenkins integration for each PLIP.

We all think that this is a very good idea. You might have seen this
already in Eric's FWT meeting notes, but here again:

"""* Testing team working on Jenkins configuration for plips.
plone.app.contenttypes already working. Would we like these for all
plips? Absolutely.
    * We need to get some documentation in the coredev docs about how
PLIP implementers can get access to their builds.
"""

Please let me know if you need some more information from the FWT to
continue your work. And keep me updated about the progress.

Thanks a lot,
Johannes



&lt;/pre&gt;</description>
    <dc:creator>Johannes Raggam</dc:creator>
    <dc:date>2013-05-13T08:09:32</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.teams.framework">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.teams.framework</link>
  </textinput>
</rdf:RDF>
