[Framework-Team] RE: [Plone-developers] finishing up the sprint work
Hello, During the sprint, I did work on https://dev.plone.org/plone/ticket/6201 and https://dev.plone.org/plone/ticket/6349 I explained all the things I did in the tickets. Created branches are: https://svn.plone.org/svn/plone/plone.app.kss/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/plone/plone.locking/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/archetypes/Archetypes/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/plone/CMFPlone/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/plone/plone.app.layout/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/archetypes/archetypes.kss/branches/jfroche-6201-locking-improvements/ https://svn.plone.org/svn/plone/plone.app.contentmenu/branches/jfroche-6201-locking-improvements/ I did the bundles in https://svn.plone.org/svn/plone/bundles/branches/3.0-jfroche-6201-locking-improvements/ https://svn.plone.org/svn/plone/bundles/branches/3.0-lib-jfroche-6201-locking-improvements/ Do not hesitate if you need more infos ! Regards, Jeff Wichert Akkerman a écrit : > Now that the Sorrento sprint is need to wrap up all the work done there. > If you worked on modification in a branch or elsewhere and you think it > is ready for merging please mail a pointer to the branch to the > framework-team list along with a description of the changes and why they > are needed. > > Wichert. > ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
Florian Schulze wrote: > What does Zope commit access and z3c.widget have to do with > ÜberSelectionWidget? There is a small bit of code in there which I want to use. http://svn.zope.org/z3c.widget/trunk/src/z3c/widget/namespace/README.txt?rev=71292&view=markup ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: NuPlone and Plone 3.0
On 4/4/07, Wichert Akkerman <[EMAIL PROTECTED]> wrote: > - Decide based on how ready it seems to be whether it should be the > default in the RCs. It certainly won't become the default anymore. We're in full bugfixing-only mode now and a change like that is too big. I think given current timelines, the size of the collector and the state of NuPlone last time I looked at it, that's a wise decision. For example, I was fixing portlet visual bugs. The portlets management page had (is?) not yet been styled as part of NuPlone and I never gave it much testing. My point is, at the moment, during the time when we need to be closing down bugs, people are not testing with NuPlone, which means that if we suddenly switch, we may get a swathe of new visual bugs that would introduce a lot of risk. I don't think we can make a switch of the default look-and-feel without at least one beta to follow it, and the usual time delay between betas/rcs would still apply. Given how integral the look-and-feel is to Plone's user experience, I think it's important not to rush into it. Having to start most issue resolutions with "as a workaround, switch back to the old default Plone skin..." would leave a bad taste in users' mouth and would probably make people hostile to NuPlone in particular if not Plone in general. At the same time, I think it's very important that the great work that's been done with NuPlone gets exposure and momentum. NuPlone is in the bundle now, and is part of what we've shipped in beta. It has bugs, the bugs should be fixed. NuPlone is an important testament to how we should encourage people to do skinning, proof that we can make Plone look different, and hopefully (probably) a part of our future default look-and-feel. So, fix it, ship it, make it easy to install, make it clear we believe in it and will probably make it the default, but don't do so right now for 3.0. All IMHO. Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: The big 3.0 ;)
On 4. apr. 2007, at 09.09, Alexander Limi wrote: 3.0.x minor are for bug and security fixes, not feature changes. So in 9 months, we can add comments without reloading the page, It is worth noting, though, that one theory to why there is a long span between releases is that people keep putting new stuff into the release last-minute instead of just starting a branch and completing the feature regardless of when in the cycle we are. I have noted there is some interest in a new discussion about the release process (like: 'when did we decide to not follow the official time-based releases we decided on after-all? - and is the current way the better way?'). I have met all such requests with "let's first get 3.0 done, so we don't interfere and mix discussions of particular features and development with the discussion of the process itself. Anyway, in my opinion, we should schedule this discussion for soon after the release of 3.0. :) -- __ Geir Bækholt · Plone Solutions · http://plonesolutions.com __ Plone Foundation · http://plone.org/foundation · Protecting Plone ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
On Tue, 03 Apr 2007 21:59:05 +0200, Jeroen Vloothuis <[EMAIL PROTECTED]> wrote: Wichert Akkerman wrote: - Get a basic UI on ÜberSelectionWidget It has a basic UI, just no ajax interface. Nobody appears to be doing that either, so we're going to have to postpone that until 3.5. I was looking into this. Then I ran into a problem with z3c.widget because it was not a proper name space package. I offered to change it and received positive feedback. Today I got Zope commit access so I can start working on this. This week is filled with PyWeek. Therefore it will take some more time before this is finished (definitely not for 3.0). What does Zope commit access and z3c.widget have to do with ÜberSelectionWidget? Regards, Florian Schulze ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: NuPlone and Plone 3.0
Previously Alexander Limi wrote: > On Tue, 03 Apr 2007 03:30:52 -0700, Wichert Akkerman > <[EMAIL PROTECTED]> wrote: > > >I'm wearing my release manager hat today and was looking at NuPlone. At > >the moment there are still a lot things that do not work or look bad in > >NuPlone (IE support, form styling and control panel styling are easy to > >find examples). That means that it is currently not in a state where I > >want it to even ship with Plone 3. > > The plan is still the same as outlined earlier: Whose plan is that? The release plan for all of Plone, which includes NuPlone at this moment is to be 'feature complete' when we go beta. I was lenient for NuPlone since it was showing promise and was actively developed, but that seems to have stopped the moment it was added to the bundle. > - Get NuPlone "feature complete" by beta2 > > - Work on IE6/7 issues towards the RCs > > - Decide based on how ready it seems to be whether it should be the > default in the RCs. It certainly won't become the default anymore. We're in full bugfixing-only mode now and a change like that is too big. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It 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
[Framework-Team] Re: NuPlone and Plone 3.0
On Wed, 04 Apr 2007 09:12:43 +0200, Alexander Limi <[EMAIL PROTECTED]> wrote: - Work on IE6/7 issues towards the RCs Too late IMO, spliter offered to help here, but I guess he would like to know the chances on NuPlone to be included before he invests energy in this. So it needs to be feature complete first. Regards, Florian Schulze ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: The big 3.0 ;)
Previously Alexander Limi wrote: > On Tue, 03 Apr 2007 03:45:56 -0700, Wichert Akkerman > >3.0.x minor are for bug and security fixes, not feature changes. > > So in 9 months, we can add comments without reloading the page, great... Correct. That is the only way to do release and be able to promise a stable platform for people building on top of Plone. Stability is more important than introducing new features. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It 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
[Framework-Team] Re: The big 3.0 ;)
On Wed, 04 Apr 2007 09:09:27 +0200, Alexander Limi <[EMAIL PROTECTED]> wrote: 3.0.x minor are for bug and security fixes, not feature changes. So in 9 months, we can add comments without reloading the page, great... I understand this frustration, but agree that minor releases shouldn't have new features. *But*, I think we should really consider 3.1.x. The question is how we manage this. Regards, Florian Schulze ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
Wichert Akkerman wrote: >> - Get a basic UI on ÜberSelectionWidget > > It has a basic UI, just no ajax interface. Nobody appears to be doing > that either, so we're going to have to postpone that until 3.5. I was looking into this. Then I ran into a problem with z3c.widget because it was not a proper name space package. I offered to change it and received positive feedback. Today I got Zope commit access so I can start working on this. This week is filled with PyWeek. Therefore it will take some more time before this is finished (definitely not for 3.0). -- Jeroen ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: NuPlone and Plone 3.0
On Tue, 03 Apr 2007 03:30:52 -0700, Wichert Akkerman <[EMAIL PROTECTED]> wrote: I'm wearing my release manager hat today and was looking at NuPlone. At the moment there are still a lot things that do not work or look bad in NuPlone (IE support, form styling and control panel styling are easy to find examples). That means that it is currently not in a state where I want it to even ship with Plone 3. The plan is still the same as outlined earlier: - Get NuPlone "feature complete" by beta2 - Work on IE6/7 issues towards the RCs - Decide based on how ready it seems to be whether it should be the default in the RCs. I have set off tomorrow evening to work on NuPlone. - Danny has a made a fair number of improvements on the Informaat NuPlone-based intranet design, which might be mergable into NuPlone directly. But he has no time to work on that. If he sends those changes to me, I'm happy to merge them and sanitize. I have asked him several times, but no response yet. -- Alexander Limi · http://limi.net ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
On Tue, 03 Apr 2007 03:45:56 -0700, Wichert Akkerman <[EMAIL PROTECTED]> wrote: - Members folder gets created even though it's turned off? Bug, should be fixed. Still present. - Put back autofocus behaviour now that we have ondomload (make sure tabindex is correct) Already done I think Halfway, the iterator still emits tabindex="0", which is wrong, so the JS is commented out for now. But shouldn't be hard to fix, and I asked Florian if he could have a look today. - Move sendto/print/whatever to bottom of page, use text representation Needs to happen soon or becomes 3.5 material. Done. Better styling is coming. - Fix up Table-of-Contents styling - Fix up presentation mode styling Needs to happen soon or becomes 3.5 material. Part of my work scheduled for tomorrow. It depends on getting some help with sanitizing the JS since it emits invalid HTML right now. - Search: "only in this section" checkbox Needs to happen soon or becomes 3.5 material. Added. - Fix in 3.0.x releases - Incremental KSS UI improvements, examples: - Login should be in-place (digg.com for an example) - Adding comments should give you a textfield inline - etc... 3.0.x minor are for bug and security fixes, not feature changes. So in 9 months, we can add comments without reloading the page, great... -- Alexander Limi · http://limi.net ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Re: The big 3.0 ;)
On Tue, 03 Apr 2007 12:47:35 -0700, whit <[EMAIL PROTECTED]> wrote: Alec Mitchell wrote: I don't see why this should be considered any better/worse than the content add menu which uses the exact same links and will be shown on all such pages as well. From a spiders point of view, it's not different, AFAIK. Not that this isn't an important issue, but we've lived with it for a long time. Forget the spidering comment, that was just an additional concern. The real issue here is that people get "dead content objects" since it doesn't use portal_factory. It's Plone 1.0/2.0 all over again. this is like 3-4 line fix unless you wanted to create a proper add view (ie less effort than has been expended in writing emails about it). might have time this weekend to do it. Why not just link to the same adding method as Plone uses instead of the old-style adding method? That way, portal_factory is used, and everyone is happy. -- Alexander Limi · http://limi.net ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
