Re: [Framework-Team] getting rid of plone.app.search
Big +1 from me! For what it's worth, we replaced the stock livesearch with a select2 widget in one of our sites this week. Works beautifully. On 6 Feb 2015, at 21:26, Nathan Van Gheem wrote: I'm working on fixing live search. I was wondering if I could move plone.app.search into Products.CMFPlone. The package only provides a view right now--seems a bit silly to be in it's own package. It would be part of this PLIP: https://dev.plone.org/ticket/13283 Makes more sense to do it package by package instead of one huge PR. -Nathan ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] FWT meeting attendance stats
On Mon, Jun 23, 2014, at 10:58 PM, Rok Garbas wrote: hi guys, last month i've been unactive since i was on a quest to learn surfing (some call this vacation). with july i'm starting to work in berlin in a position which does not involve any plone development, therefore i would like to step down as a framework team member since i will have very little or no time for plone in comming year. thank you for all the patience you had with me. Thanks for everything you've done for us. You've had a major influence on Plone 5 and we're all grateful. Don't be a stranger. Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Arnhem Sprint PLIP Champions Wanted!
Thanks so much for doing this, David. On Friday, November 8, 2013 at 1:04 PM, David Glick (Plone) wrote: I put together an overview of the various efforts that are underway for Plone 5, along with a few thoughts on what the highest priorities are right now: http://titanpad.com/Sfinb2geKV On 11/4/13, 7:42 AM, Rob Gietema wrote: Just one more week and the Arnhem Sprint will start! We currently have a total of 33(!) sprinters which we’ll split into 5 scrum teams during the sprint. To get the most out of the sprint we would like to get PLIP Champions who will act as “Product Owners” for the teams (preferably on location, but remote is also fine). If you want a team to work on your PLIP please let me know and I’ll add you to the list of available PLIP’s. Checkout https://dev.plone.org/roadmap for available PLIP’s for Plone 5. Cheers, Rob Gietema Four Digits ___ Framework-Team mailing list framework-t...@lists.plone.org (mailto:framework-t...@lists.plone.org) https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] FWT meeting notes
Looks great. Eric On Tuesday, June 25, 2013 at 5:13 PM, Johannes Raggam wrote: Please review and comment in an answer, if you have something to correct or add. Otherwise, I'll send it out tomorrow morning (CET) on plone-dev. Best, Johannes = Framework Team Meeting 2013-06-25 = Attendees = Nathan Van Gheem Nejc Zupan Eric Steele Ross Patterson Craig Haynal David Glick Johannes Raggam (meeting chair) Plone 5 Talk The FWT decided that the next Plone Release will be Plone 5 (+6, -1). Instead of having a Plone 4.4 Release with major PLIPS included, where we have to expect that the upgrade experience isn't as seamless as it should for a minor release, we better do a Plone 5 release. In our vision, Plone 5 will also have the other major PLIPS included, among others: - plone.app.widgets, - plone.app.toolbar, - new theme, - Removing the dependencies on CMFFormController and CMF skins, - plone.app.* package merging. The PLIPS mentioned above are in the midst of implementation or even the conceptional phase. So, Plone 5 isn't exactly around the corner but an undefined timespan away - we expect it to be a year, which should give us and the implementors enough time to finish, review and integrate the PLIPS. Six Feet Up is investing 5 hours a week for QA of the upcoming Plone 5 release. Eric is revisiting the PLIPs and reassigns them to Plone 5 as needed. Plone 5 content upgrades We had a discussion about how to handle content upgrades in Plone 5: - 3 votes for forced upgrade of all standard Products.ATContentTypes to their Dexterity based plone.app.contenttypes and plone.app.event equivalents to keep the old cruft away from Plone 5. - 1 vote for optional upgrade steps to migrate the content to let integrators decide what to do. - 2 votes were for waiting and deciding later, when the upgrade steps are fully implemented. Schema extended standard content types cannot easily be upgraded, since this involves custom code. For such contents, custom upgrade steps have to be implemented anyways, if wished. Release Team Eric is building up a release team to help him doing releases, as much automated as possible. This makes release dates less dependent on time constraints of a single person. More FWT Team members = Ross brought up the topic of acquiring more Framework Team members, as it turned out that the last couple of meetings were poorly attended. More people means also more eyeballs on the development and progress of Plone, so we thought this is a good idea. He sets up an invitation mail soon. Next meeting Next meeting is scheduled on July, 9th. 2013. Eric is doing the meeting chair. -- programmatic web development di(fh) johannes raggam / thet python plone zope development mail: off...@programmatic.pro web: http://programmatic.pro http://bluedynamics.com ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Plone 5
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 from content for easier styling (plone.app.toolbar) * Accessible: WCAG- and ATAG-compliant * Deco.gs is replaced with a more commonly-used grid system, responsive * New folder contents UI with filtering and batch operations * Improved, tested widgets * TinyMCE gets upgraded to version 4.0, with a simplified integration making it easier for us to stay up-to-date * Plone 5 ships with an empty portal_skins. * Exists for add-ons * Most content moved to browser views, z3c.form * Login rewritten to use views, events. Simple, but pluggable for more complex use cases * Pay attention to proper XSRF protection for our most common functionality * Plone 5 has amazing test coverage. * Migrating scripts from portal_skins to browser views allows more unit testing * New JavaScript practices mean more unit tests for our interactive stuff * Plone 5 is faster. * Chameleon reduces rendering times by 30% * Date formatting is handled on the client side * Plone 5 is easier to learn. * plone.api covers most common development tasks. * Plone 5 eats its own dog food and sets an example for: * Views * z3c.form * Dexterity * Diazo * JavaScript integration/development requires less knowledge of Plone * Theming requires less knowledge of Plone, less fighting with the default setup And most importantly... * Plone 5 is achievable within the next 12 months. There are, I'm sure, 30 other features that are in some stage of not-doneness, and while I'd like to see us do everything, we need to find some kind of scope. I think the above featureset gives us a nice range of features, a not-too-painful upgrade, and gives everyone plenty to do over the next year. We've already begun approaching Plone companies to get buy in to the effort, asking for time, money or organizational support. Six Feet Up has pledged 5 hours per week of their QA team's time to test our work. Netsight is organizing a sprint to rework the login. AMP is pledging 5 hours a week toward deprecating portal_skins. Wildcard is taking on the folder contents revamp. If your group has a particular need, now is the time to make it happen. In addition, we have plans to use the general community excitement that comes along with a major release to build some momentum in our non-code teams. If we can move this forward, I think Plone 5 will be a big step up for both Plone the software and Plone the community. Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Reminder: Call tomorrow
We have our bi-weekly call tomorrow at 1900 GMT (http://everytimezone.com/#2013-4-29,1860,6bj) https://www.google.com/calendar/render?gsessionid=Dp9GXhE7itL_ES8VyufSqA Please check in on your PLIPs so we can discuss status. Thanks, Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Support for pre-PSE sprint
+1 from me. Eric On Thursday, April 18, 2013 at 4:42 PM, Elizabeth Leddy wrote: Hello Lads, The board needs some official communication that the FWT supports the pre-PSE sprint as a strategic sprint. The pre-PSE sprint will be focused on on ripping out CMFFormController. Any objections to supporting funding this? Otherwise a +1 will suffice. Thank you for everything lovelies! Liz -- Elizabeth Leddy Sent with Sparrow (http://www.sparrowmailapp.com/?sig) ___ Framework-Team mailing list framework-t...@lists.plone.org (mailto:framework-t...@lists.plone.org) https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Collections portlets
So now that we've got plone.app.collection in 4.2, how do we want to handle collections portlets? We currently ship with plone.portlet.collection. plone.app.collection adds its own, largely the same (though missing some of the more recent features/fixes added to the other). Should the p.a.collection version be made the default (and updated for parity with p.portlet.collection) or should p.portlet.collection be updated to handle the newer collections (and remove the portlet functionality from p.a.collection)? Seems like the latter would be the simpler option. Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] PLIP 12227: In-Plone Theme Editor
Hi all, The FWT has asked that I pass along http://dev.plone.org/ticket/12227 to you. #12227 adds a through-the-web editor for Diazo/plone.app.theming customization. The Framework Team is happy with things from the code side, but feel the UI definitely warrants a closer look. Also, if anyone is willing to assist Martin with improving the look of things, he's looking for for help (https://dev.plone.org/ticket/12227#comment:11). If there's anything I can do to get someone up and running with a demo version, I'm happy to help. Eric___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Framework Team dinner?
On Nov 3, 2011, at 4:48 PM, Martin Aspeli optilude+li...@gmail.com wrote: On 3 November 2011 16:45, Laurence Rowe l...@lrowe.co.uk wrote: On 1 November 2011 11:55, Laurence Rowe l...@lrowe.co.uk wrote: Friday is the Roadmap Team dinner, so Sunday would work best for me. So, roadmap team dinner is now tonight instead, so Friday should work for everyone. Yep, followed by SFU party ;) Martin Friday it is then! Uh...any restaurant suggestions? ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Framework Team dinner?
Shall we get our current and past members together for supper some night this week? I'm guessing Friday or Sunday nights are the most available times. Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Next meeting (calliflower issues)
FWT, I'm sorry for all of the noise from Calliflower this evening. I'm trying to get the upcoming meeting scheduled (Sept 27th) and remove any future scheduled occurrences (we'll figure that out on the 27th). I'll silence it while I try to get things working properly and then send out a proper reminder. Eric ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
[Framework-Team] Conference Call (5 April)
It looks like Calliflower's recent subscription changes have left me disconnected from Plone's account. Steve McMahon is in the process of setting up a new call for today. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Meeting Minutes - 22 March 2011
Attending: Eric Steele, Craig Haynal, Laurence Rowe, Ross Patterson , Elizabeth Leddy, Alec Mitchell, Matthew Wilkes(!) • Ross: Trac has been synced with LDAP, so we can rely on notifications now. • Batch Editing plugin has been installed, but does not work. Wyn is looking at it. • Mark Corum sending out an announcement about revised PLIP process • Ross will do the mass spamming of previous plip owners • Liz will contact the implementers of events, content listing, search results PLIPs to make sure they're still targeting 4.2 • PLIP 11300: http://dev.plone.org/plone/ticket/11300 • Concern that updates to forms is intended to be broken out into another PLIP. If we're going to do make the move, we need to do it throughout. • Concerns over IE support for HTML 5. • Don't have built-in support, but inclusion of a javascript will provide that functionality • Related to http://dev.plone.org/plone/ticket/9300? We can close that one. • Potential implications for Diazo. Output will become HTML instead of XHTML. Conversion issues with libxml2. • No one has stepped up to be a champion. • It's a no, but it's a really minor no. • Eric will ask Denys to give a stronger case for why this is needed. Call audio at http://apps.calliflower.com/recording/download/12633?rec_key=e248b99143343d8a2a29314c1b67343d54f4a84a Next Meeting: April 5, 2011. ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting Notes: 8 March, 2011
Attending: Eric Steele, Craig Haynal, Alec Mitchell, Elizabeth Leddy, Ross Patterson, Martijn Pieters Absent: Laurence Rowe, Rob Gietema, Matthew Wilkes • Empower the release manager and PLIP authors to demand what they should expect from the FWT • Each PLIP should have a designated FWT champion • Allows us to keep better track of PLIPs, AWOL FWT members • PLIP authors can poke FWT champion as needed • TODO: Make a how to shepherd your PLIP doc • TODO: Go through existing PLIPs to cull dead ones, find implementers for others • https://dev.plone.org/plone/report/24 • Move existing PLIPS to Orphaned • Ross will contact orphaned plip implementers to see if they're still interested • Targets for 4.2: collections, search results, events, contentlisting • Eric will go through and clear out 4.1 milestone • Problem: Not all trac users have email addresses assigned. This was probably a part of the communication problem in 4.1. • TODO: Get Trac user email addresses populated from Plone.org accts. • Eric will contact board RE: increasing team size to 10. • Eric will contact existing members to make sure they want to stay Next call: 22 March, 2011 Meeting audio: http://apps.calliflower.com/recording/download/12255?rec_key=9e88c163e6ef37da10d608a9ed3165b333b73ae4 ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Reworking the PLIP Lifecycle | discussion
On Feb 24, 2011, at 1:36 PM, Hanno Schlichting wrote: On Thu, Feb 24, 2011 at 3:26 AM, Elizabeth Leddy ele...@umich.edu wrote: Feel free to respond over email or just edit the document: http://dev.plone.org/plone/wiki/PlipProcess Great work! In general, I'd like to give the fixed release schedule a 6 month test drive. If it sucks we can go back to status quo or move forward with the latest and greatest. I cannot remember any Plone releases that only took 6 months - even when we tried hard. I'd usually expect a 50% overrun from any stated timeline, so while aiming for 6 months we can manage to do a release after 9 months. We'd have to aim for a 3-4 months cycle to actually be able to do two releases in a year. And I wouldn't really want to do more than two releases per year, or we risk getting too fragmented, diverging code bases and very short support lifecycles for each release (only the last 4.x release gets bugfixes at any given time according to our current policy). I think we could aim for a spring and an autumn release, expecting most people to be busy in summer vacations and around x-mas/new year. Hanno You're probably right. That's my over-eager under-estimation issue. ;) What I'm after is trying to reduce the penalty for missing the merge deadline. By that, I mean that once that deadline is missed, development tends to completely halt for months at a time before another last minute push at the next deadline. Maybe that's something we can fix with better back and forth from the FWT. Maybe it's just a fact of life. ;) Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Reminder: Biweekly Call on Tuesday
A reminder that we have our call on Tuesday, 8 March. http://apps.calliflower.com/conf/show/170350 The agenda is currently: * Discussion of proposed changes to the PLIP lifecycle * 4.2 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Meeting Minutes – Feb 22, 2011
My crummy meeting notes... PLIP process • Attending: Eric Steele, Craig Haynal, Ross Patterson, Elizabeth Leddy, Laurence Rowe, Martijn Pieters • Move to more of a cyclical (fixed timeframe release) cycle • Be more responsive to people • Better distribute load among FWT members • PLIPs can be submitted at any time • Regular FWT conference call schedule • http://www.mail-archive.com/framework-team@lists.plone.org/msg04500.html • Some PLIPs (p.a.discussion) wound up with an iterative review process, which worked well • Others wound up stopping all development for 6 weeks waiting for reviews • Review comments in PLIP ticket or in review doc? • Implementers aren't looking at review docs • How to get others (non-implementers) to chip in on fixing small issues • Ticketing in other trackers? • Lots of PLIP tickets in a I may work on this some day state. How do we handle those? • eleddy will put up a doc describing stages of process • 3 month release cycle • How do we keep up submission momentum? Will we get new proposals if there is no hey, it's Plone 4.x! announcement? • Let's try it for now. • Regular FWT call, every 2 weeks. We'll be able to keep it shorter. Audio: http://apps.calliflower.com/recording/download/11882?rec_key=ad1d9263d77a1f419c2e21fa76fca420842be9fa Next call: 8 March, 2011 @ 19:00 GMT ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Rescheduling tomorrow's call
FWT, Can we push back tomorrow's call for another week? I've wound up with 2 conflicting meetings on top of our call. I've heard from two others who wouldn't be able to make it tomorrow as well. Thanks, Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Reworking the PLIP Lifecycle | discussion
On Feb 9, 2011, at 10:49 PM, Ross Patterson wrote: Ross Patterson m...@rpatterson.net writes: Elizabeth Leddy ele...@umich.edu writes: Thanks for all the feedback guys! Curious what current team members think +1, though I expected to gather more contradicting perspectives before weighing in in. Ok, so Eric I think we're a go. Lets schedule another FWT meeting and hammer out the details. Liz, get ready! :-) Ross Yes, sorry I never managed to respond to this. I have 12 different theses sitting in my drafts folder and never quite managed to accurately capture what I wanted to say. Basically: 1) Consider me +1000 on this 2) Let's plan on faster/regular/smaller releases 3) Review process should be a process of continuous feedback, not the stop doing things so we can maybe look at it over the next 6 weeks 4) We need to be able to adapt to ideas that happen in the run-up to a release (see Geir's discovery of other places contentlistings could be used) 4) 4.2 should be focused on getting events, collections, content listings, search results. These need to happen. 5) Let's chat about this on Tuesday Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org https://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] 4.1a1 pending release
I've just soft-released 4.1a1. So far, the following PLIPs have been merged: 9472Include plone.app.registry 9473Include z3c.form 9938Factor custom output transformations out of the editors 10776 Update to Zope 2.13 10778 Standalone UUID implementation 10809 Table sort internationalization 10846 Include plone.testing and plone.app.testing in KGS 10877 Separate Products.CMFPlone from the Plone egg and its optional dependencies 10878 Add SiteAdmin role 10901 Set and enforce base coding standards for our own JavaScript I'll work on getting the remaining accepted PLIPs merged over the next week and will have an alpha 2 out shortly thereafter. Great work, everyone! Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] 4.1 Reviews are (essentially) done
We've closed off the initial implementation review period, at last. Revised implementations are due on Dec 31st, after which we'll take another look and discuss/vote at our Jan 4th meeting. We'll have an early Plone 4.1a1 out in the near future, once I've cleared up some lingering test failures. This will include the Zope 2.13 update; Plone/CMFPlone split; table sort internationalization; site admin role; and inclusion of plone.app.registry, z3c.form, and plone.app.caching which were deemed completed enough for an early merge. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [PLIP-Advisories] [Plone] #11017: Tags MultiSelectionWidget w/scrollbar checkboxes
Grab me on irc today and I'll walk you through how to get this working. On Dec 1, 2010, at 1:17 AM, Change notifications for Plone PLIPs on Trac.plip-advisor...@lists.plone.org wrote: #11017: Tags MultiSelectionWidget w/scrollbar checkboxes ---+ Reporter: rmattb | Owner: RMattB Type: PLIP | Status: new Priority: minor | Milestone: 4.1 Component: User Experience and Interface |Keywords: ---+ Changes (by rmattb): * cc: rmattb (removed) * cc: matt.bar...@… (added) -- Ticket URL: http://dev.plone.org/plone/ticket/11017#comment:58 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] 4.1 PLIP reviews
FWT, Since we only have 13 of our 33 reviews in, we'll have to give it another week. I'll tentatively schedule a call for Tuesday, Dec 7 for us to go over the reviews. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] FWT Meeting Tuesday
Sorry, it looks like the calliflower notification didn't go out when I'd originally set it up. I've resent, but here's the link just in case: http://apps.calliflower.com/conf/show/141209 Eric On Nov 7, 2010, at 8:22 PM, Eric Steele wrote: FWT, I'd like to have a quick meeting on Tuesday, Nov 9 to go over divvying up the submitted implementations, set a deadline, and discuss the merging of the Zope 2.13 and CMFPlone PLIPs. I'd also like to attempt to turn the meeting minutes into more of a collaborative endeavor: http://sync.in/y8V3Wtpg7E Eric ___ 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
[Framework-Team] Meeting Notes – November 9 , 2010
Meeting minutes are below. The TLDR version: FWT members, sign up for a minimum of 4 PLIPs to review. Have them done by Nov 30th. We're merging Zope 2.13 soon, voice any concerns ASAP. Plone 4.x Framework Team Meeting – Nov 9, 2010 In attendance: Eric Steele, Laurence Rowe, Craig Haynal, Rob Gietema, Alec Mitchell, Ross Patterson Agenda: * Merging Zope 2.13 and CMFPlone PLIPs * Craig has looked at it again in the last few days and tests are now passing and its working. * Decision to merge Zope 2.13 upfront, wait on CMFPlone until after reviews. * Divvying up PLIP reviews * 11 new implementations ready for review, will need at least 4 reviews from each FWT member to reach the desired 3/PLIP count. * Please sign up for reviews on the Plone 4.1 PLIP votes GoogleDoc http://bit.ly/Plone41PLIPs before reviewing. * Please add a link to your completed review to the spreadsheet. * UI team has been handed 10 PLIPs to review. Eric will attempt to coordinate. * Review deadline * Endeavour to complete reviews by November 30th * lxml in installers * Include lxml in the installers, makes life easier when using Diazo, etc. * Laurence will submit a PLIP, to be reviewed outside of the current round * Login changes * Changes are minor and can be merged once we branch * Changes to plone.session for auto-logout support should not be exposed through add/remove plugins, there is a variable in plone somewhere to list profiles to hide. * Functional browser testing * Eric will be submitting an out-of-process PLIP in the next month. Basics: standardize use, setup of Selenium 2 in core packages. Builds on work from sprints. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting Tuesday
FWT, I'd like to have a quick meeting on Tuesday, Nov 9 to go over divvying up the submitted implementations, set a deadline, and discuss the merging of the Zope 2.13 and CMFPlone PLIPs. I'd also like to attempt to turn the meeting minutes into more of a collaborative endeavor: http://sync.in/y8V3Wtpg7E Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PloneConf2010 FWT Dinner
On Oct 29, 2010, at 6:37 AM, Ross Patterson m...@rpatterson.net wrote: Eric Steele ems...@psu.edu writes: Let's plan on Friday night for a Framework Team dinner. FWT alumni are invited, as well as whatever UI team members are here. I'd also like to have Israel, as our de facto docs team leader, join us. Any suggestions on a location? I'll be there. Also, I think it's about time for specifics. Can we at least set a time so I know what to plan for tonight? Let's plan on meeting at 7 in Marlows (basement bar at Thistle) and we'll go from there. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PloneConf2010 FWT Dinner
On Oct 29, 2010, at 9:47 AM, Eric Steele wrote: Let's plan on meeting at 7 in Marlows (basement bar at Thistle) and we'll go from there. Oh, and a reminder that Marlow's gives a 20% discount on drinks with your conf id. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PloneConf2010 FWT Dinner
Let's plan on Friday night for a Framework Team dinner. FWT alumni are invited, as well as whatever UI team members are here. I'd also like to have Israel, as our de facto docs team leader, join us. Any suggestions on a location? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] WebLion Team Meeting Agenda
The agenda for today's team meeting is available https://weblion.psu.edu/intranet/weblion-team-meeting/21-october-2010 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] WebLion Team Meeting Agenda
Crap. Wrong team alias. Sorry for the noise. Eric On Oct 21, 2010, at 9:00 AM, Eric Steele wrote: The agenda for today's team meeting is available https://weblion.psu.edu/intranet/weblion-team-meeting/21-october-2010 Eric ___ 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: [Framework-Team] Today's Call (Oct 12, 2010)
On Oct 12, 2010, at 8:58 AM, Eric Steele wrote: FWT, We have a call scheduled for today. Since we've had all of one new review in the past two weeks, is it still worthwhile for us to get together to talk? Do we have any updates to the PLIPs we've already cast votes for to discuss? Ok. We'll cancel today's meeting and try for next week, assuming we can get some movement on reviews. I'd like to get feedback for all of those before the conference so that people can use the sprint time effectively. I'd remind you that we're now 3 weeks from our implementation deadline, so there will be many more reviews to do at that point. So far, we've been unable to get a full 3 reviews for 6 of the 8 PLIPs in the review queue. Current reviews: Craig: 5 Rob: 5 Alec: 3 Elizabeth: 2 Laurence: 0 Matthew: 0 Martijn: 0 Ross: 0 ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Today's Call (Oct 12, 2010)
On Oct 12, 2010, at 12:08 PM, Martijn Pieters m...@zopatista.com wrote: On Tue, Oct 12, 2010 at 17:59, Eric Steele ems...@psu.edu wrote: Current reviews: Craig: 5 Rob: 5 Alec: 3 Elizabeth: 2 Laurence: 0 Matthew: 0 Martijn: 0 Ross: 0 Though shamefully behind, I did complete 1 review (#9473). My apologies. I'll update my notes. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] New releases in the Plone 3.3 series
On Oct 7, 2010, at 2:44 AM, Godefroid Chapelle wrote: Le 05/10/10 21:46, Geir Bækholt a écrit : The Plone 3 series has run for a longer time than anticipated, but there is still a demand for new releases. Our awesome release manager, Wichert, has, after a long series of successful releases, stated that he unfortunately doesn't have the time available any longer to continue as Plone 3.3 release manager. The Plone Foundation board hereby requests that the framework team appoints a new release manager for further releases in the Plone 3.3 line. I'd be happy to take that role. I'd just need some handholding for the first release in case the process id not documented. I can certainly help. FWIW, we're two packages (plus CMFPlone) away from having a 3.3.6 release ready. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] New releases in the Plone 3.3 series
On Oct 7, 2010, at 10:59 AM, Wouter Vanden Hove wrote: Eric Steele wrote: FWIW, we're two packages (plus CMFPlone) away from having a 3.3.6 release ready. We don't have a dedicated milestone for Plone 3.3.6 in Trac with a list of bugs we like to see solved for this specific release. So what is the criterium to say we're two packages away from a release? What are those two packages? When I use z3c.checkversions on the buildout of plonenext-3.3, there are many packages that have minor updates. I already reviewed some of these and updated the versions.cfg accordingly. I volunteer to spend more time on his. Fine. I should say that when I last had time to make releases 2 weeks ago, we were down to two packages with failing tests (PlonePAS and Archetypes, I believe). Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Reminder: We need your reviews
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
[Framework-Team] Missed PLIP (#10987 – I mplement Link Checking as Core Feature of Plone)
This PLIP came in before the deadline, but I missed getting it on our tally sheet. Please have a look at it and we'll discuss it at next week's meeting. https://dev.plone.org/plone/ticket/10987 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] FWT Meeting Minutes – Sept 7, 2010
On Sep 20, 2010, at 11:56 AM, Eric Steele wrote: • #11003 – Content governance metadata • Is this a common need? • Sounds useful, but are people actually going to use this? • Should be developed as an add-on • Inappropriate to change the behavior of existing fields (expiration date) at this point • Decision: Accepted Sorry, that one should be 'declined'. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Framework Team Meeting Minutes – Sept 21, 2010
In attendance: Alec Mitchell, Craig Haynal, Elizabeth Leddy, Eric Steele, Rob Gietema, Ross Patterson * There's a meeting? * Calliflower didn't send out notifications to several people. * Eric will make sure to notify the list of upcoming meetings (and get meeting minutes out sooner). * Reviews * 1-2 done for submitted implementations so far * Want 3 reviews per PLIP * Worst (best?) case scenario, that's 7 per person. * Can dig up some willing non-FWT reviewers as needed. * Releases * We have 6 important PLIPs in already. Is it worth considering those plus a few extras as 4.1, moving on to 4.2? * Hadn't considered that. It'd be great to follow up 4.0 with a just-as-awesome 4.1 * Sexy to developers, nobody else. We need some of the user-focused features to make it compelling. * Resolution: Finish reviews for these ASAP, cut an early alpha in early October. * Scheduling * Oct 1 implementation deadline is rapidly approaching. * October is busy for reviewers. * Implementation time at sprints? * Discussed rescheduling the initial implementation deadline. * Resolution: No action taken yet. * Communication * We've been asked to be more public about decisions * PLIP review discussion * Alert mailing list to completed reviews? * Not all implementers subscribe to FWT list * Discussion should happen in tickets. * Make sure you ref tickets when committing reviews. TODO: Get 3 reviews for each of the submitted implementations for next week's meeting. Recording: http://apps.calliflower.com/recording/download/8524?rec_key=f912a989dcf19a91aa6d8a252f63b48be3043605 Next Meeting: Tuesday, Sept 28, 2010 (http://bit.ly/aqeKUT) ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting Minutes – Sept 7, 2010
Sorry for the delay getting these out. • #10280 – Allow overriding the title tag on a per-template basis • How common of a need is this? • Using the viewlet instead allows customization / view • Decision: Declined • #10964 – Asynchronously fetch suggestions for 404 Not Found Page • Do we still want to consider this? • Laurence hasn't had time to do benchmarks • Pass it along to implementation stage, ask for benchmarks as a deliverable? • Provide ability to disable suggestions, allow site admins to decide • Decision: Declined • #11003 – Content governance metadata • Is this a common need? • Sounds useful, but are people actually going to use this? • Should be developed as an add-on • Inappropriate to change the behavior of existing fields (expiration date) at this point • Decision: Accepted • #11013 – ARIA Landmark Roles for accessibility • Looks extremely low-risk • Previous experience of this resulting in JAWS getting confused with ARIA content. Will need testing • Make changes in markup, not Javascript. Make it opt-in. • Will XDV have problems? Parser ignores namespaces. • Decision: Accepted • #11016 – Configurable breadcrumbs • Like the idea, are there really no risks? • Would like to see this as an add-on • Too much configurability. • Decision: Declined • #11017 – Tags MultiSelectionWidget w/scrollbar checkboxes • No jQuery UI. • Concept is good enough, no need to provide a proof-of-concept. • Decision: Accepted • #11021 – Simple theming customizations through the plone interface • plone.app.themeeditor looks to be the way forward in this area of site customization • Like the idea of having text areas for editing css/js, but not as a proxy for dtml documents. • Render the two directly instead of proxying. • Implement as an add-on, resubmit for 4.2 • Decision: Declined • #11025 – Content Batch Editing • Keep as an add-on for now • Some batch editing already included: name, id, workflow, expiration. • Decision: Declined • #11065 – Ship with plone.app.caching • Immediate consensus • Decision: Accepted Recording available at http://apps.calliflower.com/recording/download/8320?rec_key=3441aceb551f83efd252ed71ef055ed43e234bfa Next meeting will be Sept 21, 2010. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Reminder, PLIPs ready for reviewing
FWT! A reminder that there are 5 PLIPs already in the review queue: Include plone.app.registry https://dev.plone.org/plone/ticket/9472 Include z3c.formhttps://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 I'd love to get these (plus the Zope 2.13 PLIP) merged in and released as a very early 4.1a1. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Three PLIPs ready for review
On Aug 28, 2010, at 10:19 AM, Martin Aspeli wrote: Hi, The following are ready for review: https://dev.plone.org/plone/ticket/9472 - plone.app.registry https://dev.plone.org/plone/ticket/9473 - z3c.form https://dev.plone.org/plone/ticket/10856 - plone.testing ... Thanks Martin. FWT, I've added the above to the ready for review section of our tracking spreadsheet (see the initial reviews tab). WIth Laurence's PLIP, that makes four that are ready to look at. Since we're spreading out the review process a bit more this time and I want to make sure we're a lot more picky about what goes into a minor release, I'd like to have at least 3 reviewers for each. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team Meeting Minutes - Aug. 24, 2010
On Aug 24, 2010, at 3:57 PM, David Glick wrote: - Present: all except Ross Patterson (excused). David Glick sat in to take minutes. David, Thanks for doing this. It made my week much easier. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team Meeting Minutes - Aug. 24, 2010
On Aug 24, 2010, at 3:57 PM, David Glick wrote: - Six week PLIP implementation period beginning on the submission deadline and ending Sept. 11 Just a note on the implementation deadline. That should be Oct 1. That'll give everyone about 5.5 weeks to get their work in and we should be able to get reviews back before the conference. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team Meeting Minutes - Aug. 24, 2010
On Aug 24, 2010, at 10:50 PM, Martin Aspeli wrote: On 25 August 2010 04:57, David Glick davidgl...@groundwire.org wrote: - 10804: Include workflow manager - based on uwosh.northstar - May need some input from the UI team to make it fit in with the rest of Plone's UI Was this one accepted or rejected? Martin Accepted ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team M eeting Minutes– 17 August, 2010
On Aug 19, 2010, at 10:24 AM, Godefroid Chapelle wrote: Reason why I insist on automated tests. Functional tests run too slowly to rely on developers running them regularly. We need to delegate to Hudson or buildbot. I agree completely. I very nearly* have a Hudson/Selenium Grid/plone.app.testing pile running Selenium tests automatically across multiple browsers and machines. If I can convince the kid to give me a few free hours to work today, I'll wrap it up and write up what I have. * For some definition of nearly Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team M eeting Minutes– 17 August, 2010
On Aug 19, 2010, at 12:32 PM, Godefroid Chapelle wrote: Le 19/08/10 18:14, Eric Steele a écrit : On Aug 19, 2010, at 10:24 AM, Godefroid Chapelle wrote: Reason why I insist on automated tests. Functional tests run too slowly to rely on developers running them regularly. We need to delegate to Hudson or buildbot. I agree completely. I very nearly* have a Hudson/Selenium Grid/plone.app.testing pile running Selenium tests automatically across multiple browsers and machines. If I can convince the kid to give me a few free hours to work today, I'll wrap it up and write up what I have. Have you written a new layer ? Have you looked at gocept.selenium ? * For some definition of nearly Eric I wrote a new layer, mainly because I wanted to figure out how it all worked. I've put up a quick screencast of the whole thing in action, if anyone's interested. http://blip.tv/file/4023258 Basically Hudson controls a Selenium Grid which doles out requests to the requested browsers based on RC instance availability. The testcase layer accepts environment variables for ZServer host/port and Selenium host/port/browser. I've created one job per browser (Firefox and Safari in the screencast), passing in a new port and browser string environment var in each. Selenium Grid will pass the request along to the first available RC instance with that browser identifier and that'll hit the one-off ZServer created by the testcase. We should be able to kick off each of these jobs after the Plone 4 build runs and AFAIK they'll run simultaneously without issue. The one thing I'm missing at the moment is preventing them from running during normal test runs, but David's shown me a way forward on that. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Our next meeting – PLI P-a-thon part 1
On Aug 13, 2010, at 5:30 AM, Ross Patterson wrote: Eric Steele ems...@psu.edu writes: We've got 30 PLIPs in for 4.1 already (http://dev.plone.org/plone/report/24), so it's time to get together and start talking. Can I assume that next Tuesday at 14:00 UTC will work, or should I set up another Doodle thing? If that's the same time as the last meeting, that works for me. The last meeting was at 10AM here on the pacific coast. The web sites I'm consulting to translate 14:00 UTC to my time, however, seem to indicate that's *way* too early in the morning. I apologize in advance for my time zone ignorance, but can someone tell me what time that is on the pacific coast? Ross Bah. You're right. I can't add properly. That'd be 18:00 UTC, the same time as our last meeting. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Our next meeting – PLIP-a-t hon part 1
Team, We've got 30 PLIPs in for 4.1 already (http://dev.plone.org/plone/report/24), so it's time to get together and start talking. Can I assume that next Tuesday at 14:00 UTC will work, or should I set up another Doodle thing? Everyone should be reading over the submitted PLIPs, asking questions of the proposers, and getting an idea of whether or not you'd like to pass each one on to the implementation stage. Also, be thinking about those that might be considered prerequisites (like p.a.registry, z3c.form) and could have an effect on how the other PLIPs are implemented. Thanks, Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone 4.1] Framework Team, let's chat
On Jul 8, 2010, at 10:51 AM, Eric Steele wrote: (I believe everyone is signed up for the FWT list, but cc'ing Craig and Elizabeth, just in case) Once again, congratulations to all of our new and returning Framework Team members! Now that 4.0 is nearing RC status, it's time for us to start talking about the future. I'd like to kick things off with a conference call. Calliflower seemed to work well enough last time, so we'll continue with that. I've set up a Doodle page (oh, how I hate Doodle, but it's the only tool I've found) at http://www.doodle.com/vwyfmx3e5w3cr8zb to try to find a time we're all available. I've chopped down the times to try to make for reasonable calling times for our geographically-diverse group, hopefully I've done the timezone math correctly. I'd ask you all to think about what you'd like to see out of the 4.x series, especially 4.1. For those returning members, give some thought to what changes to the process you'd like to make. Eric All responses are in. Thanks! It looks like Tuesday the 13th will work for everyone. You should be receiving a call invite from Calliflower shortly (or go to http://apps.calliflower.com/conf/show/108047). I recommend registering with their site so that you don't have to enter a pin number every time you call in. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4.1] Framework Team, let's chat
(I believe everyone is signed up for the FWT list, but cc'ing Craig and Elizabeth, just in case) Once again, congratulations to all of our new and returning Framework Team members! Now that 4.0 is nearing RC status, it's time for us to start talking about the future. I'd like to kick things off with a conference call. Calliflower seemed to work well enough last time, so we'll continue with that. I've set up a Doodle page (oh, how I hate Doodle, but it's the only tool I've found) at http://www.doodle.com/vwyfmx3e5w3cr8zb to try to find a time we're all available. I've chopped down the times to try to make for reasonable calling times for our geographically-diverse group, hopefully I've done the timezone math correctly. I'd ask you all to think about what you'd like to see out of the 4.x series, especially 4.1. For those returning members, give some thought to what changes to the process you'd like to make. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team Members Named
On Jul 1, 2010, at 12:20 PM, Steve McMahon wrote: Congratulations, and thanks, to the members of the new Plone 4.x Framework Team: Alec Mitchell Ross Patterson Laurence Rowe Matthew Wilkes Martijn Pieters Rob Gietema Elizabeth Leddy Craig A. Haynal Congratulations, all! I'm looking forward to working with you all. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone-developers] Plone 4.x Framework Team Nominations Open
I'd like to put in a nomination for Elizabeth Leddy for the 4.x Framework Team. Elizabeth has been working with Plone for quite some time now, but only recently popped up on the community radar at the 2009 conference. Her Unloading Plone talk was hailed as a conference highlight. Since then she's been an irc and planet.plone regular, showing an uncanny ability to mine the depths of Zope and Plone and still be able to relate them to the average user. I had a chance to meet her last week at Plone Symposium East and was able to confirm my feeling that she: 1) really knows her stuff 2) works well with others 3) is willing and able to defend her positions I think she'd make a fantastic addition to the 4.x team. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Improving the process -- PLIP UI and Documentation
FWT! I want to introduce two additions to the PLIP process that I'd like us to add into the Plone 4.1 process. UI: I'm pleased to announce that Plone now (finally/once-again?) has a UI Team. Alex will be heading up the effort alongside Geir Baekholt, Denys Mishunov, Sisi Nutt, and Nathan Van Gheem. I've asked them to serve as a non-blocking vote on each PLIP, providing a group response to each submission. Their goal will be to judge the UI elements of submitted PLIPs for consistency, usability, accessibility, and general saneness. This should give FWT members more time to focus on the underlying codebase. My hope is that the UI team will also be able to serve as a resource for PLIP implementers before and during the implementation phase, providing input on UI matters as needed. Documentation: In an effort to reduce the amount of time the Documentation Team needs to spend chasing down implementers for documentation, Israel is asking that we try to get as much of that taken care of during the PLIP process as we can. Essentially, we'd require that implementers submit full docs (not necessarily required to be well-written, but concept-complete) with their final code implementation. Assistance from the doc team will be available. I think we can get the majority of this content up front if we enforce proper proposal structure (something we were lax on in 4.0). I'd also like to recommend that structure be expanded to include: What existing documentation will need to be updated? What new documentation will need to be created? Will this require migration documentation? Ideally, the implementers would create the documentation directly in PHC, in the correct place, in 'private' workflow state. If updating documentation, implementers would duplicate the current document and edit the copy. The Docs Team will weigh in with their opinion of its status, to apprise the Framework Team of the implementers' compliance with this requirement. I believe Steve will be revving up the process for selecting the 4.x team in the near future. It's my hope that with these two new additions, we can continue to improve our process and reduce the strain on our new team. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
I need to do some backtracking on my previous release plans...
First and foremost, I've completely overestimated the time I'd have available
this week. Preparing for next week's symposium has eaten all of my available
time and I'll be unable to cut a b4 beforehand. I absolutely hate being the
point of failure here, but we can make this work...
I'm now realizing I've put the cart before the horse on scheduling the first
RC. As Hanno points out, we have a number of yet-to-be-completed migration
issues that need to see the light of day in at least one release prior to an
RC. There are plenty of other bugs of all sizes to take care of as well.
The main issues I'd like to see fixed and released before we move to RC are:
#10124 - should remove Large Plone Folder type and expose the folder ordering
setting in the schema
#10360 - Incomplete migration: site_properties and portal_controlpanel
#10363 - Can not edit personal information when one is loged in with email
address
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
We also have scads of finishing touches to make to templates/CSS, including 7
open tickets regarding Alex's introduction of CSS sprites. There are another 23
open tickets relating to TinyMCE. I also need to consult with Sidnei regarding
some concerns over the Windows installer.
As always, there is a full list available to those wishing to try their hand at
the rest. http://tr.im/plone4tix
So let's move the b4 release to June 2, which should give us time to get the
majority of these wrapped up (and provide me with the time to actually cut the
release). At that point, I'll take another look at what's remaining and decide
whether a June 16 release should be dubbed b5 or rc1.
With Jessica's blessing, I'm proclaiming the upcoming May 28th TuneUp an
official Plone 4 bug day. I'd appreciate help in spreading the word.
Thanks,
Eric
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Upcoming Plone 4.0 releases
So here's where we stand, from my viewpoint... 1) Plone 4.0 is feeling like a nearly-finished product (Great job, everyone!) 2) Everyone is getting sick of working on it So let's get an RC1 on the schedule and get this thing out the door. Despite our fine history of making big-name releases during Plone events (see symposia of late May), I'm forced to postpone that by a few days and schedule the RC1 release for Wednesday, 3 June. Why so long? This does three things: 1) (and foremost) Gives the principals on some of our remaining large bugs the time to get those wrapped up 2) One more Tune-up (which I hope to push as a Bug Day). 3) Leaves me with some shred of sanity over what is an exceptionally busy 4 week period. In the interim, I'd like to drop a beta 4 next Wednesday (19 May). This one isn't going to be substantially different from b3, but I think we have enough changes in there to make it worthwhile. I'll be spending time over the next few days digging through our remaining tickets to consider what gets pushed off until 4.x and what should rightly be considered a blocker. I'll regret saying this, but if you have a ticket that needs to be in 4.0, drop me a line and state your case. Mention breadcrumbs though, and you're on your own. ;) In other news: over the next few weeks, we'll hopefully be spinning up the process of constructing our Framework Team for 4.1. We have some really good looking PLIPs already waiting in Trac and I hope you'll consider adding your own in anticipation of 4.1's upcoming submission period. I'm also thrilled to announce that we'll be adding a dedicated UI team to the mix, something that's been sorely needed for some time; more to come in the following weeks. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] 4.0b3 Due 28 April
For those who haven't seen my message in plone-dev, we're pushing the deadline for b3 back a week. Between the slight delay in starting the packaging and the 2 days of soft-release, b2 really hasn't had enough time in the wild to make a difference. This will give us some extra time to wrap up the remaining sticky bits. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Documenting the process
I'm finding that I'm consistently wrong about how I think whole Plone thing works. Every assumption I had coming into this job has been met with some sort of No, we have a process. It's just not documented. Let's fix that. I'm looking for some help in actually writing down the process of how a major release of Plone comes together. Rough list of necessary parts would be: * Choosing a FWT * Choosing a release manager * The role of the FWT * The role of the Release Manager * PLIP review process * By what standards is a PLIP judged? * By what standards is a PLIP implementation judged? * Creating the release Suggestions for missing sections? Anyone willing to help me write this? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 5 - rough roadmap
On Mar 15, 2010, at 4:58 PM, Nate Aune wrote: What about Amberjack for self-guided tours/help? http://dev.plone.org/plone/ticket/9324 Is that still on the roadmap for landing in Plone 4.1? It certainly is if someone resubmits it. I asked the implementers to continue developing it outside of Plone 4 with the idea that they could start building tutorials against something stable in the release candidates and could give it some time to mature on its own after the release is out. Then, we could include it as part of the core for 4.1. I've been gearing up for the sprint, so I haven't had a chance to reply to the discussion. My general plan for 4.1 was to wrap up as many of the nearly-done PLIPs from 4.0. If we can make significant progress this week, I think we could drop a 4.1 very shortly after 4.0 that includes plone.app.discussion and events, search results, and collections improvements (and by extension plone.registry and z3c.form). That'd be one hell of a dot-x release. Even just two of those packages would be enough for me for 4.1. Or we could space them out so we don't raise expectations for 4.2 too much. ;) Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: A suggestion to egg on add-on product authors
Thanks, Jon! I'll take care of this tonight. :) Eric On Mar 9, 2010, at 10:20 AM, Jon Stahl wrote: Bravo! Eric, can I suggest that you take the opportunity of the beta release to send out an email from The Release Manager to the wider Plone community in which you specifically remind add-on product developers to test and update their add-on products, provide a link to the upgrade docs (which already exist, right?) and celebrate the significant number of add-on products that are already Plone 4-compatible? Here's some rough-draft text to get you started -- I just think that you're the most authoritative (read: shame-inducing) messenger. ;-) This should probably go to developers, users, product-developers. Maybe even plone.org/news. best, jon = Plonistas- Plone 4 beta 1 is now out. It's the culmination of months of hard work by dozens of Plone developers -- what we'd originally envisioned as a boring release is now without question the most exciting release of Plone ever: faster, more beautiful and easier to use than ever before. Thanks to all of you who've made it happen! As we enter the beta stage of our release cycle, our focus shifts, splits and widens. We need everyone -- not just core developers and framework team members -- to start testing the beta in as many routine and not-so-routine ways as possible, to find and document bugs, and to join the core developers in making fixes. Fixing bugs is a great way to make your first contributions to the Plone core. Perhaps even more importantly, it is time to focus on testing and updating add-on products for Plone 4. Most products will require only minor changes (if any). We've quietly made a great start on this already -- Plone 4 already has more compatible products at the beginning of the beta process than any previous Plone release! But there is much more to do. If you're the author of a Plone add-on product, your to-do list for the Plone 4 beta cycle should include: 1) Test your product against Plone 4 2) Make any necessary changes -- see http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0 for a detailed overview of the handful of minor changes you need to make -- including tips for updating themes. 3) Tag a new release of your add-on product and upload it to Plone.org. Be sure to set its version compatibility so it shows in the search at http://plone.org/products?getCategories=getCompatibility=Plone+4! Kudos to the many folks who've *already* released Plone 4 compatible versions of their popular products, including: Steve PloneFormGen McMahon David Various Groundwire Products Glick David PDFPeek Brenneman Ralph Classifieds Jacobs Luca custommenu.factories Fabbri Espen SubSkins Moe-Nilssen Nathan PloneTrueGallery Van Gheem Niteoweb Roberto Various Themes Allende Malthe Collage Borch Manubu c2.transform.office Terada Wojciech collective.disqus Lichota G. qiPortletTagClouds Gozadinos ... and more -- see the full list at: http://plone.org/products?getCategories=getCompatibility=Plone+4 Thanks for being out ahead of the curve! If you're an everyday Plone user, you can help by installing Plone 4 beta 1, testing your favorite add-on products, and reporting bugs to the add-on products issue tracker at http://plone.org/products. If you're not already on it, the Add-on Product Developers list is a great place to discuss add-on product compatibility and updates. http://plone.org/support/forums/addons ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: A suggestion to egg on add-on product authors
On Mar 11, 2010, at 8:00 PM, Eric Steele wrote: Thanks, Jon! I'll take care of this tonight. :) Eric On second thought, I'll hold off on this until we have installers available. Eric___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Beta 1 is (essentially) out! FWT, your job is done.
I've just finished getting the last bits of 4.0b1 to wherever they need to be. I'll give it another 24 hours of soft-release before handing it over to the installers folks to make sure everything is there. If I understand this whole Plone process correctly (and I'm not at all sure I do), this means it's the end of the line for the 4.0 Framework Team. I want to thank all of you; you've done an amazing job. You took what was supposed to be a very boring release and turned it into something that everyone is excited about. We gave you heavy workloads and horrible deadlines and and you came through. Well done, all! So... now that those bums are out the door, how do we go about appointing a 4.x team for me to abuse? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] User Preferences Form
FWT,
Back in December, I asked Kees to think about what would be involved in
modifying the two user preferences forms (prefs_user_details and
personalize_form) to function in a way similar to the new registration forms.
It seemed silly that we had this nice new, extensible way to add and remove
fields on the registration forms, but those changes weren't reflected in the
forms the user/admins would use to modify that data once the registration
process was complete.
With apologies to Kees, I'm just going to paste his response to me here...
Hi Eric,
Some time ago you asked me to look into modifying prefs_user_details and
personalize_form, so they take extra fields defined in plone.app.users' forms
into account. I have finally thought about this, and gotten some of the work
on
the way. I'll sketch my proposed approach here.
It seems to me the best way to go is to modify the prefs_user_details and
personalize_form in such a way that work as @@register and @@new-user, that is
with a Zope form class. That seems more than a simple change, and i'm
wondering
if this is what you had in mind. On the other hand, it does give us a chance
to
clean up the code, and fix plip 9311 (https://dev.plone.org/plone/ticket/9311)
along the way. Please let me know if this approach is feasible.
What i've done is create a new form ('@@change-member-details') for this.
(This
form is intended to be renamed to '@@personalize_form' eventually, so it won't
break anything that relies in that name being there.) Currently it will only
display the 'fullname' field and update that. Eventually we could extend
IUserDataSchema so it also includes the extra fields which are currently in
personalize_form, like description (Biography), language, external editor,
wysiwyg editor, visible id's, etc.
The code is in a new plone.app.users branch:
https://svn.plone.org/svn/plone/plone.app.users/branches/user_preferences_form/
I've added a development buildout which uses this branch:
https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0/experimental/user_preferences_form.cfg
(So one can just check out
https://svn.plone.org/svn/plone/buildouts/plone-coredev/branches/4.0 and run
buildout -c experimental/user_preferences_form.cfg)
Note that CMFPlone should remain unchanged for now, until the new forms work.
Kees
I've unfortunately let this slip to the bottom of my todo list. I wanted to
bring it here for more discussion and more eyes. I took a quick look at it and
it seemed like a sane approach. I'd appreciate more eyes.
Down the road, I can foresee a management ui that lists all of these fields and
allows us to select to which of these 4 forms they're available.
Eric___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4 - holidays are over :)
On Jan 6, 2010, at 2:02 PM, Steve McMahon wrote: Regarding the AJAX dialog problems, I just haven't gotten to those because of holiday busyness. I've watched them as they've come in, and they all look like they should be easily fixable. I'll make every effort to get to them soon! I've mainly been checking with Eric on which dialogs would benefit from AJAX. This is all convenience work, so if there's any dialog that is resistant to full fixup, we can easily omit it from the AJAX handling. All of these are set up in a single js file that's part of CMFPlone. Steve Thanks for the update, Steve. Let me know if there's anything I can do to help. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4 - holidays are over :)
On Jan 4, 2010, at 2:42 PM, Hanno Schlichting wrote: Heya. Some of us have been busy over the holiday season and worked a bit more on Plone 4. The next question now is: What is missing for a beta release? I'll allow myself to give my opinion on that. Eric feel free to disagree, it's your call :) In general I think Plone 4 is in good overall shape. But there's some blockers and critical issues noted in the bug tracker, which we need to address. I cleaned up Trac, so the 4.0 milestone only has tickets which are new to Plone 4.0 and should *all* be resolved before a release candidate. But here's the list of things that we need to tackle, before we can label a release beta in my opinion: ...big snip... Looking at this there's still a ton to do. I'll leave it to Eric to figure out whom to encourage to get these things done ;-) Hanno Thanks Hanno. I've been slogging through the changelogs trying to get caught up on what's been done over the last two weeks. Between whatever plague it was that I contracted in late December and the holidays, I've been mostly useless lately. We're definitely close. I'd love to see a beta out by the 18th. I'll start rounding up people to get the worst of it cleaned up. There's a lot above to address, so I'll just make a few points: 1) I've got people (including myself) on most of the user/groups stuff. Some of that needs to be aired out here, which I'll do tomorrow. 2) We *really* need to move away from this whole limi's theme thing where Alex is the point-of-failure for anything template/design related. These are the most visible and obvious bugs and though they're not necessarily the most critical, they're the ones that leave the biggest impression of our doneness. Denys has been picking up some the slack, but I'd like to find 1-3 more people willing to have at it. 3) /me clears his throat in witsch's general direction ;) 4) I'll talk with Steve about the JS issues. He's got quite a lot of tickets assigned at the moment, so I'm guessing he could use some help. Just a cursory look at the problem leads me to think there's a generally easy way of fixing it across the board, but also a nicer, one-less-page-load way that would be much more involved. And on points 2 and 4...what does the UI team do these days, do we still have one? Oh, and you said... Personally I disagree with some of the choices mentioned in the PLIP (like shipping the unmaintained Clouseau, using eggtractor where buildout covers the same use-case today, turning on debug-mode in zope.conf, which should only be done via bin/instance fg vs. bin/instance console) A quick poll in #plone-framework showed that myself and Messrs. Glick and Clark had never heard of bin/instance console. We need to document the crap out of that. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Discontinuing the conference calls
FWT! After getting agreement from 50% of the team on IRC today, we'll just forgo the remainder of our conference calls. If anyone feels the need before 4.0 drops, we'll jump back into them. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] No FWT meeting Nov 18 or 25
Since there's really nothing to discuss worth dragging everyone out of their routines tomorrow, let's skip this week's meeting. I'll be traveling next week, so I'm happy to skip that one as well. I'll touch base on IRC in 2 weeks and see if there's reason for us to meet. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Plone 4 FWT meeting - Nov 11
Gents, I'd like to talk to you all tomorrow during our regular time. There are a few final features being bandied about that we should discuss. I'd also like to talk about the early release schedule. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT, Let's meet up
For those of you in Budapest, I'd like to try to get together for a bit to 1) just actually meet you face-to-face 2) talk about which sprints we want to promote/run this weekend 3) buy you each a beer Think we can make that work? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP9311 status
On Oct 16, 2009, at 6:13 AM, Kim Chee leong wrote: Hi, Just saw the FWT minute meetings and I would like to update you on PLIP9311 status. Most of the work is done. What still needs to be done are a part of the tests and according to the second review the password form isn't working. I've got this form workking locally so the fix is probably easy. So a big part is done but not enough, hence the negative advice for merging with 4.0. But I wil happily make this PLIP read for 4.x. Cheers, Kim Chee Thanks. Expect me to hold you to that. ;) Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Meeting Minutes – Oct 14, 2009
Attending: Alec Mitchell,Ross Patterson, Eric Steele, David Glick Absent: Erik Rose, Laurence Rowe, Matthew Wilkes • Sprints we want to promote after the conference • Add-on sprint: • Make sure popular products are ready to ship with Plone 4 ie... • CacheFu • LinguaPlone • PloneFormGen • Developers Pack products • Do in conjunction with documentation effort • There may be backwards compatibility changes that can be made. Have FWT members around to debate debate what should be done. • Documentation • Performance • Testing • QA Team • CMF release (Eric will drum up support) • Alec will send an email • Release schedule • Get an alpha out ASAP, figure out remainder as we go • Largely dependent on CMF release • https://mail.zope.org/pipermail/zope-cmf/2009-February/028180.html • https://mail.zope.org/pipermail/zope-cmf/2009-September/028633.html • Eric will check in with them, Hanno • Will also need a Zope 2.12.1 release (multibyte splitter). Eric will speak with Andreas. • Bug fixing • Ticket gardening needed • Tag anything with the 4.0 milestone • As we have time, page through the open tickets and assign to Plone 4 • Performance testing • Ross will rerun Plone 4.0 against 3.3, but wait until we're nearly at an alpha stage. • Next call Nov 4th. See you in Budapest! ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Framework Team Meeting Minutes - Oct 5, 2009
Attending: David Glick, Alec Mitchell,Ross Patterson, Eric Steele, Erik Rose, Laurence Rowe, Matthew Wilkes Absent: None * Raphael and Calvin. * Raphael has informed Eric that he'll have to leave the FWT due to time constraints. * Calvin has asked for a leave-of-absence until 4.1, granted by Eric. * Eric: has extended the same offer to Raphael. He's indicated that he appreciate that option. * Alec: I'm OK with that as long as there's some clear explanation of why they couldn't participate this time (despite having volunteered to do so) and of why that will not happen for the next release. * Agreement from the remainder from the FWT. They'd like to seek replacements if not comfortable with the reasoning. Eric will contact both. * Magic number score to pass is now a +4. * Theme PLIP * Matthew is uncomfortable with dropping base_properties use * OOTB project listed base_properties as a standard of a good Plone theme * Basis for simple customization: simple CSS or forms/widgets (CSSManager) * Is this a discussion that really has to do with this PLIP? Removing base_properties is a PLIP in and of itself * This theme is special because it's the ootb default * base_properties is really only particularly useful when using CSSManager * Limi, Veda, Joel, Rob Porter were mentioned as people to bring into the discussion * Matthew was nominated to take this question to the larger community, both because he was so passionate about the issue and he'd left the meeting and could not turn it down. * 9311, needs work yet. Ok to retarget for 4.x release? Probably. * Laurence: 9309 monkey patch would likely be acceptable for inclusion in Zope 2.12.x * 9310: Very close, needs default fields to be added to new registration form. * 9310 and 9330: 9310 creates a new join_form. Who merges these? Recommended aclark do it as his is the less-involved one. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Plone 4.0 Voting finished!
Now that I have Erik's votes in (and, for the sake of time, have decided to overrule Matthew's remaining votes on the remaining two PLIPs in contention), we at last have a full list of accepted PLIPs: 7822Make standard file content types use ZODB BLOB support 8801Move action icon support into actions, remove CMFActionIcons 8802Move our upgrade / migration infrastructure to GenericSetup 8808Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 8814Replace SecureMailHost with a standard Zope mailhost 9186Set Image IDs from Title field 9214Support logins using e-mail address instead of user id 9249Add TinyMCE as the default visual editor 9250Add jQuery Tools to base install 9256 Expand variable substitution in mailing action of plone.app.contentrules 9258 Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget 9259Group dashboards 9263GenericSetup syntax for importing Sharing page roles 9264Merge backport patches from plone.app.dexterity into Plone 9272Exposing and editing Dublin Core properties 9285Show blocked portlets in management interface 9286Allow to show/hide portlets 9305Use real names instead of usernames 9309Better search for East Asian (multi-byte) languages. 9310User registration process more flexible 9315New theme for Plone 4 9316Unify folder implementations 9321Reimplement the search form with an eye on usability 9330Add ability to choose role when adding new site members I'll be updating tickets and will send out an email to the dev list today expressing our congratulations/gratitude for everyones' work. I'm setting the merge deadline for next Friday. Matthew, would you be available to get out a news item now that we have a real list of features? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Tomorrow's meeting, PLIP reviews/voting, and Raphael
FWT! Just a reminder that I'd really like to have all of your votes in by tomorrow's meeting (same time, same place). We'll hammer out any remaining voting questions and discuss what happens next. Two PLIPs have passed the acceptance threshold: 9249Add TinyMCE as the default visual editor 9250Add jQuery Tools to base install The following PLIPs have updated reviews (or the reviewers have indicated that their opinion has not changed) and need your votes: 7822Make standard file content types use ZODB BLOB support 8801Move action icon support into actions, remove CMFActionIcons 8802Move our upgrade / migration infrastructure to GenericSetup 8808Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 8814Replace SecureMailHost with a standard Zope mailhost 9186Set Image IDs from Title field 9256 Expand variable substitution in mailing action of plone.app.contentrules 9258 Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget 9264Merge backport patches from plone.app.dexterity into Plone 9272Exposing and editing Dublin Core properties 9288Improved commenting infrastructure 9305Use real names instead of usernames 9310User registration process more flexible 9311Clean up of user related actions UI 9315New theme for Plone 4 9316Unify folder implementations 9330Add ability to choose role when adding new site members We still need updated reviews (or just a no change confirmation) from: Erik: 9214Support logins using e-mail address instead of user id 9263GenericSetup syntax for importing Sharing page roles 9285Show blocked portlets in management interface 9286Allow to show/hide portlets 9321Reimplement the search form with an eye on usability Laurence: 9259Group dashboards Matthew: 9309Better search for East Asian (multi-byte) languages. Also, Raphael has expressed his regrets that he must leave the Framework Team due to time constraints. Raphael, I think I speak for all of us when I say: thank you for your hard work and we're sorry to lose you. I have to follow that up with procedural question: This obviously drops the number of team members to seven. Is the feeling of the group unchanged in that we need five total votes to consider a PLIP properly assessed or will four (still 50%) now be sufficient? Itchin' to merge, Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plip #9321, was: PLIP9311, postpone final implementation deadline
On Oct 1, 2009, at 3:45 AM, Carsten Senger wrote: Hi all, --On Donnerstag, Oktober 01, 2009 09:13:01 +0200 Kim Chee leong le...@goldmund-wyldebeast-wunderliebe.com wrote: Hello framework team, Today is the final implementation deadline for the PLIPs. I'm working on PLIP 9311 'Clean up user related actions'. I would like to request a postpone for the deadline. I can deliver a final version next week (wednesday 7 October). I'm requesting the delay because I forgot the deadline date and I expected that the deadline date would be moved because of the delayed reviews. I already started working on the review comments from Rob but stopped because I was waiting on the second PLIP review. I know it's my error that I didn't noticed the deadline of the PLIP implementations and I hope it's possible to extend the deadline so I can deliver a proper PLIP. Ofcourse I'm willing to buy you a few beers when we're in Budapest :-). I've also can't finish #9321 within the deadline. I will finish it this weekend, would be happy if the framework team accepts it nonetheless and join Chee Leong bribing the framework team members. ..Carsten I'll give you both until the end of the day on Saturday. After that and it'll be necessary to bump it to a 4.x release. The FWT needs time to review and vote. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Final Voting for Plone 4.0
FWT, It's time to start voting on PLIPs again. We're looking for up or down votes on each of the submissions. The following PLIPs have updated reviews and are ready for your vote. A reminder that we've agreed that we need a minimum of 5 votes for each PLIP . Please record your vote in the PLIP ticket for posterity and in the spreadsheet for my ease-of-tallying. 7822Make standard file content types use ZODB BLOB support 8801Move action icon support into actions, remove CMFActionIcons 8802Move our upgrade / migration infrastructure to GenericSetup 8808Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 8814Replace SecureMailHost with a standard Zope mailhost 9186Set Image IDs from Title field 9249Add TinyMCE as the default visual editor 9250Add jQuery Tools to base install 9256 Expand variable substitution in mailing action of plone.app.contentrules 9258 Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget 9264Merge backport patches from plone.app.dexterity into Plone 9272Exposing and editing Dublin Core properties 9305Use real names instead of usernames 9310User registration process more flexible 9315New theme for Plone 4 9330Add ability to choose role when adding new site members Erik and Laurence, we also need updated reviews (or at least confirmation that your recommendation has not changed) for the following: 9214Support logins using e-mail address instead of user id 9259Group dashboards 9263GenericSetup syntax for importing Sharing page roles 9285Show blocked portlets in management interface 9288Improved commenting infrastructure I'd like to get this wrapped up by Monday, so that I can start the merge process. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Final PLIP reviewing and voting
FWT!, It's final review time for 4.0. We currently have 6 PLIPs awaiting final review and merge vote: 9186Set Image IDs from Title field 9259Group dashboards 9285Show blocked portlets in management interface 9263GenericSetup syntax for importing Sharing page roles 9272Exposing and editing Dublin Core properties 9305Use real names instead of usernames I'll be rearranging the spreadsheet (http://bit.ly/plips) as new ready- for-merge PLIPs come in. Please update your reviews and give us your recommendation. Everyone should be recording their final votes in the PLIP ticket (for posterity) and adding it to our tally in the spreadsheet (for easy tracking). Guest reviewers, we'd appreciate updates to your reviews as well. During yesterday's meeting, we decided that a minimum of 5 votes was needed to make a call on a particular PLIP, with at least half of those votes being positive to merge. If you're unable to review and/or vote, please, let me know. Seriously. I'd much rather know you're not going to do anything than hope you'll do something. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: [Plone 4] Final PLIP reviewing and voting
On Sep 24, 2009, at 9:03 PM, Martin Aspeli wrote: Eric Steele wrote: FWT!, It's final review time for 4.0. We currently have 6 PLIPs awaiting final review and merge vote: 9186Set Image IDs from Title field 9259Group dashboards 9285Show blocked portlets in management interface 9263GenericSetup syntax for importing Sharing page roles 9272Exposing and editing Dublin Core properties 9305Use real names instead of usernames What does this mean for the other PLIPs? - the author hasn't completed required showstopper changes in time? - the reviewer hasn't reviewed their changes? I think the CMF add-views PLIP should be ready as well, as mentioned on the ticket and this list. Martin It means the author hasn't indicated that the PLIP is ready for review/ merging or I've managed to completely missed that indication. #9264 added. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] Framework Team Minutes - Sept 23, 2009
Attending: Eric Steele, Erik Rose, Ross Patterson, Alec Mitchell, David Glick Absent: Calvin HP, Raphael Ritz, Matthew Wilkes, Laurence Rowe Short meeting as everyone is still recovering from initial review period. • So what now? • Eric's been preoccupied this week and didn't send out a reminder email to the initial wave of implementers (shaaame). Everything is due by next Wednesday so we can do a final review. • Missing FWT members? Make sure they know that voting is happening and where it lives. • Accounting for them...How many votes do we need to accept for merging? 50%+1 with a minimum of 5 votes. • Eric will update FWT on which PLIPs are ready for merging. • Reviewers, please update your reviews for the merge-ready PLIPs. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting Minutes - Sept 9, 2009
Attending: Eric Steele, Alec Mitchell, Ross Patterson, Erik Rose, David Glick Absent: Calvin HP, Laurence Rowe, Raphael Ritz, Matthew Wilkes * Break deadlines into chunks. Some of these need more review than others. * Alec will pick up #9309. Ask Vincent Fretin to guest-review. (Later note: He's said yes.) * Concern about failing tests. Some of this is due to things being fixed after PLIP branches were made. * Really only comfortable judging PLIPs with two reviews. Some of the simpler ones are fine with just one. * 9250: Name change has been made. Plone 4 should use this somewhere. Tabs? Fieldsets? * 9258: Well tested, good package. Should dialog be inline/modal? * 9259: In favor. * 9295: Fairly incomplete at this point. Difficult to review. Needs much polish, user testing. Basic UI concepts are good. No migration from existing collections. Ross is working on benchmarks. Candidate for a minor release. We'll see where they are in 2 weeks. * 9315: Has a destination in mind, just hasn't reached it yet. Suggest Alex find someone to help with the non-design parts of the PLIP (failing tests, repackaging of existing theme). * 9329: Needs a lot of UI work, but is on the right track. Also a candidate for a minor release if needed. * 9285: Mostly complete. Link needs to be changed. * 9286: Needs new CSS style for hidden portlets. Needs migration for old static portlets. * 9376: Optimizations made in archetypes.schemaextender have rendered this moot. * 9186: In favor. Do we cover files with this as well? Generally * 9272: Don't need per item on/off. Eric updated review accordingly. * 9284: This is really more of a bug to be fixed in CMF than something we should be patching in Plone. * Eric will send out another email tossing shame and roses as appropriate. Also request some volunteers for guest reviews. * The above PLIPs were judged. Let implementers know that their PLIPs have been evaluated. They can refute any suggestions on list or in ticket. They'll have 2 weeks to complete the suggested changes. After the meeting, we also waved through #9330. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Framework Team: Time is short, we need your reviews.
Framework Team, Friendly cajoling has not produced results, so the time has come for some public shaming. Your initial 2 week PLIP implementation review period came and went. We added another week. With 24 hours left on that new deadline, we're not much closer to being finished. Shame. Shme. We'd agreed that each of you would review a minimum of 6 PLIPs. Here's the breakdown of what you've done so far vs what you signed up for: David Glick 5 of 7 Calvin HP 0 of 6 Alec Mitchell 5 of 6 Ross Patterson 0 of 8 Raphael Ritz0 of 0 Erik Rose 3 of 7 Laurence Rowe 1 of 2 Matthew Wilkes 0 of 6 In total: 14 of 42. Ugh. Half of the team hasn't completed even one review, which tells me that providing more time won't be at all productive. In order to have any sort of discussion, we're going to need at least one full review per submitted PLIP. To this end, I'm assigning you each 1-2 PLIPs to cover so that we can move on and stop delaying Plone 4. I've tried to account for relative complexity of each PLIP, the number you've completed so far, and the number I think you can realistically complete before tomorrow's FWT meeting (I'm leaving out Raphael because I haven't heard a peep from him in 6 weeks). 9214Support logins using e-mail address instead of user id Erik Rose 9249Add TinyMCE as the default visual editor David Glick 9263GenericSetup syntax for importing Sharing page rolesCalvin HP 9283A more lightweight backend for collections Alec Mitchell 9288Improved commenting infrastructure Laurence Rowe 9305Use real names instead of usernames Ross Patteson 9309 Better search for East Asian (multi-byte) languages. Matthew Wilkes 9310 User registration process more flexible Ross Patterson 9311 Clean up of user related actions UI Matthew Wilkes 9321 Reimplement the search form with an eye on usability Erik Rose 9330Add ability to choose role when adding new site members Eric Steele 9352 Search results improvements Calvin HP In conclusion: Shame. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP load test reports available
Thanks so much for doing these Ross! These Plone 4 vs previous versions comparisons are going to be great for marketing. I'll put out a post touting our progress on Tuesday (was going to do it Friday, but didn't want to see it swallowed up by the holiday weekend here in the US). One thing we need to keep in mind with the PLIP comparisons is that many of them haven't merged in changes to CMFPlone and other packages since they did their initial branches so that may be one of the factors in their speed differences. I'll have to check with the guys at the office, but we may be able to spare a VM to do this sort of thing regularly. Eric On Sep 6, 2009, at 5:03 AM, Ross Patterson wrote: You can find funkload load test benchmark reports and comparisons at: http://weblion.psu.edu/static/loadtesting/plone4.0/plips.html The buildout logs for the individual plips can be found with the same name as the *.cfg file substituting .log for .cfg in: http://weblion.psu.edu/static/loadtesting/plone4.0/ So if a PLIP looks like it has erroneous results take a look at the log and let me know if there's anything to be done to get valid results. Do this soon since the EC2 instance is costing me money so I will take it down soon and I won't want to set the whole thing up again once I take it down. You may also be interested in the following: - Plone 4.0 base against Python 2.4, 2.5, and 2.6 http://weblion.psu.edu/static/loadtesting/plone4.0/base.html - Plone 4.0 against Plone 2.5, 3.0, and 3.3 http://weblion.psu.edu/static/loadtesting/plone4.0/versions.html - Plone 3.3 write conflict error comparison http://weblion.psu.edu/static/loadtesting/plone4.0/threads-retries.html (interesting how well 1 ZEO client with 1 thread does against 2 ZEO clients with 1 thread each) Limi and I are working on adding some explanatory text and legends to these reports but for now this is all you get. :) Click through and around and if there's anything you still can't make sense of, ask and I'll see what I can do. Ross ___ 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: [Framework-Team] Re: PLIP load test reports available
On Sep 6, 2009, at 1:02 PM, Ross Patterson wrote: Eric Steele ems...@psu.edu writes: ... One thing we need to keep in mind with the PLIP comparisons is that many of them haven't merged in changes to CMFPlone and other packages since they did their initial branches so that may be one of the factors in their speed differences. Any chance we can get implementers to do this? ... Definitely. It'll make my life easier when merge time comes as well. I'll ask them to get their branches up to date during the next implementation run. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting minutes - Sept 2, 2009
In the call: Eric Steele, Alec Mitchell, Ross Patterson, Erik Rose, Laurence Rowe, David Glick * We're really behind on reviews, unfortunately we'll have to add another week. Eric will email the dev list to alert everyone of the change. * We need everyone to cover at least 8 reviews for proper coverage. * No word from Raphael for several weeks. Check in on him. * Ross is generating funkload reports for each PLIP vs base Plone 4. Working on a base Plone 3 vs Plone 4. * More discussion of plone.app.registry. Erik gave the package a closer look this week. Generally happy with it, is +1 on inclusion. Group's general feeling hasn't changed much from Yes, but with reservations. Erik created tickets for discussion at http://dev.plone.org/old/plone/ticket/9472 and http://dev.plone.org/old/plone/ticket/9473 * David raised concerns about #9352's 15% slowdown for search results. Detailed profiling needed. * #9376 (archetypes.schematuning): Opinion has soured greatly after reading Alec's review and subsequent discussion in #plone-framework * #9258 (archetypes.referencebrowserwidget): We're all happy with it. Use overlays? Modailty would be a concern * #9329 (TTP actions): Eric feels it needs much work. Good candidate for a 4.x release. * More guest reviewers? alcark? stevem? In a fit of UI muckification, we've added some columns for voting to the Implementation Reviewers spreadsheet (http://bit.ly/plips). Add a +1 if you're happy with the implementation. Lowest scores get discussion priority at next week's meeting. Homework for next week's meeting: Finish your reviews, try to do at least 8. Read over others' review notes and vote so that we have an idea of which need the most discussion. Audio at http://apps.calliflower.com/conf/download/3987?rec_key=a16357e17e0f0577d121129f6287a8855a4d0014 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Status of PLIP 9315 — Ne w theme for Plone 4
On Aug 17, 2009, at 4:17 AM, Matthew Wilkes wrote: ... • A theme skeleton — plonetheme.sunburst — that Denys checked in for me while I was flying across the Atlantic. Unfortunately this is just a blank skeleton still, since I can't get Plone running at the moment. How does this relate to zopeskel? plonetheme.sunburst is a zopeskel-created theme. It just doesn't have anything in it yet. I believe that's what he means by skeleton. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIPs ready for review
The following 27 PLIPs have been indicated as being ready for review: 7822Make standard file content types use ZODB BLOB support 8801Move action icon support into actions, remove CMFActionIcons 8802Move our upgrade / migration infrastructure to GenericSetup 8808Require Python 2.5 or 2.6, Zope 2.12, and CMF 2.2 for Plone 4.0 8814Replace SecureMailHost with a standard Zope mailhost 9186Set Image IDs from Title field 9214Support logins using e-mail address instead of user id 9249Add TinyMCE as the default visual editor 9250Add jQuery Tools to base install 9256 Expand variable substitution in mailing action of plone.app.contentrules 9258 Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget 9259Group dashboards 9263GenericSetup syntax for importing Sharing page roles 9264Merge backport patches from plone.app.dexterity into Plone 9272Exposing and editing Dublin Core properties 9284Allow views to override skin layer elements easily 9285Show blocked portlets in management interface 9288Improved commenting infrastructure 9295 Improved UI for collections (merged with 9283 for review: A more lightweight backend for collections) 9305Use real names instead of usernames 9309Better search for East Asian (multi-byte) languages. 9316Unify folder implementations 9321Reimplement the search form with an eye on usability 9327Unified interface for lists of content 9330Add ability to choose role when adding new site members 9352Search results improvements We also have 2 PLIPs that depend on the outcome of the theme PLIP and will require a later review: 8805Do not ship with NuPlone anymore 9300Well formed, valid XHTML And two that are installer options: 9314Plone Developer Pack option for installers 9322 Ensure that Plone 4 can upgrade Zope on Windows and Mac OS X via binary eggs (See our spreadsheet for the full list of PLIPs http://spreadsheets.google.com/ccc?key=rR4UAIObeTZtdUExfYophHw) If we stick with the 2 reviewers/PLIP that we'd discussed last week, that means at least 6 reviews per FWT member. I'm going to make the assumption that you'll want some help with these. I think there are some cases where we'd be best served having one FWT review and one external review for a PLIP. Hanno has offered to pitch in and I'd like to see him review David's backporting PLIPs. Some would benefit greatly from a UI team reviewer (do we need a UI review of the collections work since half of the UI team worked on it?) I've also asked accessibility evangelist Christian Vinten-Johansen here at WebLion to look at some of these for possible accessibility issues. If there are others you'd like to bring in, let me know and I'll make it happen. Our deadline for reviews is August 30. We can discuss the feasibility of that during Wednesday's call. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [Plone-developers] Adding dependency on plone.registry
On Aug 14, 2009, at 8:14 AM, Geir Bækholt wrote: In our work on the collections-PLIPs: #9283 and #9295 https://dev.plone.org/plone/ticket/9283 https://dev.plone.org/plone/ticket/9295 …we have found a need to persistently store configuration data. Our options are: 1) either to write a new persistent utility/tool that keeps this data, then adding new genericsetup handlers for it and all the work that comes along with this or 2)Use the shiny new plone.(app.)registry that Hanno has built for this exact purpose (for Plone 5) While this is a rather large dependency (it depends on z3c.form), we believe the advantages outweigh the drawbacks. As this will probably be the de-facto standard of storing configuration data in the near future anyway, it seems silly to spend big lots of work creating something that will be redundant in the near future. The fourdigits-team also wants to use the registry for the TinyMCE- plip: https://dev.plone.org/plone/ticket/9249 We'll add the dependency now — and hope that the framework team will signal us as soon as possible if this change should be reverted. -- Geir Bækholt in collaboration with Hanno Schlichting Ralph Jacobs Rob Gietema Roel Bruggink I'm generally in favor, with the stipulation that somebody takes ownership of getting it ready for real world use and it goes through its own FWT review process (to make sure it's right, rather than for inclusion). CC'ing the FWT*, in the hopes that we can get some solid discussion on this now instead of waiting until next Wednesday's phone call. Eric * Though I'm sure all are subscribed to Plone-dev, I just want to push it somewhere they're more likely to notice it. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIPs ready for review
FWT, We have 3 PLIPs that are ready for review with quite a few more not far behind. https://dev.plone.org/plone/ticket/9259 https://dev.plone.org/plone/ticket/9263 https://dev.plone.org/plone/ticket/9264 I'll be keeping our spreadsheet (http://spreadsheets.google.com/ccc?key=rR4UAIObeTZtdUExfYophHw ) updated to show PLIP status (in the Implementation Reviewers section). We'll need 1-2 people to review each of these. I've not seen any code or comments from Carsten Senger, Ricardo Alves, and of course, Mr. Limi. Does anyone know of their status? Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Good spot for documentation of ready-for-review plip?
Yes, sorry. I'd meant to send out an email detailing this procedure for everyone. I'll be sure to do that shortly. The FWT decided that a readme placed in the 4.0 buildout's plips folder would be preferred. Bonus points for linking to it (or the changeset that adds it) in your PLIP ticket. See http://svn.plone.org/svn/plone/review/plip240-locking-improvements/PLIP_240_README.txt for an example of what sort of readme the FWT would like to see. Eric On Aug 6, 2009, at 7:52 PM, Maurits van Rees wrote: Hi, I am working on plip 9214 (email logins - not finished yet). I wonder what the best spot is for adding some documentation about this plip (or others plips) with pointers for the framework team. I think most plip authors used to add a README.txt to the branch that had the plip implementation. But the plips are now just config files in the same directory. So where do I put this? - Something like plone-coredev/branches/4.0/plips/doc/plip9214.txt ? - The trac ticket of the plip ? - A mail to the framework list? - Copy/paste to all of the above? -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ 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
[Framework-Team] #9310 (User registration process more flexible)
FWT, As previously noted, https://dev.plone.org/plone/ticket/9310 has been abandoned by the implementer due to time constraints. Given the current state of the code and the scope of the proposal, we're not going see this one completed for 4.0. I'd like to see if we can get *something* into 4.0 that could be built upon in a 4.x release to make this happen though. Are there steps in the right direction that we could take? Alex Clark has expressed a willingness to contribute if time allows. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] today's meeting
On Jul 29, 2009, at 1:03 PM, Hanno Schlichting wrote: On Wed, Jul 29, 2009 at 6:26 PM, David Glickdavidgl...@onenw.org wrote: A couple things I'd like to talk about: * Upgrade policy. Currently Plone 3 supports migrations from Plone = 2.0.5. I was hoping to be able to do that for Plone 4 as well, but there is a tradeoff. Plone 4 no longer has any runtime dependency on GroupUserFolder, so I was hoping we wouldn't need to depend on it any longer. However, it is still needed in order to migrate Plone sites from before we used PAS (e.g., Plone 2.5). I think we have 2 options: Thoughts on which is preferable? 3. What about supporting upgrades from Plone 2.5 final and later? These sites all have PAS installed already. Since 2.5 is considered a major version, we would still support the upgrade from the last two major versions of Plone instead of one. 2.5 also introduced GenericSetup, and with an upgrade machinery depending on GS it is easier to have that in place before any upgrade. I'm comfortable with that. I've only attempted it once, but the 2.0.x - 3.x migration I've done needed a pass through a 2.5 instance to work properly anyway. * wicked / AdvancedQuery. See https://dev.plone.org/plone/ticket/ 9398 ...Does removing this dependency make sense? Is someone willing to volunteer to make the needed change in wicked? I think the change makes sense. AdvancedQuery was only accidentally included as a dependency of wicked and never got a proper risk analysis. With Dieter Maurer now essentially gone and as far as I know no longer doing any Zope development, we don't have any chance of updating AdvancedQuery to silence all the deprecation warnings for 2.12. I can take that on. I It's time I got my hands dirty instead of sitting back and letting David do all of the fun stuff. ;) ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] PLIP #9305
Laurens sent me a document outlining how he plans to implement his PLIP (#9305: Use real names instead of usernames) and asked that I forward it along to the FWT to see if it meets your approval. I've attached it to his ticket at https://dev.plone.org/plone/attachment/ticket/9305/Fullname%20proposal.pdf I've asked him to go ahead and start a topic on plone-dev but figured I'd give you a heads-up. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] archetypes.schematuning
I've asked Jens and Hedley to resubmit their archetypes.schematuning PLIP as it was one of the more interesting ones from the old roadmap that didn't make it into Trac. Please take a look at their proposal, I'd like to get your opinions on this one. https://dev.plone.org/plone/ticket/9376 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] July 15, 2009 FWT Meeting notes
Apologies for missing a few weeks of recaps. I'm going to start volunteering people to do these... Attending: David, Raphael, Eric, Erik, Alec, Ross Short meeting this week. Work is getting started. We have at least 4 PLIPs being worked on at the moment. 5 weeks remaining. Divvied up remaining unclaimed PLIPs (5 owners) https://dev.plone.org/plone/query?status=newgroup=ownerorder=prioritycol=idcol=summarycol=prioritycol=componentmilestone=4.0type=PLIP Will email the owners to make sure that 1) they're actually the PLIP implementer and 2) they're still willing to do the work. David: Zope 2.12 support moving along, could use help making sure tests pass. Will start filing tickets. For next week: Everybody go through and pick out 5 PLIPs to oversee, marking the spreadsheet as you do so. Feel free to claim your own. Eric would like to have a second person to help keep an eye on progress/as we move towards the implementation deadline. Recording at: http://apps.calliflower.com/conf/download/3777?rec_key=052187714e6203565e6f4f4098f7718559d4a470 Next meeting will be next Wednesday, same time. http://bit.ly/UttjX A reminder that I've got an ical feed of Plone 4 meetings and deadlines at http://bit.ly/plone4ical Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] FWT Meeting 8 July 2009.
This week's meeting will be Wednesday, July 8 at 19:00 UTC. We have a few outstanding PLIP matters to discuss. Are there other items for the agenda? Call info is at http://bit.ly/eTSg9. Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] [Plone 4] FWT meeting June 30, 2009
Since I haven't received updated availability from everyone, we're going to stick with our normal day and time (Tuesday, 18:00 UTC) for this week's conference call. This week's agenda: PLIPs. Call details are at http://bit.ly/1akaCu We're 58% of the way through the voting process. Let's get those finished up! Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone 4] FWT meeting June 30, 2009
On Jun 29, 2009, at 9:29 AM, Eric Steele wrote: We're 58% of the way through the voting process. Let's get those finished up! Correction, we're 45% done. *prod* *prod* ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP Change Mailing List
On Jun 24, 2009, at 7:14 PM, Steve McMahon wrote: All the 4.0 PLIPs now have plip-advisor...@lists.plone.org in the CC list. If you want to subscribe, visit: http://lists.plone.org/mailman/listinfo/plip-advisories Most were added in the last few minutes, so previous activity is not in the archives. Fantastic. Thanks Steve! Eric___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Plone 4 FWT meeting summary 2009-06-23
Present: - David Glick - Alec Mitchell - Ross Patterson - Raphael Ritz - Erik Rose - Eric Steele - Matthew Wilkes Discussion: * Eric needs a new headset. * Haven't heard from Calvin lately. Eric will check in with him. * We have 57 PLIPs to evaluate, more than any previous version of Plone (we're told), with less time than any other major release. #$@! * Keep initial review period as short as possible, we'll try to finish before next week's meeting. Can go over any problem areas then. * PLIP gardening: * Mark any incomplete or excessively ill-formatted PLIPs as invalid with a friendly message asking submitter for some cleanup. They can be reopened and considered once they're in an improved state. * Between those and the obvious yes/no submissions, we should reach a much more manageable number for more in-depth review. * Will set up a Trac page to track PLIPs and who will be investigating each. * Would be helpful to be automatically CC'ed on all PLIP changes. Would be too much noise for the FWT list, let's create a new one. Ross will try to get that set up. * Schedule of deadlines at http://bit.ly/plone4calendar. Everyone feels comfortable with the Aug 16 initial implementation deadline. Will allow 6.5 weeks of work. * Timing of call is somewhat inconvenient for some. We'll see if we can reschedule. New poll at http://www.doodle.com/zf9hkvyexzgi98tt, please fill out before next week. We'll meet weekly from now on. I think that was everything. Apologies for not getting names all names and tasks matched up, I don't recognize you all by voice yet. ;) Calliflower seemed to work well enough. If there are no objections, I'll ask the foundation board to set us up with an account. Audio version is available at http://apps.calliflower.com/conf/download/3571 Eric ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
