[Framework-Team] Re: PLIP lifecycle

Alexander Limi limi at plone.org
Sat Dec 27 22:28:36 UTC 2008


On Sat, 27 Dec 2008 09:56:23 -0800, Ross Patterson  
<me at rpatterson.net> wrote:

> One way to keep these cross-checks lightweight might be to start with a
> statement of impact.  There are code changes, for example, that have no
> UI impact.  In such cases, it would be fast and more painless if a PLIP
> champion noted this.  Someone from the UI team could then corroborate
> that the PLIP entails no UI impact and that would be the end of it.  If
> there is an impact, then the PLIP champion would need to include full UI
> consideration for the impact in the PLIP.  The UI team could then review
> both the statement of impact for accuracy and the UI consideration for
> sufficiency and completeness.  The same would largely be true for the
> doc team with the exception that, IMO, all changes have a documentation
> impact even if it's only for developers and so there should be no option
> to declare no impact.

This sounds like a good starting point. +1.

-- 
Alexander Limi · http://limi.net





More information about the Framework-Team mailing list