Re: [PLIP-Advisories] [Plone] #10778: Standalone UUID implementation

[Change notifications for Plone PLIPs on Trac.]

#10778: Standalone UUID implementation
+---
 Reporter:  optilude|Owner:  optilude
 Type:  PLIP|   Status:  new 
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by davisagli):

 The test failure in archetypes.referencebrowserwidget looks really trivial
 -- it simply uses a regexp that needs to be updated to match UIDs with
 dashes in them.

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [Framework-Team] changing name of plone.app.event?

[Raphael Ritz]

Andreas Jung wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> plone.app.calendar is even more misleading since plone.app.event
> provides only the event core implementation but not calendar
> functionality (or?). I think plone.app.event is fine since Plone
> developers know of ATEvent and speaking of plone.app.event as a
> replacement seems more logical than renaming it to .calendar.
>   

On the other hand it provides to Plone what
CMFCalendar provides to CMF - I think at least.

Personally, I have no particular preference.

And never ever ask or listen to a German when
it comes to naming things in English ;-)

Raphael


> My 2cents,
> Andreas
>
> Johannes Raggam wrote:
>   
>> Dear Framework Team!
>>
>> The name plone.app.event for the event improvement package (see:
>> http://dev.plone.org/plone/ticket/10886 ) was proposed by me at the
>> cathedral sprint in Cologne. But since then I often think that this
>> wasn't the best possible name. It's too ambiguous because it may impose
>> some zope.event like event-machinery as purpose.
>>
>> Would the FWT agree to change it to plone.app.calendar and eventually
>> create an additional package called plone.calendar for general purpose
>> tools and interfaces?
>> "calendar" seems a good name to me because among other reasons some
>> parts are modeled after the RFC2445 (iCalendar) specification.
>>
>> This is the last possible moment to change the name before
>> plone.app.event would possibly released with plone4.1.
>>
>> Thanks and all the best,
>> johannes raggam
>>
>> ___
>> Framework-Team mailing list
>> Framework-Team@lists.plone.org
>> http://lists.plone.org/mailman/listinfo/framework-team
>> 
>
>
> - -- 
> ZOPYX Limited   | zopyx group
> Charlottenstr. 37/1 | The full-service network for Zope & Plone
> D-72070 Tübingen| Produce & Publish
> www.zopyx.com   | www.produce-and-publish.com
> - 
> E-Publishing, Python, Zope & Plone development, Consulting
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQGUBAEBAgAGBQJMoLHuAAoJEADcfz7u4AZjWFULv0WEWyzJvSp6rrns9W9Vr6aw
> q1OcgDfJClL5Zy0MMNeOzS1r9ZOAv9WxR/Xo79Dax7d3pBN9aMZnUciRBRyvnzQx
> no6yJHtnrRRrNDrBubtwK+Soyu0HpoL+LtX4tVw3WAAmtzUwqO4dU4KrHYN0pMlx
> UnXR/ajQZMThJl9wC94JH+rXhZ3sEoQluOJLLHvUOqfo6tJYK/flwBEOnty0esye
> WSsvTIgLh+wmhC9kDReIXWSUhf0cyypjQLZMYyuz74F7wnVxeHqhV4+pl1qWwTtN
> OrvW/82f0Gv7BRxg9VFTQQ9FGctTLA9k0EgwU37idWRYhIZjIORFBYbdzYmZrNI5
> 4Oxi8a7oj52Lo3RWthM1AJZEpgjZ19+A9xUnd46dZCNi7SPo8CRs4ZKrnMn7hgUQ
> zJkL6YGq1ZR4929pzlGrzlv4/YwMkRsONEsaKcXIP4WWJpjv8oRqWbP42ZGVitR7
> i2c/6UON/JhWqxWSIUvVsBjRjbv5OkY=
> =MLyt
> -END PGP SIGNATURE-
>   
> ___
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
>   

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by esteele):

 FWIW, I'm only seeing test failures in plone.app.blob and wicked. The
 GenericSetup failures have been cleared in 4.0 (which 4.1 currently uses
 as a versions base).

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10778: Standalone UUID implementation

[Change notifications for Plone PLIPs on Trac.]

#10778: Standalone UUID implementation
+---
 Reporter:  optilude|Owner:  optilude
 Type:  PLIP|   Status:  new 
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by alecm):

 (In [40362]) Added review for PLIP 10778.  Refs #10778

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by davisagli):

 Alec, thanks for the reminders regarding our deprecation policy. I took a
 closer look at the changes on CMFCore trunk and none of them are a
 concern, given that policy (or even particularly a concern without it).

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by alecm):

 I also saw issues when attempting to downgrade my Zope.  Such problems are
 to be expected, but it will be tremendously important to document this
 fact and provide a stronger than usual recommendation that Data.fs needs
 to be backed up before upgrading.

 Regarding CMFCore deprecations: my understanding is that removal of
 previously deprecated features is generally acceptable in a .x release,
 though not in a .x.x release, and that new deprecations are generally
 acceptable at any release level as long as the feature is not prematurely
 removed.  We'll certainly need to discuss the impact of these CMFCore
 changes though.

 David, is there a summary of the deprecations and backwards incompatible
 changes in CMFCore somewhere?

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by davisagli):

 It concerns me a bit that the update to Zope 2.13 appears to require an
 update to CMFCore 2.3 (currently unreleased), which deprecates some stuff
 that was available in 2.2.  That doesn't seem good for a Plone .x release.

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by eleddy):

 (In [40359]) zope 2.13 plip review. refs #10776

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] [Plone] #10776: Update to Zope 2.13

[Change notifications for Plone PLIPs on Trac.]

#10776: Update to Zope 2.13
+---
 Reporter:  hannosch|Owner:  hannosch
 Type:  PLIP|   Status:  assigned
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by cah190):

 (In [40358]) Review for PLIP 10776.  Refs #10776.

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories

Re: [Framework-Team] changing name of plone.app.event?

[Andreas Jung]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

plone.app.calendar is even more misleading since plone.app.event
provides only the event core implementation but not calendar
functionality (or?). I think plone.app.event is fine since Plone
developers know of ATEvent and speaking of plone.app.event as a
replacement seems more logical than renaming it to .calendar.

My 2cents,
Andreas

Johannes Raggam wrote:
> Dear Framework Team!
> 
> The name plone.app.event for the event improvement package (see:
> http://dev.plone.org/plone/ticket/10886 ) was proposed by me at the
> cathedral sprint in Cologne. But since then I often think that this
> wasn't the best possible name. It's too ambiguous because it may impose
> some zope.event like event-machinery as purpose.
> 
> Would the FWT agree to change it to plone.app.calendar and eventually
> create an additional package called plone.calendar for general purpose
> tools and interfaces?
> "calendar" seems a good name to me because among other reasons some
> parts are modeled after the RFC2445 (iCalendar) specification.
> 
> This is the last possible moment to change the name before
> plone.app.event would possibly released with plone4.1.
> 
> Thanks and all the best,
> johannes raggam
> 
> ___
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team


- -- 
ZOPYX Limited   | zopyx group
Charlottenstr. 37/1 | The full-service network for Zope & Plone
D-72070 Tübingen| Produce & Publish
www.zopyx.com   | www.produce-and-publish.com
- 
E-Publishing, Python, Zope & Plone development, Consulting


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQGUBAEBAgAGBQJMoLHuAAoJEADcfz7u4AZjWFULv0WEWyzJvSp6rrns9W9Vr6aw
q1OcgDfJClL5Zy0MMNeOzS1r9ZOAv9WxR/Xo79Dax7d3pBN9aMZnUciRBRyvnzQx
no6yJHtnrRRrNDrBubtwK+Soyu0HpoL+LtX4tVw3WAAmtzUwqO4dU4KrHYN0pMlx
UnXR/ajQZMThJl9wC94JH+rXhZ3sEoQluOJLLHvUOqfo6tJYK/flwBEOnty0esye
WSsvTIgLh+wmhC9kDReIXWSUhf0cyypjQLZMYyuz74F7wnVxeHqhV4+pl1qWwTtN
OrvW/82f0Gv7BRxg9VFTQQ9FGctTLA9k0EgwU37idWRYhIZjIORFBYbdzYmZrNI5
4Oxi8a7oj52Lo3RWthM1AJZEpgjZ19+A9xUnd46dZCNi7SPo8CRs4ZKrnMn7hgUQ
zJkL6YGq1ZR4929pzlGrzlv4/YwMkRsONEsaKcXIP4WWJpjv8oRqWbP42ZGVitR7
i2c/6UON/JhWqxWSIUvVsBjRjbv5OkY=
=MLyt
-END PGP SIGNATURE-
<>___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

[Framework-Team] changing name of plone.app.event?

[Johannes Raggam]

Dear Framework Team!

The name plone.app.event for the event improvement package (see:
http://dev.plone.org/plone/ticket/10886 ) was proposed by me at the
cathedral sprint in Cologne. But since then I often think that this
wasn't the best possible name. It's too ambiguous because it may impose
some zope.event like event-machinery as purpose.

Would the FWT agree to change it to plone.app.calendar and eventually
create an additional package called plone.calendar for general purpose
tools and interfaces?
"calendar" seems a good name to me because among other reasons some
parts are modeled after the RFC2445 (iCalendar) specification.

This is the last possible moment to change the name before
plone.app.event would possibly released with plone4.1.

Thanks and all the best,
johannes raggam

___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

[Framework-Team] Reminder: We need your reviews

[Eric Steele]

FWT,

At last week's meeting, we agreed that we need 3 reviews per PLIP. I want to 
get the first 5 wrapped up during tomorrow's meeting so we can move on to the 
slew that'll be coming in over the next week.

We're nearly there, most just need one more completed review.

Needs 1 more review:

Include plone.app.registry  (https://dev.plone.org/plone/ticket/9472)
Include z3c.form(https://dev.plone.org/plone/ticket/9473)
Include plone.testing and plone.app.testing in KGS 
(https://dev.plone.org/plone/ticket/10846)
Separate Products.CMFPlone from the Plone egg and its optional dependencies 
(https://dev.plone.org/plone/ticket/10877)
Standalone UUID implementation (https://dev.plone.org/plone/ticket/10778)

Needs 2 more reviews:
Update to Zope 2.13 (https://dev.plone.org/plone/ticket/10776)


Add "SiteAdmin" role (https://dev.plone.org/plone/ticket/10878) is also 
complete, if anyone wants to get a head start.

BIg thanks to Rob and Craig for rocking the reviews so far (5 and 4 completed, 
respectively). 

Eric
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Re: [PLIP-Advisories] [Plone] #10846: Include plone.testing and plone.app.testing in KGS

[Change notifications for Plone PLIPs on Trac.]

#10846: Include plone.testing and plone.app.testing in KGS
+---
 Reporter:  optilude|Owner:  optilude
 Type:  PLIP|   Status:  new 
 Priority:  minor   |Milestone:  4.1 
Component:  Infrastructure  |   Resolution:  
 Keywords:  |  
+---

Comment(by cah190):

 (In [40353]) Review for PLIP 10846.  Refs #10846.

-- 
Ticket URL: 
Plone 
Plone Content Management System
___
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories