in the row
background.
* All the Plone tests now pass (when run in known-to-be-compatible
groups by a script Hanno wrote).
To do
--
* PLIP implementation deadline is Sunday the 16th.
Cheers,
Erik Rose
___
Framework
of products. MatthewWilkes will talk to
Hanno about this and see if it really did help performance. The
FWT is concerned about breaking every product if it turns our
we're just replacing one very slow thing with many less-slow
things.
Cheers,
Erik Rose
folks from Four Digits are going to sprint 3 days
before the PLIP deadline and, defying the very laws of physics,
still plan to get it all done.
Cheers,
Erik Rose
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org
1) The current code base is located in the Collective. Since TinyMCE
will be
the default editor in Plone 4 should I move (copy) the code base to
Plone
SVN?
-1. Why make it harder for people to contribute?
2) I'm currently using the Products namespace for the package. Would
it be
better
have to rebalance the load anyway once we know which 40% of them
actually get implemented.
Cheers,
Erik Rose
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
/conf/download/3839?rec_key=0553f747be52398457b84dca12426d904f2d8280
Next week's meeting will be on the same day, same time.
Cheers,
Erik Rose
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework
It occurred to me during today's call that a lot of our discussions
hinged on what's happening in Plone 5: ensuring smooth transitions,
not changing things that are about to change again, and so on. Might
it be handy to have Hanno on our calls, since he's elbow-deep in Plone
5 every day?
I've put up a Doodle calendar so we can readjust our meeting time if
need be: http://www.doodle.com/4qd32ckeimc69x48 . Either they just
added timezone support, or I just figured it out, so we don't have to
convert in our heads anymore. :-)
Regards!
Erik Rose
Based on the responses, generally folks are available Monday and
Tuesday at 2:00PM US/Eastern time. This works for me, how about
the rest?
Good for me.
___
Framework-Team mailing list
Framework-Team@lists.plone.org
reasons, but I can relate to their pain points and look
forward to spending my FWT votes to try to make things simpler and
more consistent (which is hopefully the way we're going anyway).
Erik Rose
weblion.psu.edu
___
Framework-Team mailing list
We currently have responses of:
available: Raphael (3), Ross (4), Matt (4)
unavailable: Andi (3)
I'm available. If a million other people want to do it, I'll be
equally happy to bow out and just write a bunch of PLIPs.
Erik
___
Framework-Team
One way to mitigate this — and make Plone seem a bit more modern
along the way — could be to apply the new typography/theme that I'm
currently applying to trunk. This is essentially the typography from
the plone.org redesign along with a color-neutral design for the
navigation and other UI
1) Everyone is for a near-future release of the less risky work
being done in trunk
2) Calling it 3.5 breaks the dot release contract. Go with Plone 4
instead.
+1
I'd also be okay with (and in fact in favor of, if it didn't create
too much additional work) releasing another round of Plone
I actually first implemented it exactly that way (even called it
IRefreshableLockable), then wondered if the complexity was worth
it. I can go either way, but would like to hear some other opinions
of best practice in a case like this.
For what a non-3.x-FWT opinion is worth, I'd rather
This is actually really bad, and I think it should block the 3.2 full
release (i.e. with installers).
+1
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
On Dec 27, 2008, at 13:31 , Ross Patterson wrote:
It seems like this this dump format will likely become a point of
hackability in our software ecosystem. People out there will find
interesting things to do with it aside from dump-and-reload. This
would
be a good thing except we're
On Dec 28, 2008, at 5:23 , Tom Lazar wrote:
i particularly like the notion of using workflow states as
'reminders' to make sure aspects aren't missed.
OTOH, workflow states are serial, and it'd be a shame to force teams
to do their evaluations in a specific order.
On Jan 2, 2009, at 14:33 , Tres Seaver wrote:
OTOH, workflow states are serial, and it'd be a shame to force teams
to do their evaluations in a specific order.
You can actually have multiple workflows for a given type. I may be
the
only person who has ever actually used the feature, but
18 matches
Mail list logo
