Hi guys. I just updated the http://plone.org/development section. There is
lorem ipsum but I will fix that soon. But I need some feedback from you
guys:
- What do you think is missing?
- How can we separate the material logically?
- Once we get everything that is missing into it, someon
> > Being that primary purpose of the framework team is to review code,
> > some short day after December 1 the plone 2.2 framework team
> > becomes obsolete. Or at least enters a time of transition.
> >
> > being the bootstrap team, we get the honor of deciding what happens
> > next and I'm go
Before we disolve the framework team we need to capture all the information
that is important SOME PLACE. I am trying to capture it all on
http://plone.org/development. Some of the information is transisient -- I
want to isolate that information. I would like:
- What is the process for a rele
I think its natural. The framework team freezes features/functionality.
The call to arms is to ensure this frozen feature set is what needs work.
A new framework team is created. Responsible for 2.3 and/or possible some
other 2.2 work.
Alan
> -Original Message-
> From: [EMAIL PROTECT
> > +1 on disolving the team. I think it's a great idea and
> lots of other
> > folks would jump on board.
> >
> > Maybe one person should stay on so that the next team
> doesn't have to
> > figure it all again. I nominate Whit ;)
> >
> > -Michel
> >
> dude. my girlfriend is going kick your as
ning these installers will have a
hard time porting to newer Python.
Cheers,
Alan Runyan
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team
Alan Runyan
Enfold Systems, Inc.
http://www.enfoldsystems.com/
phone: +1.713.942.2377x111
fax: +1.832.201.8856
-Original Message-
From: Sean Duffy [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 10:45 AM
To: [EMAIL PROTECTED]
Subject: Plone site compromise
> Framework-Team mailing list
> Framework-Team@lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
>
--
Alan Runyan
Enfold Systems, Inc.
http://www.enfoldsystems.com/
phone: +1.713.942.2377x111
fax: +1.832.201.8856
___
+1 to Hanno/Martin being Plone 4 release manager/communicator
--
Alan Runyan
Enfold Systems, Inc.
http://www.enfoldsystems.com/
phone: +1.713.942.2377x111
fax: +1.832.201.8856
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http
take framework team some time. So I would suggest allocating
lots of resources to reviewing these changes since they are many.
The PLIP should grow by 2-3 paragraphs explaining at a high level what
changes were made and why they were made.
Does this sound correct?
--
Alan Ru
gh,
> it's just another regression to work around what many consider a real
> UI bug.
I agree. Who owns this part of the UI?
--
Alan Runyan
Enfold Systems, Inc.
http://www.enfoldsystems.com/
phone: +1.713.942.2377x111
fax: +1.832.201.8856
___
F
have been working on the problem for over 3 years. I would suggest that
sidnei/framework team focus on a platform agnostic dav client on the first
go around. If you focus on having every platform supported fully - it may or
may not happen.
I will let sidnei answer for himself.
--
Alan Runyan
Enfol
rged
upstream to Zope, AT, Plone)
- ExtensionRename (policy for how to handle renaming)
- Lime and/or Calendaring (should be merged into ATContentTypes,
these are marshallers for Links and Events)
The upside is that this stuff has been in production a long time. And
it does work with OS X.
cheers
>> I don't think that's a good option. We may not need to support both, but
>> supporting one is probably quite important. For one thing, it'd kill Enfold
>> Desktop and similar integrations. WebDAV is also very useful for bulk
>> movement of images and documents.
Webdav is main mechanism for iPad
14 matches
Mail list logo
