http://blog.gmane.org/gmane.comp.web.zope.plone.plip-advisories hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1374 <pre>#10902: New collections (merged plip) ---------------------+------------------------------------------------------ Reporter: elvix | Owner: jaroel Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Unknown | Keywords: ---------------------+------------------------------------------------------ Comment(by jaroel): Looks like we're sprinting on this next friday. That should be enough, but we'll know by then :P </pre> Change notifications for Plone PLIPs on Trac. 2011-04-20T13:37:11 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1373 <pre>#10902: New collections (merged plip) ---------------------+------------------------------------------------------ Reporter: elvix | Owner: jaroel Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Unknown | Keywords: ---------------------+------------------------------------------------------ Comment(by rossp): Great! More importantly, however, what are the rough chances you'll be able to address all the issues by the end of May? </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T21:44:35 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1372 <pre>#10902: New collections (merged plip) ---------------------+------------------------------------------------------ Reporter: elvix | Owner: jaroel Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Unknown | Keywords: ---------------------+------------------------------------------------------ Comment(by jaroel): I haven't gotten around doing anything on this since last update. Just to be clear: I want this one too :) </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T20:31:49 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1371 <pre>#9327: unified interface for lists of content ----------------------------+----------------------------------------------- Reporter: elvix | Owner: elvix Type: PLIP | Status: reopened Priority: n/a | Milestone: 4.2 Component: Infrastructure | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment(by rossp): Poke! Can you briefly reply to the previous comment? Let us know if you can do this and when you think you might be able to do this? We also discussed the possibility of adding test coverage to assure that we don't break backwards compatibility for anyone who's customized any of the templates. </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T19:25:48 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1370 <pre>#10902: New collections (merged plip) ---------------------+------------------------------------------------------ Reporter: elvix | Owner: jaroel Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Unknown | Keywords: ---------------------+------------------------------------------------------ Comment(by rossp): Poke! What the status on this work? </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T19:24:13 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1369 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: 4.2 Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Changes (by eleddy): * milestone: Future =&gt; 4.2 Comment: Replying to [comment:14 cwarner]: Thanks for the update. The FWT would like to see this happen so I'm going to put a 4.2 release marker on it and let's just go for broke on hitting it. In the meanwhile, it sounds like you need some people to throw ideas off of. I am happy to look at some of the front end issues, or just to talk about them. I'm not entirely too familiar with the insides though so I don't feel comfortable talking about implementation. Seeing that davisagli was a seconder I put him on the cc and maybe he can help if needed there :) Happy to keep this as a PLIP, we just want to see it go in a fixed direction and will try to get you what help you need. Based on the previous comments it just seems like there is a direction that needs to be chosen. Let me know what I can do to help here (either on this ticket or email is fine). </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T19:20:01 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1368 <pre>#9352: Improved search results ----------------------------+----------------------------------------------- Reporter: laurenskling | Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Infrastructure | Keywords: search ----------------------------+----------------------------------------------- Comment(by eleddy): Replying to [comment:70 spliter]: &gt; Hi, I am willing to keep working on this one. But can not keep it going for the next month more or less. But the PLIP should be ready by 4.2 I suppose. Just checking in here - I heard that things have been pretty busy for you - would you like me to try and find you some help on this PLIP? We really want to see this make 4.2. </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T19:12:43 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1367 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: Future Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Changes (by eleddy): * cc: davisagli (added) </pre> Change notifications for Plone PLIPs on Trac. 2011-04-19T18:26:35 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1366 <pre>#10886: plone.app.event - new eventtype for plone ----------------------------+----------------------------------------------- Reporter: thet | Owner: thet Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure | Keywords: event, recurring, date ----------------------------+----------------------------------------------- Comment(by thet): thank you vincent! awesome work. i'm looking forward for the buschenschanksprint. </pre> Change notifications for Plone PLIPs on Trac. 2011-04-06T14:04:37 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1365 <pre>#10886: plone.app.event - new eventtype for plone ----------------------------+----------------------------------------------- Reporter: thet | Owner: thet Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure | Keywords: event, recurring, date ----------------------------+----------------------------------------------- Changes (by ctxlken): * cc: ken.wasetis&lt; at &gt;… (added) </pre> Change notifications for Plone PLIPs on Trac. 2011-04-06T13:53:35 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1364 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: Future Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Comment(by cwarner): Sure, so after implementing a prototype of this and applying it into a semi-production scenario it turns out that there are a lot of problems via user interface and interaction issues. Especially in regards to users who are aware of their openid and then trying to use the automatic login. In those cases the generated identifier changes in response but it is actually the same account. So automatic association needs to be done there. I'm in the process of rolling out a more robust prototype at nyu where I hope to get more information and can sure some of those issues up. There are also user management issues that I simply haven't worked out yet. For instance, managing the user becomes problematic as some users are using one openid and simply decide they are changing it on a whim. So instead of Yahoo, they switch to Google. This in and of itself isn't a software issue perse but being able to manage the process or migrating the user and the content they've created is another slightly messy issue. There are also other minor issues in to making sure the discovery endpoint uri is configurable. Walking through and making sure each of the main openid endpoints behaves the same way to the user and more. My time here at NYU will most likely revolve back to this in the next couple of weeks so I'd like to simply leave the ticket open as on-going and at the very least update with relevant doc and source. There is a paper i'm writing with this that simply isn't complete and it's not an easy problem. However nailing down a proper implementation that is usable for all services, including user configurable endpoints will take more time. If the FWT sees it fit this not make Plone at all that is one thing, but I think having a robust and usable solution instead of a confusing mess will be highly beneficial. I'm of the mentality that this need not be a PLIP if it is causing confusion or holding anything up and I can continue my work here and when it's ready it will again be considered for inclusion. It is simply not as easy as originally anticipated. </pre> Change notifications for Plone PLIPs on Trac. 2011-04-05T21:08:07 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1363 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: Future Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Comment(by eleddy): Christopher - the FWT wants to approve and integrate this but we are nervous about what still needs to be done exactly. If you could be more explicit about what still needs to be done, the risks, and the plan of attack on this it would help us a lot. </pre> Change notifications for Plone PLIPs on Trac. 2011-04-05T19:25:06 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1362 <pre>#9327: unified interface for lists of content ----------------------------+----------------------------------------------- Reporter: elvix | Owner: elvix Type: PLIP | Status: reopened Priority: n/a | Milestone: 4.2 Component: Infrastructure | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment(by rossp): After discussing this, the FWT decided that we would like the core Plone templates converted to use this new package. Firstly, the only reason I was concerned about converting the core listing templates was the possibility of breaking commonly customized templates in a minor release. In today's call cah190 pointed out that changing templates in core plone wouldn't necessarily break customized templates. Secondly, and more importantly, if this PLIP includes changing the core Plone templates then it is no longer dependent on one of the other PLIPs that use plone.app.contentlisting being accepted. We really want to merge this PLIP and converting the templates means it won't get hung up on others. Finally, converting the core templates actually accomplishes the primary goal of this PLIP, to reduce the number of way we list content. So please go ahead and convert the following core content listing templates in your PLIP branch: * all the views behind the folder display menu options * all the views behind the collection display menu options * portlets: review list, news, events, collection * folder_contents </pre> Change notifications for Plone PLIPs on Trac. 2011-04-05T19:15:57 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1361 <pre>#10959: API for password validation policy ---------------------+------------------------------------------------------ Reporter: djay | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: 4.2 Component: Unknown | Resolution: Keywords: | ---------------------+------------------------------------------------------ Comment(by eleddy): FWT approved for 4.2 with a couple notes: - Tests must be included - 1 external review must be from the security team - matthewwilkes will be your framework team contact for this Please note the new process needs two external reviews. When you are ready for the FWT to do an integration review please update status to "please review" Thanks! </pre> Change notifications for Plone PLIPs on Trac. 2011-04-05T18:51:55 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1360 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: Future Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Comment(by cwarner): Reopened ticket, progress continues there are no new plans sans the last email sent on the topic: ''This initial implementation was always going to be a stop-gap measure but a couple of new things have come to light here which are changing this PLIP's functionality. The openid whitelisting patch, a UI review and some other things. Even though the minor implementation could technically make Plone 4.1 I am not sure now if it should. After thinking about the problem a little bit more it became obvious that even though I consider the direction to be the right one. There may need to be a bigger overall push here in regards to actually solving the Nascar Problem as pointed out in the ticket and at Google's Faculty Summit. How I believe we go about doing this needs to be implemented, written up and presented to the Plone &amp; Openid communities for review. That aside, I'd really like to wrap up the whitelisting functionality that Kai Lautaportti has been working on at the very least as it's integral to the functionality of the whole Single-Sign on Federated process which increases the functionality of the ticket but clearly for good purpose.'' </pre> Change notifications for Plone PLIPs on Trac. 2011-03-31T15:27:03 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1359 <pre>#10687: Plone OpenID Federated Login ----------------------------+----------------------------------------------- Reporter: cwarner | Owner: Type: PLIP | Status: reopened Priority: minor | Milestone: Future Component: OpenID support | Resolution: Keywords: openid login | ----------------------------+----------------------------------------------- Changes (by cwarner): * status: closed =&gt; reopened * resolution: wontfix =&gt; </pre> Change notifications for Plone PLIPs on Trac. 2011-03-31T15:24:35 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1358 <pre>#10886: plone.app.event - new eventtype for plone ----------------------------+----------------------------------------------- Reporter: thet | Owner: thet Type: PLIP | Status: new Priority: minor | Milestone: 4.2 Component: Infrastructure | Keywords: event, recurring, date ----------------------------+----------------------------------------------- Comment(by vincentfretin): Hi, I sold the recurrence functionality to a customer, so I quickly needed something functional. I continued the plone.formwidget.reccurence widget, it serializes and deserializes the rfc string perfectly now, but it's not internationalized and there is no automated tests on it. The widget will be normally reimplemented by Rok for the next sprint (http://www.coactivate.org/projects/buschenschanksprint-2011/project-home) The plone calendar portlet is not functional with recurring events. Instead of using the portlet I use Solgema.fullcalendar which now supports recurring events from plone.event. This works really well. There are issues with the timezone field on the event content type, it is handled after the start and end dates, so it always default to the portal timezone. So for now, I only enable one timezone for the portal to not have weird issues. I will put a Plone 4.1b1 + plone.app.event site on production the next week with the current work status. </pre> Change notifications for Plone PLIPs on Trac. 2011-03-28T08:37:02 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1357 <pre>#9327: unified interface for lists of content ----------------------------+----------------------------------------------- Reporter: elvix | Owner: elvix Type: PLIP | Status: reopened Priority: n/a | Milestone: 4.2 Component: Infrastructure | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment(by eleddy): + 1 on converting some templates and a plan. That was a major sticky point in discussions. </pre> Change notifications for Plone PLIPs on Trac. 2011-03-23T16:54:44 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1356 <pre>#9352: Improved search results ----------------------------+----------------------------------------------- Reporter: laurenskling | Owner: spliter Type: PLIP | Status: assigned Priority: major | Milestone: 4.2 Component: Infrastructure | Keywords: search ----------------------------+----------------------------------------------- Comment(by rossp): As I recall the biggest remaining issues were the lack of history for AJAX searches and the loss of search context on some operations. Can you add some detail of how you plan to address those issues? </pre> Change notifications for Plone PLIPs on Trac. 2011-03-23T16:40:57 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1355 <pre>#9327: unified interface for lists of content ----------------------------+----------------------------------------------- Reporter: elvix | Owner: elvix Type: PLIP | Status: reopened Priority: n/a | Milestone: 4.2 Component: Infrastructure | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment(by rossp): It's my memory that this one was ready to go for merge and only didn't get merged because nothing that depended on it got merged and we didn't want to add a core dependency that was unused in core. So from my recollection, this should be merged as long as one or both of those PLIPs that depend on it are merged. That said, I think it would be a great plus to convert some of the core templates to use it. </pre> Change notifications for Plone PLIPs on Trac. 2011-03-23T16:35:20 http://permalink.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1354 <pre>#9327: unified interface for lists of content ----------------------------+----------------------------------------------- Reporter: elvix | Owner: elvix Type: PLIP | Status: reopened Priority: n/a | Milestone: 4.2 Component: Infrastructure | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment(by davisagli): Replying to [comment:54 elvix]: &gt; Yes. I am. &gt; &gt; It would be good, however, to get a clear idea of what the FWT wants to see in place for it to be included. &gt; &gt; Should we convert all templates to use it, some templates, all portlets, etc? — or is it enough to have the search depend on it? Speaking personally, I would like to at least see a roadmap for how we switch all these things over -- ideally including some work on prototypes. It's probably fine if we don't switch everything for 4.2 as long as we have a plan. </pre> Change notifications for Plone PLIPs on Trac. 2011-03-23T15:45:30 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.plip-advisories