plonewars.com

<sep/>is a directory containing all the parts that make up a project, including a Zope instance, the Plone sources, custom configuration options, and your our project’s source code. Create one like this<sep/>

Creating a buildout for your project — Plone CMS: Open Source Content Management

Originally from del.icio.us/tag/plone by sweet_k

La Fundación Plone anuncia el lanzamiento de Plone 3.0 — Plone CMS: Open Source Content Management

Originally from del.icio.us/tag/plone by bakara

Open source projects usually have a challenge in producing documentation and keeping it up-to-date.  The challenge arises from a number of factors: things change too fast, can’t find people with good communication skills, keeping those people energized, etc.

Thus, it’s awesome to see Plone with a group that doesn’t just do something adequate, but instead does a sustained and wonderful job.  Darci Hanning announced the updated Plone 3 user manual and Plone 2.5 user manual.  Congrats to Darci, JoAnna Springsteen, Martin Aspeli, Jon Baldivieso, Andrew Burkhalter,
Sam Knox, Jon Stahl, Jeff Pittman, Esther Schindler, Rob Stevenson,
Veda Williams, and Donna Snow.

Looking at that list, I’d say there are a few great choices for Plone Foundation board nominees (wink wink, nudge nudge).

Paul Everitt: Congrats to the Plone 3 docs team

Originally from Planet Plone

Early notice: we’re starting the nomination process and election process for the next Plone Foundation board of directors.  The nomination process should start next week, using the same sequence we’ve done for several years.  We’ll make a formal announcement next week with all the details.

Please consider running!  Especially if you have skills beyond “rock star code god”…the community needs people with certain skills and energy to help organize and maintain the Plone Foundation.  Next year’s board should have a better budget to work with, if the coming ramp-up (more next week) on PF sponsorship works out as hoped.  So it’s a good time to get involved.

As an FYI, I don’t plan to run again, for two reasons: (a) I did a crappy job this year and don’t merit another shot, and (b) I think it’s time for the Old Guard to make way for others.  The PF has succeeded and is a stable basis for others to do new and useful things with.  Thus, I will join the election folks (Joel and others) in conducting the election.

The next notes you will see from me:

1. Announcement of the nomination process.

2. Announcement that the Plone Foundation has formally launched Plone.net and is accepting sponsorship to fund its proposed budget initiatives.

Paul Everitt: Plone Foundation board elections coming up

Originally from Planet Plone

With ZopeSkel you can easily generate a setuptools-ready skeleton for your plone product. To install it:

$ easy_install 
http://svn.plone.org/svn/collective/ZopeSkel/trunk#egg=ZopeSkel-dev

Tip1:

I faced a problem after generating my skeleton with:

$ paster create -t plone_app myploneapp

After I added some python files to the product, I run the following command to see how the package will be built:

$ python setup.py build

I checked the ‘build’ folder. All the files I added are not there !!!. Setuptools didn’t pick my files.
To get all files in the built, you have to do one of these:

• edit the SOURCES.txt file in the egg-info folder and add the full path to the files you added.
• setuptools is an SVN friendly tool. Put your package in an svn repository and check it out. Your working copy will be stuptools-friendly. When you add some files to your package, run:

$ svn add path_to_your_files/
  

and then:

$ python setup.py build
   

look in the ‘build’ folder. You have a complete package without missing files and the SOURCES.txt file is updated.

Tip2:

When generating a plone product skeleton with paster you can tell it to create an svn repository with the standard trunk/ tags/ branches/ hierarchy.

$ paster create -t plone_app myploneapp 
–svn-repository=http://your.svn.server.org/path/to/your/project

This will create:

• The ‘myploneapp’ product in the current folder
• myploneapp/trunk, myploneapp/tags and myploneapp/branches under http://your.svn.server.org/path/to/your/project repository

if you get “No egg-info directory found” error, just update your setuptools to the latest version. This is a known bug in versions prior to 0.6c7. If you cannot or you don’t want to update setuptools for some reasons, do:

myploneapp$ svn ci -m 'I have to check in' 

and then

myploneapp$ python setup.py egg_info

this should fix the problem.

Your friends can install your product by running:

$ easy_install  
http://your.svn.server.org/path/to/your/project/myploneapp/trunk

Tip3:

Vidar wrote a very good tool to generate plone3 pruduct skeleton from wsl files. To install it:

$  easy_install 
http://svn.plone.org/svn/collective/genesis.wsl/trunk

You will get a new paster template named wsl_plone. Take the Vidar’s example from his page and save it as myploneapp.wsl and run:

$ paster create -t wsl_plone myploneapp wsl=myploneapp.wsl 
–svn-repository=http://your.svn.server/your_path/
$ svn ci myploneapp/

to get an svn working copy of your plone3 product.

Mustapha Benali: Tips: paster & svn & setuptools

Originally from Planet Plone

EasyShop — Plone CMS: Open Source Content Management

Originally from del.icio.us/tag/plone by stirlingfriend

PloneMall — Plone CMS: Open Source Content Management

Originally from del.icio.us/tag/plone by stirlingfriend

Alfresco and Plone

Enter Content Here: Alfresco and Plone

Originally from del.icio.us/tag/plone by tonychentie

Zope.org - Developer tips

Originally from del.icio.us/tag/plone by vimes656

I’ve been toying with the idea of writing a web frontend for BitTorrent for a while now (Grok looks like a likely contender for that) but since the ‘official’ python based implementation of BitTorrent is simply much too inefficient I had to first come up with a Python library to some other BitTorrent implementation. In the end, I wrote my own library for the highly commendable Transmission client. And after some clean-up and polish work today, I’m happy to announce a release candidate.

The README, the documentation and the tests live all in the same
document and the whole thing should be pretty straightforward to use. I’m curious, as to whether some other pythonistas might this useful, too. We’ll see.

Tom Lazar: Python Transmission client

Originally from Planet Plone