Re: [Framework-Team] PLIP #246 ready for review (pending review notes)
On Sat, Jan 17, 2009 at 10:44 PM, Andreas Zeidler a...@zitc.de wrote: On Jan 17, 2009, at 4:37 PM, Andreas Zeidler wrote: as a heads-up, the review bundle for PLIP 246 (View for rendering events as an iCalendar file) is ready for review. you can get it from https://svn.plone.org/svn/plone/review/plip246-ical-feed/ it does not yet contain any review notes (as i need to go afk now), but i'll add them tonight. the review notes are available now in the bundle's top-level `README.txt` file. For documentation purposes: Is there any change in the UI to reflect the new available option? -- israel ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIP 237 ready for review
Hi. I'm somewhat late with creating the review buildout for PLIP 237 (Minor i18n upgrades) at: https://svn.plone.org/svn/plone/review/plip237-minor-i18n-upgrades/ The review notes and detailed explanation is found in the review buildout's README.txt. The PLIP text at http://plone.org/products/plone/roadmap/237 is somewhat outdated and will be updated with the detailed information if I get a go-ahead. Thanks, Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP 197 ready for review: feedparser as external dependency
How come this PLIP has not been reviewed yet? I think we agreed to encourage people to submit PLIPs early so the framework team can start earlier as well in order to reduce the workload? Wichert. Previously Maurits van Rees wrote: The buildout is here: https://svn.plone.org/svn/plone/review/plip197-feedparser Note that I will not be online the next few days, so be patient when you have questions. I'll paste the README.txt below for convenience. PLIP 197: Add FeedParser as external requirement instead of shipping with it See http://plone.org/products/plone/roadmap/197 Basically the only thing that needs doing is: - Remove portlets/feedparser.py from plone.app.portlets. - Instead add FeedParser as requirement in setup.py. This has been done on this branch (see src/plone.app.portlets in this buildout): https://svn.plone.org/svn/plone/plone.app.portlets/branches/plip197-feedparser-as-external-egg One possible gotcha is that the *package* is called ``FeedParser`` and the *module* contained in that package is called ``feedparser``. ``easy_install`` can handle both spellings just fine. But I once encountered problems when using the lowercased name in setup.py. See http://dev.plone.org/plone/ticket/7299 (which is where this plip originated). I could not reproduce that later, but I say we call the dependency ``FeedFeeder`` and everything should work. ``bin/test`` will run the plone.app.portlets tests. Happy New Year! -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ This is your day, don't let them take it away. [Barlow Girl] ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP #247 ready for review (I think)
On Sat, Jan 17, 2009 at 2:37 AM, Ethan Jucovy ethan.juc...@gmail.comwrote: Some of the things that people have said ought to be discussed about PLIP #247 are: 1) impact on server startup time 2) implications for test environments 3) stabilizing and releasing a new version of z3c.autoinclude 4) debugging tools/APIs for z3c.autoinclude * 5) documentation and/or code generation templates to explain the entry point for plugin authors* I'll begin working on #3 immediately, since there's plenty I can do there while discussion is still happening. Please let me know if there's anything else I'll need to submit for the PLIP's review. I'm not a member of the Framework Team so this is not mandatory for the PLIP's review, but as a member of the Documentation Team I would appreciate number (5). Something like Before, we did this to accomplish this task. Now, we can do that., as Wichert (?) suggested, so we would be able to find and update affected docs easily. Thanks in advance! -- israel ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
