The mailing list for users and developers of Zopeskel, a collection of skeletons for quickstarting Zope and Plone projects.

[ZopeSkel Issue Tracker] #68 - New issue: HISTORY.txt file not generated by "plone" template

A new issue has been submitted to the Issue tracker tracker by Anthony Bosio and awaits confirmation.

Issue Information

Issue HISTORY.txt file not generated by "plone" template (http://plone.org/products/zopeskel/issues/68)

Issue Details:

No preliminary .docs/HISTORY.txt file is generated by "plone" template. This causes buildout to fail which may confuse new users.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 10 Apr 04:24

[ZopeSkel Issue Tracker] #67 - New issue: Bug in "plone" template creates two packages inside egg

A new issue has been submitted to the Issue tracker tracker by Anthony Bosio and awaits confirmation.

Issue Information

Issue Bug in "plone" template creates two packages inside egg (http://plone.org/products/zopeskel/issues/67)

Issue Details:

Using the "plone" template in ZopeSkel 2.21.2 to create an add-on product egg called collective.foo results in a ./collective/foo namespace package and a ./src/collective/foo namespace package. collective.foo -------------- -/collective --/foo ---configure.zcml ---__init__.py [ def initialize(context): ] ---tests.py -/docs -/src --/collective ---__init__.py [ __import__('pkg_resources').declare_namespace(__name__) ] ---/foo ----__init__.py [ empty ]

This is an automated email, please do not reply - plone.org Administrator

headers

Cris Ewing | 2 Nov 16:17

Fwd: ZopeSkel 3.0a1

Hi all,

Somehow, someone deleted the 3.0a1 release of ZopeSkel from pypi.  I have re-released the package and it is
restored.  

I would like to take this opportunity to say that I hope that this was just some random pypi problem and not a
deliberate removal of a release.  Removing released code from PyPI is a cardinal sin.  Both Marin and my
classes here at the Plone Conference depend on the presence of that release.  

If this was not a mistake, and was in fact intentional, would the person responsible for deleting the
release please contact me directly, off-list, so we can discuss whatever issue you may have, I'd
appreciate it.  

Cris

Begin forwarded message:

> 
> 
> Argh! :)
> 
> Somewhere between yesterday afternoon and right now, ZopeSkel 3.0a1
> disappeared off PyPI.
> 
> As I told my training course attendees, all 26 of which now have a
> build with ZopeSkel = 3.0a1 pinned, removing packages from PyPI *ever*
> is a terrible sin. I suggested the workaround if it ever happened was
> to find out who did it and, well... 
> 
> Can we please have it back? It's OK if it's hidden, but deleting it is very bad.
> 
> Martin

Cris Ewing
--------------------------------------------------
Principal, Cris Ewing, Developer LLC
http://www.crisewing.com
cris@...
1.206.724.2112

headers

plone.org Administrator | 7 Oct 03:21

[ZopeSkel Issue Tracker] #65 - Re: Adding plone.app.testing to templates

A new response has been given to the issue Adding plone.app.testing to templates in the tracker Issue tracker by hvelarde.

Response Information

Issue Adding plone.app.testing to templates (http://plone.org/products/zopeskel/issues/65)

Response Details:

plone.app.testing 3.x is for Plone 3.x: http://pypi.python.org/pypi/plone.app.testing/3.0a1 plone.app.testing 4.x is for Plone 4.x: http://pypi.python.org/pypi/plone.app.testing/4.0.2 just let me know.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 7 Oct 01:13

[ZopeSkel Issue Tracker] #64 - Re: ZopeSkel is about promoting best practices, so mixed messages are bad

A new response has been given to the issue ZopeSkel is about promoting best practices, so mixed messages are bad in the tracker Issue tracker by Cris Ewing.

Response Information

Issue ZopeSkel is about promoting best practices, so mixed messages are bad (http://plone.org/products/zopeskel/issues/64)

Issue state: Unconfirmed -> Resolved

Response Details:

I think your objection here has more to do with parsing wording than with actual intention. The zopeskel readme does not say that the preferred way to get a plone instance is with zopeskel. What is says is that a typical plone development workflow follows the path of building plone4 with a zopeskel buildout and then adding in one or more packages. The wording in the zopeskel readme is not especially clear, so I'll fix that, but I agree with the general principal that for most use-cases, starting with the plone installers is the best way to get going. The layout of the installers is well unified, the buildout.cfg structure is standardized, and having newcomers use that method is a great help to the community when it comes time to help newcomers figure out what went wrong. Advanced developers and deployers who are getting ready to deploy a live site may start with a zopeskel buildout template, but these folks know what they are doing and can read past the warnings, especially now that they are more friendly in nature.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 7 Oct 01:07

[ZopeSkel Issue Tracker] #65 - Re: Adding plone.app.testing to templates

A new response has been given to the issue Adding plone.app.testing to templates in the tracker Issue tracker by Cris Ewing.

Response Information

Issue Adding plone.app.testing to templates (http://plone.org/products/zopeskel/issues/65)

Issue state: Unconfirmed -> Postponed

Response Details:

well, the only one's for which it would work at all would be plone4 stuff, right? Adding plone.app.testing to earlier versions of plone leads to all sorts of buildout version conflict fun. I would suggest that after we merge templer into the trunk, we can start thinking about doing stuff like this, making the testing infrastructure of a package depend on the version of plone for which it is intended, etc.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 7 Oct 00:57

[ZopeSkel Issue Tracker] #54 - Re: plone template should have an option to generate skins folder and related xml files

A new response has been given to the issue plone template should have an option to generate skins folder and related xml files in the tracker Issue tracker by Cris Ewing.

Response Information

Issue plone template should have an option to generate skins folder and related xml files (http://plone.org/products/zopeskel/issues/54)

Issue state: Confirmed -> Postponed
Severity: Medium -> Important

Response Details:

I'm going to put this off until after we've merged the templer work in zopeskel 3.x It would be possible right now to add an entire set of structure like this to a template like the plone one, but to do so means that you have to add it for __all__ runs, and then delete the whole damned thing after the run is complete. The structures setup in templer makes this much easier to accomplish. This will not be implemented in zopeskel 2.x unless someone else steps up to do it.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 7 Oct 00:59

[ZopeSkel Issue Tracker] #43 - Re: Command-line variables are taken only for commands like "create" but they don't work for localcommands like "addcontent".

A new response has been given to the issue Command-line variables are taken only for commands like "create" but they don't work for localcommands like "addcontent". in the tracker Issue tracker by Cris Ewing.

Response Information

Issue Command-line variables are taken only for commands like "create" but they don't work for localcommands like "addcontent". (http://plone.org/products/zopeskel/issues/43)

Issue state: Confirmed -> Postponed

Response Details:

Putting this on hold, because at the moment this is by design. We may be able to find a way to fix this going forward, but with the 2.x infrastructure it will be prohibitive to fix.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 15 Sep 14:54

[ZopeSkel Issue Tracker] #66 - New issue: the "view" subcommand must change my MyCustomTypeView to MyCustomType

A new issue has been submitted to the Issue tracker tracker by Luca Fabbri and awaits confirmation.

Issue Information

Issue the "view" subcommand must change my MyCustomTypeView to MyCustomType (http://plone.org/products/zopeskel/issues/66)

Issue Details:

When using paster addcontent view The wizard ask me for a view name. Is a common error (only for me?!) to specify a final "View" after the view name. This will generate a lot of code like: MyCustomTypeViewView Maybe ZopeSkel can remove the final "View" if present.

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 8 Sep 23:37

[ZopeSkel Issue Tracker] #65 - New issue: Adding plone.app.testing to templates

A new issue has been submitted to the Issue tracker tracker by hvelarde and awaits confirmation.

Issue Information

Issue Adding plone.app.testing to templates (http://plone.org/products/zopeskel/issues/65)

Issue Details:

I would love to add plone.app.testing to ZopeSkel templates. Which ones do you consider appropriate for this?

This is an automated email, please do not reply - plone.org Administrator

headers

plone.org Administrator | 29 Aug 12:06

[ZopeSkel Issue Tracker] #63 - Re: plone3_buildout shouldn't be installing Plone 4

A new response has been given to the issue plone3_buildout shouldn't be installing Plone 4 in the tracker Issue tracker by Jean Jordaan.

Response Information

Issue plone3_buildout shouldn't be installing Plone 4 (http://plone.org/products/zopeskel/issues/63)

Response Details:

When running plone3_buildout, the Plone Version default value is coming from plone4_buildout.Plone4Buildout line 41.

This is an automated email, please do not reply - plone.org Administrator

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31

2	April 2012
2	November 2011
5	October 2011
2	September 2011
9	August 2011
2	July 2011
4	June 2011
7	May 2011
9	April 2011
1	March 2011
2	January 2011
14	December 2010
17	November 2010
34	October 2010
12	September 2010
7	July 2010
39	June 2010
9	May 2010
6	April 2010
74	March 2010
1	February 2010
10	January 2010
2	December 2009
3	October 2009