Re: [PLIP-Advisories] #9327: unified interface for lists of content

#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.

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/9327#comment:59>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #10687: Plone OpenID Federated Login

#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 => 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).
(Continue reading)

Re: [PLIP-Advisories] #9352: Improved search results

#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]:
 > 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.

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/9352#comment:72>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #10687: Plone OpenID Federated Login

#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)

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10687#comment:15>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #10886: plone.app.event - new eventtype for plone

#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.

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10886#comment:31>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #10886: plone.app.event - new eventtype for plone

#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@… (added)

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10886#comment:30>
Plone <http://plone.org>
Plone Enterprise Content Management System
_______________________________________________
PLIP-Advisories mailing list
PLIP-Advisories <at> lists.plone.org
https://lists.plone.org/mailman/listinfo/plip-advisories

Re: [PLIP-Advisories] #10687: Plone OpenID Federated Login

#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
(Continue reading)

Re: [PLIP-Advisories] #10687: Plone OpenID Federated Login

#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.

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10687#comment:13>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #9327: unified interface for lists of content

#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
(Continue reading)

Re: [PLIP-Advisories] #10959: API for password validation policy

#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!

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10959#comment:14>
Plone <http://plone.org>
Plone Enterprise Content Management System

Re: [PLIP-Advisories] #10687: Plone OpenID Federated Login

#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 & 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.''
(Continue reading)


Gmane