Re: [Framework-Team] Fwd: Volunteer to join Framework Team
Yes. Please invite me as well, I should probably be there as release manager. :-) Maurits On 29/10/2021 16:19, Alessandro Pisa wrote: Is anybody ok having a meeting the next week on Tuesday? -- Maurits van Rees https://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] RFC: Drop Plone 5.2 support in plone.api
For clarity, it is not "Drop Plone 5.2 support", but drop support for versions earlier than 5.2. Maurits On 28/02/2021 10:24, Alessandro Pisa wrote: Hi everybody, people are requesting an evaluation of: - https://github.com/plone/plone.api/issues/450 It would be great if we could provide a team answer. Ciao! -- Maurits van Rees https://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Resignation
Absolutely. Thanks Gil and Jens. And thank you to all current framework team members! We don't say that often enough. Maurits On 06/11/2019 10:21, Timo Stollenwerk wrote: Thank you, Gil and Jens, for your service at the FWT! Your tireless work for the community (past, present, future) is highly appreciated! Cheers, Timo On Wed, Nov 6, 2019 at 9:48 AM Jens W. Klein <mailto:j...@bluedynamics.com>> wrote: Hi Gil and all! thanks Gil for your great work here! I welcome our new members Rodrigo and Maik! Since I am now a Board member - and as you may know from my board nomination - I will also quit the framework team. It would be just to many tasks for me. My opinion is, more than two community tasks are enough. I am also on the security team and there is currently also work to be done by reviewing possible security issues. As we are now having more than one project in the foundation to cover it will be one of my priorities to get them wired in our processes. The framework team, its responsibilities and organisation are probably also part of this. So stay tuned - but it will take a while. I'll also try to keep up merging and closing PRs - but please please help with this task since my focus will shift to the Board work. So, spread the word to other coredevs to help closing outdated PRs and issues. If everyone would take one issue or PR a week we would already do significant better and nobody has the full load on its shoulders. Ciao! Jens On 05.11.19 22:37, Gil Forcada Codinachs wrote: > Hi all, > > I've been thinking about that for months and months, and now, given that > there are quite a few new members, it is time for me to say goodbye. > > I hope the un-subscription works :) > > Cheers, > Gil > -- Klein & Partner KG, member of BlueDynamics Alliance ___ Framework-Team mailing list framework-t...@lists.plone.org <mailto:framework-t...@lists.plone.org> https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team -- Maurits van Rees https://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Missing tags on github
I fixed the CHANGES.rst on CMFPlone master, copying it from the PyPI release, and removed the relevant entries from the news directory: https://github.com/plone/Products.CMFPlone/commit/03ae8ce3d3e91b515f3cca8233b75c7137c157fd I also updated the setup.py version to 5.2b1.dev0, as we want the next version to be a beta: https://github.com/plone/Products.CMFPlone/commit/8809b6807da52a67661b4c1c3a2e6dbb206dc7a2 Same for the Plone package. Can be reverted of course if we deem a third alpha necessary anyway. Maurits Op 06-02-19 om 10:15 schreef Gil Forcada Codinachs: You are right, for CMFPlone, Eric might have forgotten to do a git push --tags. Missatge de Alessandro Pisa <mailto:alessandro.p...@gmail.com>> del dia dt., 5 de febr. 2019 a les 21:11: I see we are missing some tags in github https://github.com/plone/Products.CMFPlone I expected to see 5.2a2 and 5.2a3 (which is currently pending). Am I wrong? Ciao! -- @ale_pisa - http://ale-rt.github.io - http://alepisa.blogspot.com - https://it.linkedin.com/in/apisa ___ Framework-Team mailing list framework-t...@lists.plone.org <mailto:framework-t...@lists.plone.org> https://lists.plone.org/mailman/listinfo/plone-framework-team -- Maurits van Rees: http://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] pytz versions in Plone 5.0.2
Unfortunately we can't. Well, not without fixing tests in various packages, and possibly code outside the tests as well. IIRC there is an abandoned pull request or branch on coredev for this. Maurits van Rees http://maurits.vanrees.org > Op 12 jan. 2016 om 16:41 heeft Johannes Raggam <thete...@gmail.com> het > volgende geschreven: > > We can safely update or even remove the version specifier. > > >> On 01/12/2016 04:02 PM, Jens W. Klein wrote: >> Did I miss the reason why we use an outdated pytz, older than in >> underlying Zope 2.13.23? >> >> pytz >> 2013b... http://dist.plone.org/release/5.0-latest/versions.cfg >> 2015.4.. http://dist.plone.org/versions/zope-2-13-23-versions.cfg >> 2013b...http://dist.plone.org/versions/zopetoolkit-1-0-8-ztk-versions.cfg >> >> Jens > ___ > Framework-Team mailing list > framework-t...@lists.plone.org > https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Stepping down
As Paul Roeland said at the Dutch Plone User Day yesterday, Plone is in its fifteenth year, proving that it is sustainable software, and we can and should work on it in a sustainable way, with a healthy life-work balance. See http://maurits.vanrees.org/weblog/archive/2015/11/paul-roeland-meer-dan-software-de-weg-naar-plone-5 <http://maurits.vanrees.org/weblog/archive/2015/11/paul-roeland-meer-dan-software-de-weg-naar-plone-5> (Dutch only) Maurits van Rees http://maurits.vanrees.org > On 11 Nov 2015, at 00:44, David Glick (Plone) <david.gl...@plone.org> wrote: > > Open source work has a way of taking more of us than we originally intended > to give, and it's so important to recognize when that happens and correct it. > > Jesse Noller had a good blog post on this topic recently: > http://jessenoller.com/blog/2015/10/31/community-boundaries > <http://jessenoller.com/blog/2015/10/31/community-boundaries> > > And I also think of Marius Gedminas' recent tweet, " At least I no longer do > stuff because I think I should, or because stuff need to be done - when I do > FOSS, I do it because it's fun." > > All the best to you Roel, and the rest of you...hope to see many of you in > Boston, or maybe sooner. > David > > On 11/10/15 3:36 PM, Roel Bruggink wrote: >> Hi all, >> >> Okay, that "change of interest" sounded a bit more dramatic than intended :) >> >> I found myself in a position where work-private life was out of balance and >> no longer sustainable for me. >> >> There were two triggers for this conclusion. One was, of course, Rob leaving >> Four Digits and the process in "reinventing" our company. The other was a >> remark by Timo during the Anniversary Sprint where we talked a bit about why >> he stopped playing drums, which boiled down to "that's how things go". It >> made me think if I was ready to give up on that just now - I'm not. >> >> Playing drums and making music has been a huge part of my life for a long >> time, but didn't get the attention it needed. I'm not trying to become a >> rockstar -as Ramon suggested-, though I do need to find myself a band and >> create music again. >> >> In all, thank you for an awesome and educational time in the FWT. Hopefully >> see you guys soon! >> >> -Roel >> >> On 10 November 2015 at 22:16, Johannes Raggam <thete...@gmail.com >> <mailto:thete...@gmail.com>> wrote: >> tnx man! and hope to see you around some time. >> >> cheers, >> johannes >> >> On 11/10/2015 05:23 PM, Roel Bruggink wrote: >> Hi all, >> >> I'm stepping down from the FWT effective immediately due to change of >> interest. >> If you need any kind of input, please don't hesitate to ask! >> >> So long, and thanks for all the fish! >> >> -- >> Roel Bruggink >> https://www.fourdigits.nl/over-ons#roel-bruggink >> <https://www.fourdigits.nl/over-ons#roel-bruggink> >> <https://www.fourdigits.nl/over-ons#roel-bruggink >> <https://www.fourdigits.nl/over-ons#roel-bruggink>> >> >> Four Digits BV >> https://www.fourdigits.nl <https://www.fourdigits.nl/> < >> <https://www.fourdigits.nl/>https://www.fourdigits.nl/ >> <https://www.fourdigits.nl/>> tel: +31 26 4422700 >> >> >> ___ >> Framework-Team mailing list >> framework-t...@lists.plone.org <mailto:framework-t...@lists.plone.org> >> https://lists.plone.org/mailman/listinfo/plone-framework-team >> <https://lists.plone.org/mailman/listinfo/plone-framework-team> >> >> >> >> >> -- >> Roel Bruggink >> https://www.fourdigits.nl/over-ons#roel-bruggink >> <https://www.fourdigits.nl/over-ons#roel-bruggink> >> >> Four Digits BV >> https://www.fourdigits.nl <https://www.fourdigits.nl/> tel: +31 26 4422700 >> >> >> ___ >> Framework-Team mailing list >> framework-t...@lists.plone.org <mailto:framework-t...@lists.plone.org> >> https://lists.plone.org/mailman/listinfo/plone-framework-team >> <https://lists.plone.org/mailman/listinfo/plone-framework-team> > > ___ > Framework-Team mailing list > framework-t...@lists.plone.org > https://lists.plone.org/mailman/listinfo/plone-framework-team ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] Stepping down
Thanks, Roel. Greetings from the Dutch Plone user day. We missed you! Maurits Op 10/11/15 om 17:23 schreef Roel Bruggink: Hi all, I'm stepping down from the FWT effective immediately due to change of interest. If you need any kind of input, please don't hesitate to ask! So long, and thanks for all the fish! -- Roel Bruggink https://www.fourdigits.nl/over-ons#roel-bruggink <https://www.fourdigits.nl/over-ons#roel-bruggink> Four Digits BV https://www.fourdigits.nl <https://www.fourdigits.nl/> tel: +31 26 4422700 ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team -- Maurits van Rees: http://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] pypi ticket for adding Plone 5.0 to trove tags
Giacomo Spettoli schreef op 15-04-14 15:32: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 12:50 PM, Johannes Raggam wrote: I just opened a ticket on the pypi issue tracker to add Framework :: Plone :: 5.0 to the trove tags. https://sourceforge.net/p/pypi/support-requests/366/ Looks like, Plone is the only project, which has version-specific trove tags. https://pypi.python.org/pypi?%3Aaction=list_classifiers Should we give up these version specific tags? IMHO no one would really trust the classifiers list for knowing the plugin's compatibility. I normally take a look at the README (when I'm lucky) and to the code (when I'm not lucky). When I am working on a package in the collective and wonder what it is supposed to be compatible with, I do look at the classifiers, so that I know with which Plone versions I should be testing any changes that I make. I like that. Of course they can be out of date, just like a remark in the readme can be out of date. -- Maurits van Rees: http://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] New releases in the Plone 3.3 series
Op 13-10-10 00:43, Wouter Vanden Hove schreef: Maurits van Rees wrote: At least I know Products.Archetypes could use a new release (which would become 1.5.17). I e-mailed Daniel Nouri earlier today about that, but if someone else wants to do the honours that is fine as well of course. Note that for Products.Archetypes I heard from Daniel Nouri that he is not really active as archetypes release manager anymore. Recent releases have been made by Eric, Hanno, Andi and Wichert. Perhaps one of you can do a release of the 1.5 branch? Maurits van Rees ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] New releases in the Plone 3.3 series
Op 07-10-10 16:59, Wouter Vanden Hove schreef: Eric Steele wrote: FWIW, we're two packages (plus CMFPlone) away from having a 3.3.6 release ready. We don't have a dedicated milestone for Plone 3.3.6 in Trac with a list of bugs we like to see solved for this specific release. So what is the criterium to say we're two packages away from a release? What are those two packages? At least I know Products.Archetypes could use a new release (which would become 1.5.17). I e-mailed Daniel Nouri earlier today about that, but if someone else wants to do the honours that is fine as well of course. Cheers, Maurits ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP #11021 - Simple theming customizations through the plone interface
Op 31-08-10 05:41, Rob Porter schreef: Hello framework team, I'd like to officially submit the following PLIP for consideration for Plone 4.1:https://dev.plone.org/plone/ticket/11021 https://dev.plone.org/plone/ticket/10878 The html link points to a different plip than the text. So here is a plain text link for good measure: https://dev.plone.org/plone/ticket/11021 Maurits ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP #10778 (UUIDs) - ready for initial review
Op 29-08-10 07:24, Martin Aspeli schreef: plone.uuid provides a simple API for generating and accessing UUIDs. If we use this to create uuids for non-content items, that cannot be traversed to, would that give any problems? For example, it might be nice to use this to create the secrets that the password reset tool sends out, or secrets used in a newsletter product. I had a few ideas some months back that may or may not ever get implemented. ;-) I'd guess that, as long as such a non-content item with a uuid does not end up in the portal_catalog, there is no way to accidentally try to traverse to such non-content. Maurits van Rees ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Plone 4.1 Framework Team Meeting Minutes - Aug. 24, 2010
Op 24-08-10 21:57, David Glick schreef: - Scheduling - Final PLIP submission deadline is next Friday, Aug. 30 Is that Friday 27 or Monday 30? Maurits van Rees ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
Op 20-05-10 22:00, David Glick schreef:
On 5/20/10 12:58 PM, Eric Steele wrote:
The main issues I'd like to see fixed and released before we move to RC are:
#10124 - should remove Large Plone Folder type and expose the folder
ordering setting in the schema
I have started working on this one.
#10360 - Incomplete migration: site_properties and portal_controlpanel
#10363 - Can not edit personal information when one is loged in with email
address
I fixed this one. Feel free to assign any remaining emaillogin related
tickets to me.
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
--
Maurits van Rees
Programmer, Zest Software
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Version support policy: revisions to page (with no change to policy)
On Wed, Jan 13, 2010 at 02:31:25PM +, Graham Perrin wrote: Casting a fresh eye over some areas of plone.org after a few months' focus elsewhere, the support policy wasn't immediately clear. (I'm familiar with the intention of the policy, but when I read it on screen, something seemed not quite right.) I have taken the liberty of editing http://plone.org/support/version-support-policy 4.x will be major. makes me think: 4.0, 4.1, 4.2 etc are major versions. And then the text says 4.1 and 4.2 will be minor. which makes me confused. I would say: Plone 4 will be a major release. BTW, I have no access to the previous version of this document. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ What are you going to create today? ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Plip 9214 (email logins) has been merged
Hi all, I am happy to announce that plip 9214, email logins, has been merged. Cheers, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] PLIP 9214, emaillogins, ready for final review
PLIP 9214, to enable logging in with your email address, is ready for final review. Cheers, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: PLIP load test reports available
On Sun, Sep 06, 2009 at 05:52:52PM +0800, Martin Aspeli wrote: This is really good stuff! I must admit, I don't understand the graphs or the tables-of-graphs at all, though. Is there a quick explanation somewhere about how to read them? The reference bench results are for Plone4 without plips. The challenger bench results are for one of the plips. If the graph is mostly green, the plip has better performance. If the graph is mostly red, the plip has worse performance. For each plip three tests have been done, showing performance for: - content creation - read only - heavy writes I don't know what is being tested exactly. On the front page of the tests at http://weblion.psu.edu/static/loadtesting/plone4.0/plips.html you have per plip the following items: - label/name of the plip - for each of the three tests: - main graph, with link to detailed report of the plip - main difference graph between plip and plain plone, with link to detailed difference report Take the diffence page for plip 9310 showing heavy writes: http://bit.ly/vN9kJ The first graph has the requests per second. The blue line shows the results for B1 (bench 1, plain plain 4.0) The purple line shows the results for B2 (bench 2, plip 9310) The first part shows the difference between those lines as red, meaning that the plip is slightly slower; this part of the graph is for 1-3 concurrent users. To the right we have a green difference, meaning that the plip is faster, even up to 80% for 10 concurrent users. If results look too absurd, probably something went wrong in the tests. For example plip 8814, replacing secure mail host, looks totally red. Apparently with that plip we serve a whopping zero pages per second. :-) I hope that clears things up a bit. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIPs in Trac
On Thu, Jun 18, 2009 at 11:48:24PM +0100, Matthew Wilkes wrote: Hi all, I'd like to open a public discussion on where tracs should be. As some of you may know, I'm very much against the PLIPs-in-trac system that has been implemented following out-of-band discussions last year. I think we need to make a proper decision, I'm not sure how that will happen, but if it'll stop me whinging either way. For Plone 4.0 we've put PLIPs on plone.org, this has the following advatanges: - Unique, relatively low number for each PLIP - Custom content type enforces PLIP structure - Workflow matches our process I do not really mind either way. But I talked with Jean-Paul Ladage about this today and he is right in saying that end users wanting to know the future of Plone will look at the roadmap on plone.org and they will not be impressed: http://plone.org/products/plone/roadmap They will see a bunch of plips for 3.3, one for trunk, and then about 40 'Proposals being discussed'. Since some are apparently being discussed since 2005 these 40 proposals might as well be ignored as there is no guarantee or indication about when they might get included. This is not the sign of the healthy, active project that Plone still is. The disadvantage of it being on a different site has been raised, but I don't buy this. How often do you want to look at the bugs and PLIPs for a release at the same time? They have a completely different process. The current crop of PLIPs for 4.0 are very unstructured, only the ones copied verbatim from plone.org have seconders. We're having to bodge workflow by assigning different milestones. It's really suboptimal. Do others agree with me, or do you prefer trac? Despairingly yours, Matt ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Version Support Confusion
On Tue, Apr 21, 2009 at 02:07:58PM -0700, Steve McMahon wrote: Active maintenance of Plone happens for one major version of Plone at a time. Once a new major version is released, the old major version is maintained until the first minor version of the new major version is released. To me, the second sentence contradicts the first one: we maintain one major version at a time, except when we maintain two... :-) How about this: Active maintenance of Plone happens for one major version of Plone at a time. The exception is that once a new major version is released, the old major version is maintained until the first minor version of the new major version is released. Or: Active maintenance of Plone happens for one major version of Plone at a time. When a new major verson of Plone is released, this new version will be the actively maintained version. However, there is a period of overlap: until the first minor version of the new major version is released, the old major version is also maintained. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] PLIP process in Trac for Plone 4 onwards
On Thu, Apr 02, 2009 at 03:49:32PM +0200, Alexander Limi wrote: Hi all, Just wanted to summarize how I think we'll using Trac for the PLIPs for Plone 4 onwards: - PLIPs are added as tickets with the PLIP type. - PLIPs show up in http://dev.plone.org/plone/report/24 - If you propose for a particular release, you assign it to that release's milestone. - Idea PLIPs are put in the Future milestone. - That the ticket is accepted reflects FWT vote I think accepted could mean two different things here: 1. The plip idea is accepted as a candidate for Plone x; no code has been written yet. 2. The plip has been implemented and this implementation is accepted and is ready for merge. Do we need a separate state for one of those? I guess if a plip idea is not accepted it wil immediately be put in the rejected state, or perhaps if the idea is fine but not for the upcoming plone version, then the milestone will be changed. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ Yes, we study economics, got to make the money make some kind of sense. - Geoff Mann ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Plone 3.3 PLIP merges
Andrew Burkhalter, on 2009-02-27: PLIP 126 is now merged and the review bundle archived. I've tried to be as comprehensive as possible here, but I hope any mistakes I've made will be pointed out. Tasks that I believe need to be done from here are: - Need new release of plone.app.controlpanel (looks like wichert, hannosch, or optilude need to do this) - Need new release of plone.app.portlets (looks like this is either wichert or optilude) A new release of plone.app.portlets is also needed for plip 197 that I just merged. - Possibly changes to versions.cfg and etc/versions with plonenext/branches/3.3, I didn't take the time to figure out what was needed. It looks like nothing is needed here at this point. - Relevant merging to trunk I'd say you can do this now. Am I on the right track here? Looks like it to me, but plip 197 is the first plip I did, so I'm no expert. :) Thanks! Andrew And thank you for creating a new plone.app.portlets branch so I did not need to do that for my plip. :) Cheers, -- 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
[Framework-Team] Re: PLIP 197 ready for review: feedparser as external dependency
Martijn Pieters, on 2009-01-20: On Wed, Dec 31, 2008 at 17:19, Maurits van Rees I could not reproduce that later, but I say we call the dependency ``FeedFeeder`` and everything should work. I take it you meant 'FeedParser' in that last sentence ;-) D'oh! You are right. Products.feedfeeder (which is actually all lowercase except for the 'Products' part) is an add-on product where I first added the FeedParser requirement in setup.py. This is not the first time I mixed up the names and it probably won't be the last. ;-) -- 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
[Framework-Team] Re: PLIP #197: Add FeedParser as external requirement
Martijn Pieters, on 2008-10-03: On Fri, Oct 3, 2008 at 23:59, Maurits van Rees [EMAIL PROTECTED] wrote: The plip is: #197: Add FeedParser as external requirement instead of shipping with it http://plone.org/products/plone/roadmap/197 Originally proposed by Christian Scholz in December 2007. Seconded bij Martijn Pieters. I did not; Jens Klein seconded it, I gave my framework team vote on it already (a +1). Ah yes, that was what I meant. :) -- 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
[Framework-Team] Plip 197 in 3.2? FeedParser
Hi, Since Plone 3.2 will mostly be about packaging and installers, shall we add Plip 197 as well? See http://plone.org/products/plone/roadmap/197 with title: Add FeedParser as external requirement instead of shipping with it Explanation: plone.app.portlets.portlets currently has feedparser.py in it. That is now available as proper package via the cheese shop. So remove the file from plone.app.portlets and add FeedParser in the setup.py. This issue by Wichert proposes the same: https://dev.plone.org/plone/ticket/7299 I added some comments there last week. The Unified Installer actually already has FeedParser in buildout.cfg: https://dev.plone.org/plone/changeset/18436 https://dev.plone.org/plone/changeset/18907 Questions are: - Does this need a maintenance branch for the current code that still contains feedparser.py? - In case someone messes up the install, do we want to fail graciously when FeedParser is not available? Or do we want Zope to crash and burn? Failing graciously sounds... gracious, but it looks less than trivial to hide e.g. the 'Add RSS portlet' option conditionally. I could make the changes in plone.app.portlets. If any installers or recipes would need to be changed for this, I could try, but I would need assistence/pointers. The only danger is that I keep writing 'feedfeeder' when I mean 'feedparser'... :-) See http://plone.org/products/feedfeeder where I actually made the same change last week. -- 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
[Framework-Team] Re: buildout error for plip215
Tom Lazar, on 2008-02-15: hi ree, thanks for the quick reply! it turns out, that my ~/.buildout/default.cfg was the culprit, where i had activated the new ppix index on advice from reinout[1]: index = http://download.zope.org/ppix after removing that the buildout works fine, sorry for the confusion. i'm reclaiming the ticket and will continue with my review. thanks, tom [1] http://vanrees.org/weblog/archive/2008/01/09/ppix-instead-of-pypi-from-now-on It works fine with that index when I try it. The last item in the index page for this package does look strange though: http://download.zope.org/ppix/infrae.subversion/ pa href=https://svn.infrae.com/buildout/infrae.subversion/trunk#egg=infrae.subversion-dev`_.https://svn.infrae.com/buildout/infrae.subversion/trunk#egg=infrae.subversion-dev`_./a/p I wonder if that somehow borks things, at least for some people. -- 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
