plonewars.com

September 25th, 2007

Get Paid: GetPaid mailing list on Nabble

<p>Interface with GetPaid-development mailing list at <a href=”http://www.nabble.com/GetPaid-for-Plone—Dev-f27137.html”>http://www.nabble.com/GetPaid-for-Plone—Dev-f27137.html</a><br /></p>

Get Paid: GetPaid mailing list on Nabble

Originally from Planet Plone


from Yoda http://plonewars.com/2007/09/25/get-paid-getpaid-mailing-list-on-nabble/







September 25th, 2007

Fundraising — Fundable — update CalendarX code for Plone 3.0 and beyond

Fundraising — Fundable — update CalendarX code for Plone 3.0 and beyond

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


from Yoda http://plonewars.com/2007/09/25/fundraising-%e2%80%94-fundable-%e2%80%94-update-calendarx-code-for-plone-30-and-beyond-2/







September 25th, 2007

zwiki.org #1322 Plone 3 compatibility issues

zwiki.org #1322 Plone 3 compatibility issues

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


from Yoda http://plonewars.com/2007/09/25/zwikiorg-1322-plone-3-compatibility-issues/







September 25th, 2007

The Plone Blog: Fans of CalendarX Unite: Help Sponsor Plone 3.0 Update!

The amazing and indefatigable Darci Hanning is helping organize a “social source” sponsorship effort to raise $2000 to support Lupa Zurven’s work to update CalendarX for Plone 3.0.  CalendarX is a widely-used calendaring add-on Product for Plone — if you’d like to see it updated for Plone 3.0, now’s the time to join together with other Plone community members and make it happen.

Lupa’s sponsorship goal is $2000.  As of this morning, there are $700 in pledges.  They’re using Fundable.org (a Plone-powered site!), which lets you make a pledge in any amount from $10 on up, and you’ll only pay if the $2000 goal is reached.   With $1300 to go, we only need another 26 people to pledge $50 each. That’s peanuts, especially compared with the number of folks who’ve benefitted from CalendarX over the years.

This is the funding model we used last year to sponsor a round of work on Ploneboard, and has also helped drive the GetPaid project forward. It’s a great way to share the load of sponsoring useful products for which there isn’t a single big customer. 

I hope you’ll join me in sponsoring CalendarX.

The Plone Blog: Fans of CalendarX Unite: Help Sponsor Plone 3.0 Update!

Originally from Planet Plone


from Yoda http://plonewars.com/2007/09/25/the-plone-blog-fans-of-calendarx-unite-help-sponsor-plone-30-update/







September 25th, 2007

Fans of CalendarX Unite: Help Sponsor Plone 3.0 Update!

The amazing and indefatigable Darci Hanning is helping organize a “social source” sponsorship effort to raise $2000 to support Lupa Zurven’s work to update CalendarX for Plone 3.0.  CalendarX is a widely-used calendaring add-on Product for Plone — if you’d like to see it updated for Plone 3.0, now’s the time to join together with other Plone community members and make it happen.

Lupa’s sponsorship goal is $2000.  As of this morning, there are $700 in pledges.  They’re using Fundable.org (a Plone-powered site!), which lets you make a pledge in any amount from $10 on up, and you’ll only pay if the $2000 goal is reached.   With $1300 to go, we only need another 26 people to pledge $50 each. That’s peanuts, especially compared with the number of folks who’ve benefitted from CalendarX over the years.

This is the funding model we used last year to sponsor a round of work on Ploneboard, and has also helped drive the GetPaid project forward. It’s a great way to share the load of sponsoring useful products for which there isn’t a single big customer. 

I hope you’ll join me in sponsoring CalendarX.

Fans of CalendarX Unite: Help Sponsor Plone 3.0 Update!

Originally from The Plone Blog by Jon Stahl


from Yoda http://plonewars.com/2007/09/25/fans-of-calendarx-unite-help-sponsor-plone-30-update/







September 25th, 2007

Permanent Link to Enabling Postfix on MacOSX Tiger

Enabling Postfix on MacOSX Tiger September 22nd, 2007 I’m doing some testing of a Plone site … server such as postfix running on my Mac, listening on port 25. Tiger ships with Postfix but it’s disabled by default. I found these instructions for enabling Postfix, so I can now send emails

Permanent Link to Enabling Postfix on MacOSX Tiger

Originally from [Technorati] Tag results for plone


from Yoda http://plonewars.com/2007/09/25/permanent-link-to-enabling-postfix-on-macosx-tiger-3/







September 25th, 2007

And it’s not even a sweeps month

And it’s not even a sweeps month September 25, 2007 at 12:48 pm · Filed under cheap flowers online, cut flowers, dhammatale, drug facts, plone, radio, stats Clit free nude alopecia cialis Sex Online Pharm Shop upskirt Online pharmacy http://www.hartwellshamus.com lesbian bdsm

And it’s not even a sweeps month

Originally from [Technorati] Tag results for plone


from Yoda http://plonewars.com/2007/09/25/and-it%e2%80%99s-not-even-a-sweeps-month/







September 25th, 2007

Why Zope community use namespace packages ?

Why Zope community use namespace packages ?

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


from Yoda http://plonewars.com/2007/09/25/why-zope-community-use-namespace-packages/







September 25th, 2007

Kamon Ayeva: Paris bootcamp for learning to develop with Plone 3

At Ingeniweb, we are organizing a bootcamp in Paris for people who want to start developing with the Plone 3 platform, i.e. using Zope 3 patterns and tools. This is a 3-day training session scheduled for october 22-24.

I’m happy to announce that we will benefit from the participation of a KSS core team member as a co-trainer ; Godefroid Chapelle is going to lead the KSS part, on the 2nd day.

You can contact me directly if you are interested, so we can arrange your participation.

For more information, see the full announcement on plone.org.

Kamon Ayeva: Paris bootcamp for learning to develop with Plone 3

Originally from Planet Plone


from Yoda http://plonewars.com/2007/09/25/kamon-ayeva-paris-bootcamp-for-learning-to-develop-with-plone-3/







September 25th, 2007

Baiju M: Why Zope community use namespace packages ?

Zope project and the community in general use lots of namespaces
packages. Though, we have some non-namespace packages like
ZODB3,ZConfig etc. Zope community has created many namespaces
for packages like `zope`, `zope.app`, `zc`, `z3c`, `lovely` etc. Here
`zc` stands for Zope Corporation, `z3c` for Zope 3 Community and
lovely for Lovely Systems’ packages.

Python is a language with namespace support at many levels.
Remember, the last line of Zen of Python reads like this: “Namespaces
are one honking great idea — let’s do more of those!”
Take it positively, don’t interpret it more ;)

A namespace package will not have any method,class or any other
objects defined in that level. So a normal namespace package will be
only having an empty `__init__.py` file. Eggs and setuptools provides
some new advantages for the distribution of namespace packages. So,
normally a namespace package’s `__init__.py` file will contain
something like this:

 import pkg_resources pkg_resources.declare_namespace(’zope’)

That’s all you required to put in your namespace package’s
`__init__.py` file. But you also will be required to add one more
keyword argument for `setup` function in your `setup.py` script like
this:

  namespace_packages=[’zope’]

You can even have nested namespace packages, in that case you have to
add it like this:

  namespace_packages=[’zope’, ‘zope.app’],

Remember, Zen of Python also says: “Flat is better than nested.” .
Even though Zope use `zope.app` nested namespace package, Zope
community discourage nested namespace packages. The `zope.app`
namespace may be consider as a mistake of Zope project.

The `zope` and `zope.app` were the first namespace packages used by
Zope. I still remember the appraisal I got from Jim Fulton after
implementing his proposal for making `zope.app` a pure namespace
package.

Here I will list some advantages of namespace packages. Feel free to
add/explain anything you found. :)

  1. Better grouping for projects/community/companies
  2. Better name for packages and don’t worry about a name conflict
  3. Re-use package name in different namespaces
  4. Easy distribution as eggs

I think the last point requires bit explanation. Consider two
packages in same namespace, `zope.interface` and `zope.testbrowser`.
In Python, package name is tied to directory structure. So, in normal
distutils based distribution both `interface` and `testbrowser` should
be under `zope` directory. But setuptools and eggs allows you to
install both separately and still use both.

Let’s save some names for new generation smart Python programmers !
Don’t pollute top-level names, use namespace packages !!

Baiju M: Why Zope community use namespace packages ?

Originally from Planet Plone


from Yoda http://plonewars.com/2007/09/25/baiju-m-why-zope-community-use-namespace-packages/