Re: [Zope3-dev] RFC: zopeproject
On Wed, 2007-07-18 at 18:50 +0200, Philipp von Weitershausen wrote: * Would it help if the 'myzopeapp' package would not be in the top- level MyZopeApp directory, but in a 'src' directory below MyZopeApp? Would that make it clearer where to go? +1 * grokproject actually also creates a hello world browser page. That way there's some initial code there and people might know better where to go in and change stuff. Would that help? Or would that be too much unnecessary boilerplate? I don't think this is unnecessary boilerplate for many projects, but it's not universal. What is the appropriate way to 'specialize' the zopeproject recipe for different 'default' purposes, one of which would be 'hello world'? 2. Is this kind of setup (I mean using zopeproject) supposed to be used to deploy applications in production environments? It certainly can be used for deployment, though you'll probably want to make some changes to the configuration files before you deploy (rip out the administrator account, deactivate developer mode, etc.). Again, this is a good question that should be answered in the zopeproject docs. If the most common configuration changes can be gathered into a 'deployment' recipe, that would also be useful, I think. - Michael R. Bernstein signature.asc Description: This is a digitally signed message part ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] RFC: zopeproject
On Thu, 2007-07-26 at 23:17 +0200, Philipp von Weitershausen wrote: On 18 Jul 2007, at 22:34 , Maciej Wisniowski wrote: I will add this to the zopeproject docs. I wonder: * Would it help if the 'myzopeapp' package would not be in the top- level MyZopeApp directory, but in a 'src' directory below MyZopeApp? Would that make it clearer where to go? * grokproject actually also creates a hello world browser page. That way there's some initial code there and people might know better where to go in and change stuff. Would that help? Or would that be too much unnecessary boilerplate? For me, second approach is more clear but even simple README.txt, located at new project's folder, with description of next steps, should be enough. The problem with boilerplate README files is that they're never changes after the fact, therefore making it look like your code has documentation while in fact it's just the unchanged boilerplate. At least the code *has* to be changed to make something useful out of it. Hmm. Perhaps both sets of requirements can be satisfied by generating a REPLACEME (or RENAMEME, or EDITME) file with the boilerplate in it. That should still help a newbie get things going while making it clear that it is not (yet) actual documentation for the new code. - Michael signature.asc Description: This is a digitally signed message part ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Automated egg releases
On Wed, 2007-09-26 at 17:18 +0200, Martijn Faassen wrote: I definitely think we should work out a human procedure *first*. But some tools to assist the human in doing repetitive, failure-prone work (releasing versions of many eggs) would definitely be appreciated by me. Perhaps these could be made lint-like initially. I.e. you run them and the tool reports possible problems (no tag created, version number in CHANGES.txt appears wrong, setup.py misses information we want in there, etc). Once that's in place, we could introduce features that actually perform actions. +100 An advisory tool could also optionally use Cheesecake. - Michael R. Bernstein signature.asc Description: This is a digitally signed message part ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope-dev] I'd lobe to merge the zope3-dev and zope-dev lists
On Thu, 2007-10-04 at 19:32 +0530, Baiju M wrote: Jim Fulton wrote: Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. +1 What about retiring #zope3-dev IRC channel and only using #zope ? No. #zope is roughly the equivalent of the main zope list. There is no #zope-dev channel. Now, someone might suggest that the zope3-users list should be merged with the main zope list, but that someone wouldn't be me. At least not as long as there are separate releases being made. - Michael Bernstein signature.asc Description: This is a digitally signed message part ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
