http://blog.gmane.org/gmane.comp.web.zope.plone.teams.framework hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3700 <pre>May 8 Framework team meeting Present: Eric Steele, Alec Mitchell, David Glick, Liz Leddy; Absent: Craig Haynal, Ross Patterson, Martijn Pieters, Laurence Rowe, Rob Gietema. - There has a been a pattern of the European team members missing meetings as of late. Do we need to reschedule the call for a better time? Is it time to issue a call for new team members and ask inactive ones to step down? - Plone 4.2 update: Eric is releasing rc1 today! - With the finalization of Plone 4.2, we have set cutoff dates for Plone 4.3 PLIPs: 1. Implementations should be done by May 31. 2. Reviews and merging should be done by June 11. 3. PLIPs not meeting these deadlines will be considered for 4.4. - PLIP 12235 (batching): Merged. - PLIP 11773 (Dexterity): Merged. - PLIP 11838 (z3c.form portlets): Still ready for merge. - PLIP 12110 (ignoring accents in search): Still ready for merge. - PLIP 12227 (theme editor): A group from UCLA has volunteered to help review it. Martin is finishing tweaks. - PLIP 12266 (css class for portlets): Alec has asked implementers for a review buildout. - PLIP 12844 (update TinyMCE): David tried to review but had trouble; has asked for instructions on getting it set up to review. - PLIP 10886 (plone.app.event): We're assuming this one won't make 4.3 at this point. But we like surprises. - PLIP 12350 (jquery ui): Eric will check in with Steve. - PLIP 12776 (remove kupu): Done. (But needs to be documented.) - PLIP 12870 (PlonePAS portrait updates): Approved for core. Liz is champion. - Eric asked whether people are using inline editing. If we can drop it, it will simplify the task of removing our use of KSS. ---------- David Glick Web Developer davidglick-jwYafjbudsc+uJoB2kUjGw&lt; at &gt;public.gmane.org 206.286.1235x32 Are you engaging? Find out! Use our free engagement benchmarking tool. http://groundwire.org/labs/engagement-strategy/diy-benchmarking-survey </pre> David Glick 2012-05-08T18:40:20 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3699 <pre>There wound up being multiple occurrences of our call in Calliflower. I've deleted the duplicates (which is why you've all received a cancellation message or 5). Call is happening today, normal time. Eric </pre> Eric Steele 2012-05-08T16:32:44 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3694 <pre>April 24, 2012 – Framework Team Meeting Attending: Eric Steele, David Glick, Ross Patterson, Alec Mitchell, Craig Haynal, Laurence Rowe, Liz Leddy - PLIP 11965 (ResourceRegistries resource bundles): Eric merged for 4.2. Clearing up test failures introduced. - PLIP 8699 (Published date): framework team has no concerns, go ahead with implementation. - Discussion on lists re theme control panels: Agreement that having 2 control panels is non-ideal, but not sure best way to resolve. Suggestions welcome. - PLIP 12844 (Switch to new version of TinyMCE): Approved for core. Next step is review of implementation. davisagli is champion, eleddy will also review. - Jens Klein's proposal about handling portraits via property sheets. Liz will follow up to get him to submit a PLIP - PLIP 10886 (new event type): still in progress, may not be ready for 4.3. - PLIP 12110 (plain text searches ignore accents): ready for merge. - PLIP 10959 (API for password validation policy) and 12521 (Customizable password generation &amp; validation): Liz will touch base and ask them to coordinate. - PLIP 11773 (Dexterity): David will merge soon. - PLIP 11838 (z3c.form support for portlets): ready for merge. - PLIP 12024 (Non-inherited portlet assignment context): closed due to lack of response from author. - PLIP 12266 (add adjustable css class option on static portlet and collection portlet): ready for review. Ross and Alex will review. - PLIP 12350 (Integrate selected portions of jQueryUI - DRAFT): Eric will ask Steve McMahon to champion. Okay for 4.3 if it's ready but won't hold up 4.3 for it. - PLIP 12238 (Add multi-sources personalize form extension): Clarified that this was rejected some time ago. ---------- David Glick Web Developer davidglick-jwYafjbudsc+uJoB2kUjGw&lt; at &gt;public.gmane.org 206.286.1235x32 GiveBIG is coming! Mark your calendar for May 2 and get ready to give big to Groundwire on this community-wide day of giving. http://www.seattlefoundation.org/npos/Pages/Groundwire.aspx </pre> David Glick 2012-04-24T19:03:33 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3693 <pre>Since this one is relatively minor and has been done for some time, I've made the executive decision to just include it in Plone 4.2. (Doing so allows me to clear up some HTML 5 that snuck into the 4.1 branch) So it's completely on me if I've gone and blown everything up. Eric </pre> Eric Steele 2012-04-19T00:47:28 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3689 <pre>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 </pre> Eric Steele 2012-04-01T23:04:33 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3688 <pre>Been meaning to do this for a while, but got a bit of a kick in the pants this week. Previous meeting minutes are at http://bit.ly/plonefwt. I'll make no guarantees of the quality of the notes taken, but some info is better than none. -- Eric March 27, 2012 – Framework Team MeetingAttending: Eric Steele, Ross Patterson, Elizabeth Leddy, Alec Mitchell, Craig Haynal Absent: Martijn Pieters, Rob Gietema, Laurence Rowe David Glick has offered to rejoin the FWT. All in favor. 4.2 blockers cleared. Eric is fixing some failing tests. RC1 this week, hopefully. Can we get minutes out to the developers? Yes. We’ll start today. #12452 (plone.app.jquery) merged into 4.2. #12350 (Integrate portions of jQuery UI) Portions (if not all) of this are integrated into the theme editor PLIP Any objections to this moving forward? None. #12776 (Remove kupu): Simple change, largely removed already. Would be good to pull out tools (link checker, etc) for general use. They’re handy, but this isn’t a requirement. 12110 (Plain text searches ignore accents): Looks good, but could use review by another with i18n experience. 10959 and 12521: Eric will contact the implementers to see if they’re willing to pool resources When can we start merging to a 4.3 branch? Eric is trying to keep only 2 active branches going at a time for sanity’s sake. 4.2 is wrapping up now, so will cut a 4.3 branch this week. Next meeting: Apr 10. Audio: http://apps.calliflower.com/recording/download/24017?rec_key=bd4fd9981d9eaa2261899e06e59cf18cd3478543 Plone FWT Meeting Minutes: http://bit.ly/plonefwt </pre> Eric Steele 2012-03-27T18:48:28 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3673 <pre>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</pre> Eric Steele 2012-03-06T01:28:42 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3669 <pre>For everyone who wasn't at the meeting today, which was almost everyone, we decided to move from weekly to biweekly meetings again. In exchange, please do *1* plip review before the next call. There are plenty still on the chopping block. One of primary concern is the search ignoring accents plip - a couple of us will review it but we are plain old english speakers. Any ideas on multiligual plonistas who could jump in and help? Liz </pre> Elizabeth Leddy 2012-02-14T19:33:42 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3668 <pre>I'm not going to be able to make the FWT call today; sorry. -- Craig Haynal WebLion - http://weblion.psu.edu/ Teaching and Learning with Technology Information Technology Services Penn State Plone Symposium East 2011: http://bit.ly/pse-email </pre> Craig Haynal 2012-02-14T11:36:29 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3664 <pre>Yo FWT peeps - I just finished reviewing a plip, the first time not in svn and I think there are some things that to happen for me to actually review more plips and not be intensely frustrated. I suspect anyone who reviewed plips already would agree with some if not all of these. People won't do reviews if they are frustrated and/or it takes freaking forever. These complaints are mostly rooted in the new github setup. I know how *I* use github and I hear there are a lot of reasons why we don't use it differently for plip reviews. I am not qualified to make suggestions because my head spins with all the arguments back and forth, I was hoping to just complain and then have you guys tell me to either can it or maybe we can work out something resembling sanity. Forking Mad: People love forking! 1. When people fork, it means that I have to delete my src/Plone.CMFPlone folders and any other folder that's now elsewhere, then rerun the long arduous process of downloading that honkeriffic package. (Grr). We need a best practice here. Would branch the coredev buildout for each PLIP solve this problem? How can we get people to stay in the plone namespace on github? Can/should we require that namespace as part of the condition of getting into core? 2. I don't know where to find code commits for review in a sane way. Looking on the file system is nutty for large packages. I just spent 15 minutes trying to find a changeset by following forks, only to see that the only line added to the CMFCore was plone.packagename in yet another fork of someone else. (Grr) Documentation: 3. Documentation is confusing AGAIN. It is tradition to use README in gihub to provide documentation. Should we be encouraging that with PLIP updates and packages? I personally like it, but then we have yet another place to have documentation. Also, when people have forked or are hosting in their account instead of under plone, holy whoah the docs could disappear. And what about collective? Can we set on a standard for at least one place for all new documentation? (Moar Grr) Reviewing: 4. I personally want to comment line by line in the code and did on this last review. This is SO much easier than putting reports in the text reviews, but then the other code reviewers need to look in the same place. Can we all agree to switch to commenting on commits and lines in github at the source instead of the review.txt file? 5. Filing bugs. If we are in github and the package is forked, it seems like we should file the bug there. Or do we keep it in trac? I don't know what the current philosophy is. Maybe we just listen to the devs? I just want them to 1) get the bug and 2) fix it. Other: 6. Can we make directories in the plips to make autocomplete easier? Maybe having a directory for each plip that then has everything about that plip? My only concern is making sure the cfgs still run. The current directory layout makes my eyes bleed after so many plips. Suggestions: I think at minimum, we need to have the PLIP implementors help us by *clearly* listing *urls* to - All documentation, which should be at a url (should it always be in collective docs? should human docs go there and sphinx docs elsewhere? What about upgrade notes?) - Which bug tracker they want us to use (that or we tell them, but I don't think that will work) - A URL which directs us to all packages that have been changed. On our end, It would be nice to provide a guide that tells the implementors... - all docs of type x go here, all docs of type y go here, all plips require docs of type X &amp; Y - fork/branch code like this - submit for review with the urls above in implementation notes (plipXXX-XXX.txt) This way we don't have a guessing game on both ends and additionally it get's way easier for people to add plips. I'm happy to do the legwork of documenting if I can get some consensus on where to put things and the best way to address these problems. Liz (eleddy) </pre> Elizabeth Leddy 2012-01-18T23:50:01 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3661 <pre>hi fwt, i'd like to submit, small but powerful plip. http://dev.plone.org/ticket/12452 i hope i'm not to late for 4.3 party with this! </pre> Rok Garbas - gmail. com 2012-01-10T04:02:52 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3661 <pre>hi fwt, i'd like to submit, small but powerful plip. http://dev.plone.org/ticket/12452 i hope i'm not to late for 4.3 party with this! </pre> Rok Garbas - gmail. com 2012-01-10T04:02:52 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3658 <pre>I'm sorry, but I won't be able to make it to today's conference call. Hope you have a productive meeting! </pre> Martijn Pieters 2011-12-13T18:27:08 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3657 <pre>Dear FWT members, For reasons that have to do with our current work at Jarn as well as personal reasons I will take a few month long break from the FWT team. I am currently lacking the time to dedicate to the framework work. Apologies for the short notice, I hope to be able to contribute again soon. </pre> Yiorgis Gozadinos 2011-12-06T17:12:31 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3656 <pre>Sorry guys, I won't be able to join you today! </pre> Martijn Pieters 2011-11-22T18:26:19 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3655 <pre>Hopefully, you've received an invite to a call this Tuesday (November 15th). We've got a lot of catching up to do. Eric </pre> Eric Steele 2011-11-13T19:03:17 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3640 <pre>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 </pre> Eric Steele 2011-11-01T17:18:30 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3639 <pre>Reminder, there is no meeting today. You'll likely be getting an email from Calliflower that I've cancelled the series. I'll recreate it after the conf once we're back on a schedule. </pre> Eric Steele 2011-11-01T17:16:32 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3638 <pre>A reminder that we have our conference call tomorrow. Please check up on your PLIPs so that we can quickly run through a status update. Eric </pre> Eric Steele 2011-10-17T13:46:32 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3637 <pre>Hello We add a new PLIP for Plone 4.3 to add an extension mechanism around the personalize info view: https://dev.plone.org/plone/ticket/12238 This PLIP is yet implemented in an addon product: collective.customizablePersonalizeForm. Regards, </pre> Encolpe Degoute 2011-09-27T15:05:29 http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3636 <pre> Alright, the Calliflower mess should be fixed now. We're on for Tuesday the 27th at our usual time. New call info is up at http://bit.ly/o5OSe2, if anyone needs it. Here are the new PLIPs since we last spoke. Please take a look at them so we can discuss. http://dev.plone.org/plone/ticket/12199Display both default item and folder 'new item' menu in the same menu http://dev.plone.org/plone/ticket/12198Ship Chamelon (2.x)/five.pt with Plone 4.3 by default http://dev.plone.org/plone/ticket/12182Extend OpenID support to include Simple Registration http://dev.plone.org/plone/ticket/12110Plain text searches ignore accents http://dev.plone.org/plone/ticket/12224Create a filesystem resource directory by default http://dev.plone.org/plone/ticket/12227In-Plone theme editor Thanks, Eric </pre> Eric Steele 2011-09-23T19:16:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.teams.framework