Hola. Soy Jefe del Áea de Tecnologías de Inclusión del CEDETI (www.cedeti.cl), es un centro de la Pontificia Universidad Católica de Chile que está enfocado al desarrollo de apoyos para personas en situación de discapacidad.

Tenemos un proyecto interesante en desarrollo y buscamos a una persona que tenga experiencia programando en Python, especialmente, aplicaciones que sean portables y de bajo uso de recursos.

La vinculación es por proyecto con posibilidad de otros trabajos en el corto y mediano plazo.

Les escribo solicitando su ayuda para difundir esta convocatoria. Hay una buena renta de por medio.
Datos para contacto de interesados: adapar@gmail.com.
Agradezco su apoyo.


Andrés Aparicio

Change log

• Give 'Modify portal content' permission to the Owner role by default. This allows sane use of workflow-less content types. Fixes http://dev.plone.org/plone/ticket/7180 [wichert]
• Modify form_tabbing.js to not touch the edit form if there's no fieldsets. [nouri]
• Set the media for ploneKss.css to screen so it can be merged with the other CSS files. [wichert]
• Add the language control panel when migration from previous Plone versions. [wichert]
• Fixed missing i18n markup in folder_constraintypes_form for portal types translation. This closes http://dev.plone.org/plone/ticket/7067. [hannosch, naro]
• Add migration to set the default GS profile when upgrading from 2.1. [alecm]
• Use a button/script combo for product reinstall from the control panel. http://dev.plone.org/plone/ticket/6457 [alecm]
• Remove silly root check from stripGRUFLocalRolePrefix script to fix migration bug. http://dev.plone.org/plone/ticket/5817 [alecm]
• Made Plone use 1/10th of the memory on file uploads. Details in http://dev.plone.org/plone/ticket/7027 (also backported to Plone 2.5.x) [zegor]
• Reverted addition of the GenericSetup import and export steps from PloneLanguageTool. [hannosch, wichert]

• http://www.plone4universities.org (Portal del proyecto)
• www.plone4universities.org/universities-using-plone  (Listado de universidades)

El blog "El Francotirador" publica un reportaje sobre el uso del software libre en el estado chileno.

Uno de los entrevistados es Christian Sifaqui, Jefe de sistemas de la BCN (Biblioteca del Congreso Nacional de Chile), quién describe como el administrador de contenidos Plone ha contribuído a darle valor a las actividades diarias de la organización.

Artículo disponible en: 

http://www.elfrancotirador.cl/2007/10/16/software-en-el-estado-licencia-para-pagar/

Feature enhancements in this release

The following features are associated with this release:

#118: Portlets engine based on PlonePortlets and Viewlets

Currently, the portlet mechanism in Plone is very crude. A proper structure to handle third-party portlets, individual caching policies and even asynchronous portlet updates is desirable.

#122: Edit-in-place mode for all basic field types

A lot of the time you just want to change a single attribute on an existing item. We want to enable an "advanced users" feature to make this quicker and more efficient.

#125: Ensuring link/reference integrity (removing 404 links)

One of Plone's weaknesses at the moment is the lack of resource tracking. If you delete a picture, and another document references this picture, you won't know before you look at the other document.

#127: Move properties to Edit screen using pre-loaded fieldsets

Clean up the UI a bit by moving the Properties to a grouped schemata on the edit screen.

#132: Return to Icon Flexibility

It is much more flexible to use the "getIcon" method to display icons via CSS in Plone than using the "portal_type". If the portal type is used, then there can only be a single icon for a content type, which makes it impossible to change the icon depending on what is contained in the content type. This is a proposal to get some of the flexibility back that was lost while going from Plone 2.0 to Plone 2.1.

#134: Reader and Editor roles

It is too difficult to share a private or restricted document with another person or group. By introducing Reader and Editor roles, the Sharing tab can be used to let any given user or group the right to read or edit any object.

#142: Componentise the global content menu

The global content menu, the green one with 'actions', 'add item' and 'state' drop-downs, is one beastly monolithic page template with a lot of logic. Worse, whilst it is possible to use actions to add new items to the 'actions' menu, if you want to add a new menu (e.g. for versioning or staging) you have to override the template wholesale. This proposal aims to change that by using views, adapters and utilities.

#144: Generalized Next / Previous navigation

There is a need for a feature that allows a user to navigate easily between content items stored in a container such as a folder.

#145: Locking

Prevent concurrent through-the-web editing in Plone. Trigger WebDAV locking on edit. Make it possible to borrow locks easily.

#146: Improve sharing page

The sharing page has to be simplified significantly.

#148: Move to CMF 2.1

Require CMF 2.1.

#149: Improved Markup Support

Creating a mechanism for adding support for additional markup languages such as Markdown and Textile for TextField fields and a site-wide policy for defining available and default formats.

#152: Dashboard

We want to create a page where the user can add portlets/widgets showing summaries with content of the portal. The idea is to provide an overview/summery over the content. The criteria which content and wich portlettype can be set/chosen by the user. The personal google page is a very good example.

#153: Portal type configlet in plone setup

Proposal for a configlet in Plone ui to control various settings related to portal types.

#157: Content rules engine

With the introduction of Zope 3 events, it becomes possible to react to events such as "object added" or "object modified". Plone should enable site administrators to set up rules that are invoked when these events occur under certain conditions. For example, it could be possible to move all Events added to a particular folder to the /events folder automatically.

#161: Remove migration code for old releases

Don't support migrating to Plone 3 from versions earlier then Plone 2.1.0-final.

#163: Minimize page weight

Plone as it is per Plone 2.5 is unnecessarily heavy when it comes to downloaded CSS, JS etc.

#168: integrate iterate for checkin/checkout/staging

builds on top of cmfeditions, to allow for explicit checkin/checkout and staging, without the overhead of site stages.

#171: Include KSS in Plone

KSS is an AJAX framework with Zope and Plone support. We propose inclusion of the framework core as part of Plone, together with the implementation of some UI improvements with Ajax.

#172: Wiki syntax support for all content

"wicked" provides usable wiki-like linking and content creation within AT based content. This proposal recommend the inclusion of this behavior as an option for Plone's content.

#173: OpenID support

Add support for the OpenID decentralized identify system to Plone

#174: More configurable and reusable i18n features

Move code for normalizing of ids out of CMFPlone and make it optionally configurable per language. Also consolidate all the three availablelanguage.py files currently found in AT, CMFPlone and PloneLanguageTool into an external package and hook these up using utilities instead.

#175: Expose more settings in the Control Panel

There are a lot of common settings that you still have to reach for the ZMI to adjust.

#176: New visual design for Plone

The existing Plone look is getting a bit long in the tooth — seeing as it essentially is the same as when it was conceived 5 years ago, it's time for an update.

#178: Return to using getIcon for content type icons

Aka. as "the un-PLIP", this proposal advocates changing back to the earlier approach used for content type icons in Plone.

#180: Add a RichText field to Smart Folders

Smart Folders would be much more flexible in real-world deployments if there was a RichText field before the results listing.

#26: Ship Plone with additional workflows and a workflow control panel

Plone currently ships with one workflow, we propose to ship it with four pre-defined workflows and a control panel that cover most of the use cases people normally have: Community, Intranet, Web Publishing and Extranets.

#8: Versioning

Plone needs to have a consistent, core solution for simple versioning tasks. This is expected of modern CMS packages. This PLIP outlines the needs and a proposed solution for versioning. Another PLIP will cover staging and multisite usage.

• Removal of portal_memberdata
• Ship with better default member handling based on Membrane
  • Having something like Teamspace for project/team handling and project workspaces + delegated user management
• Replace the discussion architecture with Ploneboard and/or Listen
• Better media file handling (Video, audio) OOTB
• Expanded Document Management capabilities
• Improved BLOB support
• Using eggs for product packaging and dependencies
• Atom support in the core
  • Syncing between portals using Atom or RSS + something like MS' extensions to it
• Power User role
• Replacing the default theming approach with something similar to Deliverance
• Possibility to separate content production from content delivery? Entransit etc.
• Subscription to pages/containers (content subscription infrastructure)
• Composite Pages?
• Ship Plone with support for the most common auth setups (LDAP, Radius, NTLM, others?)
• Get a better export/import story
• Stream-based portal transforms replacement
• Improved email framework (incoming email handling)
• WebDAV improvements