Re: [Zope-dev] Github tip to get less github spam:
On Mar 13, 2013, at 17:10 , Jim Fulton j...@zope.com wrote: Visit: https://github.com/watching Either unwatch all or selectively unwatch repositories you're not interested in. (If you stop watching all, there's a lot of clicking to then watch repositories again.) Uncheck autowatch (I wish I'd done this a couple of weekes ago :) Thanks Jim, that's a lifesaver. I've been buried in a GitHub spam avalanche, too. I had no idea this page even existed. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Github repo request: zope.tal, zope.testrunner
On Feb 11, 2013, at 11:53 , Marius Gedminas mar...@gedmin.as wrote: Could someone with the magic admin bit please create Github repositories for zope.tal and zope.testrunner? Done. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope2 git mirror not updating?
On Jan 11, 2013, at 14:07 , Wichert Akkerman wich...@wiggy.net wrote: I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? I had already mentioned in a different thread that the Zope and all Products.* packages you see on GitHub are not final migrations, just test migrations. Until a package is clearly marked as migrated in SVN (such as all packages Jim and Tres migrated) the migration is not final and all changes should still be checked into svn.zope.org. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
On Jan 10, 2013, at 11:23 , Patrick Gerken do3cc...@googlemail.com wrote: I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos but not Products.SiteErrorLog. http://svn.zope.org shows me a web view of our old cvs server. There is something wrong. Can I help with something? Going to http://svn.zope.org works fine for me. I see the expected SVN repositories. The GitHub migration happens on an as-needed basis. Package maintainers may request to have packages migrated or, like Jim and Tres are already doing, migrate packages themselves. There is no full migration of all svn.zope.org content. For those packages that are fully migrated you will have obvious markers on the package in svn.zope.org, such as the package being read-only. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
On Jan 10, 2013, at 14:37 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl j...@dataflake.org wrote: For those packages that are fully migrated you will have obvious markers on the package in svn.zope.org, such as the package being read-only. I don't think being read only is enough. Are people supposed to attempt commits to find out if a project is read-only? We should at least leave something like a MOVED_TO_GITHUB file in the project, in addition to making it read only. That's what I meant by obvious marker, such as I did not imply making a package read-only is the only marker. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
On Jan 10, 2013, at 14:45 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 8:39 AM, Jens Vagelpohl j...@dataflake.org wrote: On Jan 10, 2013, at 14:37 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl j...@dataflake.org wrote: For those packages that are fully migrated you will have obvious markers on the package in svn.zope.org, such as the package being read-only. I don't think being read only is enough. Are people supposed to attempt commits to find out if a project is read-only? We should at least leave something like a MOVED_TO_GITHUB file in the project, in addition to making it read only. That's what I meant by obvious marker, such as I did not imply making a package read-only is the only marker. But that's all that has been done for some projects. (Sorry, I don't mean to be critical and I didn't raise the issue when it happened.) OTOH, it's been argued (I disagree :) that I did too much for the ZODB projects. I think it would be helpful if we agreed on what should done, so we have a standard play book. Please get in touch with Tres if you think his migrations should be improved. All other repositories (Zope, Products.*) were test migrations where I asked for feedback and never got any. They are throw-away and not final. The only finished migrations are yours and Tres'. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
On Jan 10, 2013, at 15:40 , Leonardo Rochael Almeida leoroch...@gmail.com
wrote:
I took a quick look at the Zope migration now and I think it's
excellent. The only thing I'd add is that I'd also migrate branches
2.12 and 2.13 branches since they're all active, even if just for
bug/security fixes.
I did not choose to include or exclude any branch. The test migration uses the
package used to migrate most Plone packages from SVN to GitHub, which uses
svn2git underneath. If there's whole branches missing the migration has
obviously failed.
If you want to help you could try a migration with the attached Python script
that Jim wrote as a result of finding bugs in svn2git. I can provide you with a
suitable authors mapping file.
jens
##
#
# Copyright (c) 2012 Zope Foundation and Contributors.
# All Rights Reserved.
#
# This software is subject to the provisions of the Zope Public License,
# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED
# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
# FOR A PARTICULAR PURPOSE.
#
##
%prog [options] subversion_url
svn to git conversion helper
Based loosely on the svn2git ruby tool.
You must have git and the svn git plugin installed.
A repository directory will be created with a name derived from the
subversion URL.
The subversion URL must point to a subversion project with a standard
layout, with trunk, branches, and tags.
import optparse
parser = optparse.OptionParser(__doc__)
githelp=
Create a github repository. The argument is a string of the form
DEST/token. where DEST is either 'users/USERNAME' or 'orgs/ORGNAME' and
token is a github OAuth token:
https://help.github.com/articles/creating-an-oauth-token-for-command-line-use
curl must be installed if you use this.
parser.add_option('--github', '-g', help=githelp)
parser.add_option('--restart', '-r', action='store_true',
help=Restart after fetch times out)
parser.add_option(
'--authors', '-a',
help = 'Path to authors.txt file (required)')
import os
import sys
import xml.etree.ElementTree
def s(command):
print 'Running command:', command
if os.system(command):
raise SystemError
def r(command):
f = os.popen(command)
result = f.read()
f.close()
return result
def main(args=None):
if args is None:
args = sys.argv[1:]
options, args = parser.parse_args(args)
url, = args
if url.endswith('/'):
url = url[:-1]
name = url.rsplit('/', 1)[1]
if not options.restart:
os.mkdir(name)
os.chdir(name)
if not options.restart:
s('git svn init --no-metadata -s %s' % url)
assert options.authors
s('git config svn.authorsfile %s' % options.authors)
s('git svn fetch')
for tag in r('svn ls %s/tags' % url).strip().split():
if tag[-1] == '/':
tag = tag[:-1]
f = os.popen('svn log --xml -l1 %s/tags/%s' % (url, tag))
date = xml.etree.ElementTree.ElementTree(
file=f).find('logentry').find('date').text
f.close()
s(GIT_COMMITTER_DATE=%r git tag %r 'tags/%s' % (
date.replace('T', ' ').replace('Z', ' +'),
tag, tag,
))
for branch in r('svn ls %s/branches' % url).strip().split():
if branch[-1] == '/':
branch = branch[:-1]
s('git checkout %s' % branch)
s('git checkout -b %s' % branch)
# Not sure if this is necessary, or sufficient. The Ruby
# version ran into trouble when git left files around between
# branche checkouts. I haven't had the problem, with this
# script, which unlike the Ruby version, doesn't process
# deleted branches.
s('git reset --hard HEAD')
s('git checkout trunk')
s('git branch -D master')
s('git checkout -f -b master')
s('git branch -d -r trunk')
s('git gc')
if options.github:
github_dest, github_token = options.github.rsplit('/', 1)
if github_dest.startswith('users/'):
github_user = github_dest[6:]
github_dest = 'user'
else:
assert github_dest.startswith('orgs/')
github_user = github_dest.split('/')[1]
s('curl -v -XPOST -H Authorization: token %s'
' https://api.github.com/%s/repos -d '
'{name: '%s'}'
% (github_token, github_dest, name))
s('git remote add origin ssh://g...@github.com/%s/%s.git'
% (github_user, name))
s(git push -u origin '*' --tags)
if __name__ == '__main__':
main()
smime.p7s
Description: S/MIME cryptographic signature
Re: [Zope-dev] Status of github migration
On Jan 10, 2013, at 21:02, Matthew Wilkes matt...@matthewwilkes.co.uk wrote: When Plone did this the people involved wrote some scripts https://github.com/plone/svn-migrate That stuff works only partially. It uses a GitHub API that has been removed months ago. I migrated the Zope package based on that software and apparently there are issues with missing branches, too. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: persistent/trunk/ Prep 4.0.4 release.
On Dec 13, 2012, at 0:30 , Tres Seaver tsea...@palladion.com wrote: Getting distribution for 'persistent=4.0.0dev,4.1dev'. cc1.exe: error: unrecognized command line option '-mno-cygwin' error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occurred when trying to install persistent 4.0.4. Look above this message for any errors that were output by easy_install. While: Installing test. Getting distribution for 'persistent=4.0.0dev,4.1dev'. Error: Couldn't install: persistent 4.0.4 I don't know what the error message is about '-mno-cygwin'. From another project where I was forced to use Windoze I dimly remember that this issue arises when compiling any C extension with the installed Python. That -mno-cygwin flag is defined deep inside setuptools itself and clashes with newer versions of the compilation tools which don't know that flag anymore. I may have some of the details wrong, but this is *not* an issue with the persistent package requiring a special build setup. The issue is at the Python level and how setuptools interacts with the compiler when building C extensions. In that project I was successfully building extensions using Cygwin. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Foundation patch policy
Hi all, During the discussion about new ways to host and manage code in Zope Foundation repositories one omission we had never really addressed became clear: What is the status of patches reaching us by people who have not signed the contributor agreement, e.g. code uploaded to issue trackers, or code checked into Zope Foundation repositories by people other than the original authors? We need to have guidelines that ensure that we don't end up with code exclusively owned by third parties where no ownership assignment has taken place in our repositories. Fortunately the Plone Foundation has considered this exact issue before us and we took their well-written patch policy[1] and adapted it for our own use. Thanks to the Plone Foundation board and all those who drafted their policy. The Zope Foundation board has voted on adopting the following text as the official Zope Foundation patch policy, binding for all Zope Foundation contributors (PDF alert): http://foundation.zope.org/agreements/ZopeFoundation_Patch_Policy.pdf Jens Vagelpohl -- Jens Vagelpohl Secretary, Zope Foundation Board of Directors [1] http://plone.org/foundation/materials/foundation-resolutions/patch-policy-052011 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] We need to change how code ownership works.
On Aug 20, 2012, at 8:18 , Wolfgang Schnerring w...@gocept.com wrote: a) Using Github is found to be quite attractive by lots of people. b) We need to be diligent in maintaining the chain of custody of code so the copyright situation is kept clean. As far as I understand it, the legal lynchpin is that using Github (strongly) encourages merging code contributions of people that did not sign a contributor agreement -- which is the same situation as if someone attaches a patch file to a bug tracker ticket, but will be much more frequent and likely to happen. Could we, then, adopt a policy that we only merge pull requests (or whathaveyou) from people that have signed a contributor agreement? a) Tres, Jens: Would that work from a legal perspective? b) Ross, Alex: Would that still yield the advantages of the distributed source control model? Maintaining the chain of custody doesn't just consist of selecting pull requests or patches coming from somewhere. It also means verifying the contributor - be it the one who is creating the patch or pull request or the one who is merging new code into the repository - is who he claims to be. In the current setup the verification of the merging contributor is done using unique SSH logins with keys for every contributor, which works very well. By the way, there's no problem converting project repositories on an as-needed basis to Git repositories in the current infrastructure. But I feel the discussion is more about GitHub or nothing. Apologies to anyone who feels offended, I'm just speaking privately here under the impression that no one has mentioned any alternative solution. Moving away from any specific solution and speaking with my Zope Foundation hat on candidates must fulfil requirements like these (I don't claim completeness here, suggestions are welcome): - Read access for everyone including anonymous viewers - Write access for signed contributors only - Signed contributors must be able to create new repositories themselves (current analogy: A contributor adds a new project on svn.zope.org) - Good verification that a login to the chosen system represents a specific person/contributor (current example: access via unique SSH logins with keys) - Only ZF-appointed contributor admins may open access for contributors after receiving and verifying signed contributor agreements (currently Andreas Jung as officially appointed contributor committee member and Christian Theune as board member and contributor committee member handle this job) - Only ZF-appointed contributor admins (see above) may change or revoke access privileges for contributors - a reasonably convenient web view onto the repositories/projects for visitors and contributors - a reasonably convenient way (e.g. web admin capabilities) for the ZF contributor adminstration to do their job jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 19, 2012, at 0:01 , Alex Clark acl...@aclark.net wrote: Hi Jens, On 2012-08-18 07:49:59 +, Jens Vagelpohl said: Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! I think you are confused. I would suggest you ask Jim Fulton about it, as he moved Buildout to GitHub months ago. Both 1.6.x and 2.x are under active development there. Again, there's a confusion about perceived and legal ownership. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 19, 2012, at 3:58 , Alex Clark acl...@aclark.net wrote: IANAL but from my perspective the legitimate issue here is that Domen Kožar has not signed the Zope Contributor's Agreement, but Jim has added him to the Buildout organization on GitHub and he has been committing fixes. If I were the ZF, I would either: - Make sure everyone in any ZF organizations on GitHub (e.g. buildout) has signed the contributor agreement, or - Declare that nothing on GitHub (or at least in the buildout organization) is a valid contribution to the work. In either case, AFAICT zc.buildout development has stopped on svn.zope.org and started on GitHub so let us let the commit stand to reflect this real world circumstance. Right now it can only be the second option. There's no ZF organization on GitHub. Legally, the zc.buildout fork now existing on GitHub is independent of the ZF, and the developers maintaining it are acting independent of the ZF. Don't get me wrong, they have every right to do so. But right now they cannot claim their software as being part of the Zope Foundation set of software. The same is true for all packages forked onto GitHub that were maintained on svn.zope.org before. This may change in the future should the ZF one day embrace GitHub as the canonical repository, but that hasn't happened at this point. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 19, 2012, at 10:17 , Lennart Regebro rege...@gmail.com wrote: And since it becomes ever easier to accept code from unknown sources (e.g. pull requests) legal code ownership becomes an issue again. And that returns me to my first question: Is it really legally different for a contributor to accept a pull request from a non-contributor compared with a contributor merging a patch from a non-contributor? Legally, both are disallowed unless there's some proof (written statement etc) from the code author that he assigns ownership of the patch or the contents of that pull request to the contributor who is doing the checkin. In the past we haven't done a good job of enforcing this clear ownership assignment chain. There are always code patches from non-contributors in the bug tracker that may make it into the code base with the help of a contributor. There's a grey area: Is the act of submitting a patch into the Zope bug tracker enough to signal I am giving you ownership of this code? I am not sure. GitHub makes this pulling in of outside code even easier. I'm afraid it will become even harder to really maintain this chain of custody. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 19, 2012, at 10:55 , Robert Niederreiter r...@squarewave.at wrote: https://github.com/Pylons/pyramid/blob/master/CONTRIBUTORS.txt btw - pyramid seem to have a very pragmatic approach for the signing process ;) An approach I doubt will hold up in a court of law. We require and have wet signatures, which makes me feel a lot more on the safe side. Either way - SVN or GIT - it is just a question IF merging code from a non-contributor is done BY a contributor, not HOW. Done by a contributor with some clear gesture from the non-contributor that code ownership is going into the hands of that contributor. For me the discussion sounds a little like a general denial against github using the legal story as rationale. Speaking for myself as ZF representative, it is my duty to make sure that chain of custody for the code is upheld and safeguarded. Convenience, which I feel is driving the move towards GitHub, is nice to have. But I would not do my job if I didn't make extra-sure that any move for Zope Foundation code did not fulfil all legal requirements before spending much thought on convenience. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: A zc.buildout/README_MOVED_TO_GITHUB.txt D zc.buildout/trunk/ -=- Added: zc.buildout/README_MOVED_TO_GITHUB.txt === --- zc.buildout/README_MOVED_TO_GITHUB.txt(rev 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
Hi Hanno, Legally this must be a fork then and I'm not sure it can be released as official Zope Foundation software anymore if you make releases from GitHub. Reason: the ZF can no longer ascertain that only official ZF contributor agreement signers have modified code in the package, which is a core requirement for software released from Zope Foundation repositories/under Zope Foundation auspices. Apart from those legal points which are still not entirely clear, since this can only be a fork I would say that last checkin must still be reverted. Don't get me wrong, I'm not trying to be facetious, but until those legal questions are cleared up you should not make any checkins on svn.zope.org that basically shut down development of that package from there, such as deleting the trunk. jens On Aug 18, 2012, at 10:21 , Hanno Schlichting ha...@hannosch.eu wrote: Please note that development of buildout 2 happens on github since April this year. The buildout developers decided to do the move after Jim suggested it. Legally you could see this move as a fork, but it was done by Jim and others. Alex just wanted to clarify the situation and also move the development of the stable branch into the same place. Hanno On 18.08.2012, at 09:49, Jens Vagelpohl j...@dataflake.org wrote: Hi Alex, Please revert this checkin. You can't just take core software pieces from Zope Foundation-hosted repositories and move them somewhere else. Thanks! jens On Aug 18, 2012, at 3:09 , J. Alexander Clark cvs-ad...@zope.org wrote: Log message for revision 127519: Moved to github Changed: A zc.buildout/README_MOVED_TO_GITHUB.txt D zc.buildout/trunk/ -=- Added: zc.buildout/README_MOVED_TO_GITHUB.txt === --- zc.buildout/README_MOVED_TO_GITHUB.txt(rev 0) +++ zc.buildout/README_MOVED_TO_GITHUB.txt2012-08-18 01:09:06 UTC (rev 127519) @@ -0,0 +1 @@ +https://github.com/buildout/buildout/tree/1.6.x ___ checkins mailing list check...@zope.org https://mail.zope.org/mailman/listinfo/checkins ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 12:46 , Wichert Akkerman wich...@wiggy.net wrote: On 2012-8-18 10:39, Jens Vagelpohl wrote: Hi Hanno, Legally this must be a fork then and I'm not sure it can be released as official Zope Foundation software anymore if you make releases from GitHub. Doesn't the name zc.buildout imply that it is a Zope Corp project instead of a Zope Foundation one? The author has also never been listed as the foundation but Jim personally, which seems to imply zc.buildout never was Zope Foundation-owned software. Hi Wichert, Clearly, Jim is the father of that software and it has been developed in large part for Zope Corporation, hence the name zc.buildout. However, that's not all there is to ownership of code on svn.zope.org. If you read the contributor agreements[1] all committers to svn.zope.org signed, submitting code to svn.zope.org also meant you entered into a legal agreement with the Zope Foundation regarding that code. Code submitted to svn.zope.org is from that moment on half-owned by the Zope Foundation. That means you cannot unilaterally just declare code removed from svn.zope.org, which is my point about the last checkin to the zc.buildout package. Everyone is free to fork code. But removing stuff from svn.zope.org requires approval from you as the original owner *and* the ZF as legal co-owner of anything stored on svn.zope.org. Caveat: I'm not a lawyer, that's just how I interpret the contributor agreement. jens [1] http://foundation.zope.org/agreements/ZopeFoundation_Committer_Agreement ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 14:31 , Jean-Paul Smets j...@nexedi.com wrote: Hi, I approve your position Jens. Moving to git can make sense. Moving to github as primary platform does not make sense. Hi Jean-Paul, Technical pros and cons are valid arguments, correct, but that wasn't my point here. I'm trying to look at the contractual issues involved, that's all. I'm not saying only platform X is acceptable, just that right now I only have proof that our self-hosted Subversion repositories on svn.zope.org appear to meet all the legal requirements laid out by the contributor agreements and the role of the Zope Foundation as the guard of these contributions as well as contributors' private data held by the Zope Foundation. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zc.buildout/ Moved to github
On Aug 18, 2012, at 15:46 , Lennart Regebro rege...@gmail.com wrote: On Sat, Aug 18, 2012 at 10:39 AM, Jens Vagelpohl j...@dataflake.org wrote: Legally this must be a fork then and I'm not sure it can be released as official Zope Foundation software anymore if you make releases from GitHub. Reason: the ZF can no longer ascertain that only official ZF contributor agreement signers have modified code in the package, which is a core requirement for software released from Zope Foundation repositories/under Zope Foundation auspices. Is this because of the support for merging pull requests? Is that really legally different than a contributor making a merge from a patch? Hi Lennart, The contributor agreement requires you as the contributor to be able to enter into the contract with the Zope Foundation transferring one half ownership to the Zope Foundation. You can only enter into this contract if you own (as in wrote) the code yourself - you cannot assign ownership to someone else for something you don't fully own. The goal of these contractual requirements is to make sure software stored in the Zope Foundation is as clean as possible from an ownership standpoint. People who use code from svn.zope.org have a reasonable assurance that no third party will show up on your doorstep demanding money or license fees for code that third party claims to own. I've just recently seen what can happen for projects not following this kind of strict policy: The python-ldap package developers are unable to e.g. assign a new license to their code because since they don't hold any ownership and would need to ask every single developer who ever touched that code - an impossible task. For us that kind of issue does not arise. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 release management
On Feb 1, 2012, at 00:05 , Alex Clark wrote: Bottom line: Zope stands to benefit greatly if the current active developers keep an open mind about how/where/when development of Zope software should occur. There are plenty of people that still think Zope software is cool, and plenty of skilled developers on github that could potentially help move it forward. This discussion seems to unnecessarily combine at least two distinct issues: - what RCS software to use - where to host it It may be easier if we disentangled them. Speaking purely as a developer, I'm leaning to Git when it comes to the RCS software decision between Subversion and Git. But I can use both equally well. Where it is hosted, well, purely as a developer it doesn't matter to me, unless I need to give up too much personal data to get access. From the perspective as a Zope Foundation member the RCS software decision is a technical detail that doesn't matter much. I'm more concerned with the where question, though. The Zope Foundation is tasked with safeguarding the software released under the Zope Foundation umbrella, and it is tasked with enforcing the contributor agreements everyone signed. Commits can only be made by signed contributors, and contributors are specifically disallowed to take outside code they don't own and commit it to the repository. We already have the technical infrastructure in place for most of this, such as ZF-controlled logins on svn.zope.org, access only via SSH key, etc. Our current where can be fully trusted, so to speak, and the people tasked with maintaining this infrastructure are known, accountable, and part of the foundation. My third role is secretary of the Zope Foundation Board of Directors and in that role I collect and maintain contributor applications and the (private) data associated with it. I can vouch that our current means of storing this data is reasonably secure. I can't make that assertion if the data is stored somewhere out of Zope Foundation control. My last role is admin for the ZF infrastructure and servers. In that role I would be involved in executing any changes in repository hosting. If only the RCS software changes that's a chunk of work, but doable. Git service can be added to the ZF infrastructure and packages can be migrated into Git repositories, probably on a as-needed basis. Most of the current authentication and safety infrastructure could stay in place. On balance and taking all my roles into account, sticking with SVN and the current hosting is the most attractive option. Moving to Git in the current hosting environment is doable, it means work, but I feel I've done my job keeping the software, access to it, and contributor data as secure as possible. Any option that involves moving to a different host altogether not only makes me feel I haven't done my job, it may also throw up legal questions. jens signature.asc Description: Message signed with OpenPGP using GPGMail ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 release management
On Feb 1, 2012, at 15:53 , Charlie Clark wrote: Currently the hurdle to getting involved is signing and sending the committer agreement. A hurdle which I think is worth keeping. For any code released under the Zope Foundation umbrella that hurdle cannot be removed, anyway. To be frank, I don't even think that's a hurdle. And it helps to remind the signer that there are legal requirements and responsibilities involved. jens signature.asc Description: Message signed with OpenPGP using GPGMail ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 release management
Hi Chris, For what it's worth, in the Pylons Project, we decided to continue requiring the signing of a contributor's agreement (more or less the same contributor agreement as Zope requires). But instead of signing via paper, we ask that folks sign the contributor agreement by adding their name and date to a CONTRIBUTORS.txt file in a git fork of each repository they wish to commit to (e.g. https://github.com/Pylons/pyramid/blob/master/CONTRIBUTORS.txt). The CONTRIBUTORS.txt *is* the agreement, and the pull request serves as proof that they agree to the contribution terms it outlines. I'm not 100% confident that this will serve as watertight proof of agreement in a well-funded court challenge. But it's a lot easier on the contributor and on the organization. The contributor doesn't need to use a fax or lick a stamp and wait, and at least if they're checked in they're fairly durable and have lots of backups (it would be very impressive if the ZF would be able to produce all the paper contributor agreements that have been signed over the course of Zope's existence on demand). Yes, I remember signing the Repoze repository agreement in a similar way a few years ago. I liked it because it was convenient, sure. But as you say, I doubt it would hold up in a court. Speaking of those paper contributor agreement availability, you'd be surprised. I have them all in 3 large binders, for every signer the latest agreement they signed. jens signature.asc Description: Message signed with OpenPGP using GPGMail ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2 WSGI investigation
On Jan 3, 2012, at 09:34 , Sylvain Viollon wrote: We use Paster as well in the stack, and use it to configure the Python logging process, you can configure there a logging to syslog, and after having a central syslog server. I think it is more professional like this, than using a tool in Zope's UI. Logging to syslog usually leads to problems due to the maximum message size for syslog entries. Error log messages with a traceback tend to be cut off and information lost. I'm not saying a ZMI tool is ideal, but syslog has pitfalls. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope internals documentation
Hi Martin, Sphinx on svn.zope.org works for me. :) I have created a simple buildout and put it in SVN: http://svn.zope.org/zope_secrets/ The output is shown at http://docs.zope.org/zope_secrets/ and linked from the front page at http://docs.zope.org/. Every 6 hours, a cron job looks to see if the SVN revision has changed and if it has then the output is regenerated. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope internals documentation
On Dec 31, 2011, at 20:09 , Martin Aspeli wrote: Hi folks, I have documented some of the darker corners of Zope's internals. I put it in the Plone developer documentation for lack of a better place, but it's not Plone-specific: http://collective-docs.readthedocs.org/en/latest/zope_secrets/index.html Hi Martin, There *is* a better place, docs.zope.org. If you can tell me where the sources are I can put it there. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope internals documentation
Hi Martin, There *is* a better place, docs.zope.org. If you can tell me where the sources are I can put it there. Sure: Clone https://github.com/collective/collective.developermanual/ and get it from source/zope_secrets. Thanks, I'll take a look at it today. Where is docs.zope.org maintained? On one of the ZF servers. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope internals documentation
On Jan 1, 2012, at 11:46 , Martin Aspeli wrote: Where is docs.zope.org maintained? On one of the ZF servers. If it's going to go there, I'd like it to (a) be in version control and (b) be somewhere that I can edit it. Is that doable? That's how we do it with almost everything underneath the docs.zope.org hostname. The sources are on svn.zope.org are are pulled/built regularly. Where the source comes from doesn't really matter. The only requirement is that it should be a scriptable buildout process, like a buildout/Sphinx setup. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Mailing lists moved
Hi all, I moved all mailing lists to a newer server this weekend. If anyone is noticing any problems please talk to me off-list. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 4 publisher/traversal, sprint topic
On Oct 27, 2011, at 16:07 , Lennart Regebro wrote: Do we really have to call it Zope 4? :-) Yes. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Conversion old.zope.org to static site
Hi Tom, Further I have noticed two things: 1) Some pages are not recognized correctly and trigger a download (on Firefox) or show the source code (on IE): http://old.zope.org/Members/pje/Wikis/ZPatterns/HowTriggersWork.1 2) For some locations the folder contents are shown instead of the default page: http://old.zope.org/DevHome/CVS/ZopeCVSFAQ Those two are now fixed. Thanks for the heads-up! If you see anything else just drop me a note. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Getting back to green
On Oct 17, 2011, at 16:08 , Tres Seaver wrote:
I would like to propose that we quit reporting test failures for the
unmaintained packages ('zc3.*', for a start. If somebody really
thinks there is value in such testing, we could perhaps run those
tests only weekly (like the others which have expected failures).
+1
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Conversion old.zope.org to static site
Hi all, Just as a heads-up: Jim Fulton and I have converted old.zope.org to a static website. This allows ZC to decommission the hardware and reduces the maintenance burden for everyone involved. We have tried to keep all URLs intact and the site navigation working at the same time, which required a little creative thinking. Some of you rely on resources from the old.zope.org site, such as release tarballs of older Zope versions and other products. Please test and ensure the files you need are still where you expect them. If you have problems, just contact me off-list and I'll take a look. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Missing Zope2 tarballs
On Oct 11, 2011, at 03:33 , Alex Clark wrote: Hi, Anyone notice these missing tarballs? - http://old.zope.org/Products/Zope/2.9.12/Zope-2.9.12-final.tgz/ - http://old.zope.org/Products/Zope/2.10.13/Zope-2.10.13-final.tgz/ - http://old.zope.org/Products/Zope/2.11.4/Zope-2.11.4-final.tgz/ Hi Alex, With the help of Jim, who produced a tarball containing the spidered content of old.zope.org, the site has been converted to a static site. There will inevitably be issues here and there. I'll take a look to see if I can find the original files from the old app server. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Missing Zope2 tarballs
On Oct 11, 2011, at 17:14 , Alex Clark wrote:
On 10/11/11 3:17 AM, Jens Vagelpohl wrote:
With the help of Jim, who produced a tarball containing the spidered content
of old.zope.org, the site has been converted to a static site. There will
inevitably be issues here and there. I'll take a look to see if I can find
the original files from the old app server.
Thanks Jens, I know I occasionally need to build old Plone sites, as far
back as 2.1 but also sometimes 2.5.x and 3.{0,1,2}.x all of which use
the old tarballs ranging from Zope 2.8 - 2.11 (I think). Building these
sites will require at least the final from each series to continue
working. Ultimately, I'd love to be able to access all the old tarballs
e.g. similar to:
- http://dist.plone.org/archive/
But I realize this may require some significant bit of effort!
I'm in touch with Jim to find some solution.
jens
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On 7/6/11 13:41 , Martijn Faassen wrote: Concerning not marketing Zope 2, heh, Zope and marketing strategies? I thought we were going to call Zope 2, Zope now, so people will obviously be curious about this Zope thing... Never make any assumptions about a coherent Zope marketing strategy! I'll also drop in a reference to the existence of zope2.zope.org. I totally agree. Now would be a good moment to make it all a little better by dropping the name Zope 2 in favor of Zope. And I sincerely hope that zope2.zope.org will go away and its content end up on the new www.zope.org site. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] direction
On 7/5/11 11:56 , Martin Aspeli wrote: On 5 July 2011 10:31, Hanno Schlichtingha...@hannosch.eu wrote: So we just got ourselves a Zope2 version 3.0. And no, naming it 4.0 or 5.0 or anything else doesn't make it any better at all. So 3.0 is the most sensible one :) Boy, that's going to be confusing. :) I'd actually favour calling it Zope2 4.0 just to avoid any mix-up with the defunct Zope 3, although I don't think there are any particularly good options here. I actually think it's a brilliant idea to skip 3.0 and call it 4.0. As Martin said, the potential for confusion is very high. A 4.0 would not only steer around confusing Zope3 3.x and Zope2 3.x, it would also make it easier to move back to the simple Zope moniker without any qualifying number tacked on. People who only look at version numbers would now choose Zope 4.0 instead of falling into the unmaintained Zope3 trap. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] versions on zope.org and launchpad.net
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/29/11 08:51 , Wichert Akkerman wrote: My question would be: why launchpad? Is anyone expecting launchpad to be a canonical resource for Zope releases? As far as I know none of our documentation refers to launchpad for downloads and launchpad has never been used for anything other than it's bugtracker. I would agree that it would be nice to have a single location that lists historic releases, I would expect that to be on zope.org instead of launchpad or some other random third party website. I kept wondering why Launchpad even came up for Zope2 download resources. I don't recall a discussion where that was decided. PyPI and zope.org are still the canonical locations. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk4K0rcACgkQRAx5nvEhZLLQNQCgs9fEiTTgxcYRplJ7Gv5054X7 f64AoJk9WX/mksfR6GR3hBjG3epgGTCh =W1wc -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] versions on zope.org and launchpad.net
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/29/11 10:20 , Andreas Jung wrote: Jens Vagelpohl wrote: I kept wondering why Launchpad even came up for Zope2 download resources. I don't recall a discussion where that was decided. PyPI and zope.org are still the canonical locations. Actually PyPI is the only canonical location for the eggified releases of Zope2. Even better to have just one. The only use case that's not obviously covered is an up-to-date list of old releases. zope2.zope.org appears to advertise itself as that place (see http://zope2.zope.org/releases). jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk4K4YcACgkQRAx5nvEhZLKlGQCfaJ+I/SgKTQS06s3UWxVtyqWu PH0AnjDks9bRYb6GISq36XkzQacnEykZ =BS2C -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] versions on zope.org and launchpad.net
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/29/11 10:34 , Hanno Schlichting wrote: On Wed, Jun 29, 2011 at 8:51 AM, Wichert Akkerman wich...@wiggy.net wrote: My question would be: why launchpad? Is anyone expecting launchpad to be a canonical resource for Zope releases? As far as I know none of our documentation refers to launchpad for downloads and launchpad has never been used for anything other than it's bugtracker. We did upload all non-egg Zope2 releases to https://launchpad.net/zope2/+download but not the latest ones. That's a bit confusing. Either we remove the downloads from launchpad or we make sure it has all of the old ones. +1 for removing. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk4K6M8ACgkQRAx5nvEhZLLShACeOmY5WCssNFfUZLJiY6Z5hcad RgIAnRzUB2gJHz9bsrhnU48HqORyEZr0 =TzeY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] beta.zope.org (www.zope.org relaunch project)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/10/11 07:28 , Alex Clark wrote: - Zope is: a brand, a term for any Zope-related technology, a general term. It no longer refers to anything specific. It is all-encompassing. - Zope 2 is the original web application server. - Bluebream is the former-Zope 3 web application server. - ZTK is a set of re-usable libraries. I strongly disagree on the term Zope 2. Now is a great time to finally stop the Zope2/3 confusion: Kill that name and start using a more sensible name, such as the Zope application server. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk3I5hIACgkQRAx5nvEhZLIoswCfTAMMjJ3gfrExco99Zd/ZfhHG W0UAn35Ku/331M8NZibsLCshpClU3yXi =VWVk -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] beta.zope.org (www.zope.org relaunch project)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/10/11 11:52 , Martijn Faassen wrote: I'd call 'Application servers', which is mostly a term from Java land, web frameworks instead, because that's what Python developers will understand, and put Zope, BlueBream and Grok under it. If it sorts alphabetically (frameworks seems to do so) and Grok comes first, I don't mind. :) +1 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk3JDAcACgkQRAx5nvEhZLIORgCeMr+07DjVmyq8NLE1F/2RDf2K NgsAn1QqUN+mOovB6Y4P8Gi84WlXv4K8 =dq4s -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] beta.zope.org (www.zope.org relaunch project)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/10/11 22:31 , Chris Withers wrote: Hi All, I found a link off the new site (which looks great, btw) to: http://zodb.zope.org/ ...but this name doesn't resolve for me, does it for other people? The link is incorrect. It should point to www.zodb.org. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk3JrsUACgkQRAx5nvEhZLJbTQCePia6zUQjMyizDo6ax36axK/n u0sAoLWrk5mMGicKPyhC2BnbzgK4SUyz =hCFv -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] beta.zope.org (www.zope.org relaunch project)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/11/11 02:04 , Alex Clark wrote: Hi, On 5/10/11 5:38 AM, Lennart Regebro wrote: On Tue, May 10, 2011 at 09:15, Jens Vagelpohlj...@dataflake.org wrote: I strongly disagree on the term Zope 2. Now is a great time to finally stop the Zope2/3 confusion: Kill that name and start using a more sensible name, such as the Zope application server. Right. However I'm not convinced this is something you can agree/disagree on. Zope 2 exists. Zope 3 does not (it was split apart and renamed). As such, I don't see a problem with referring to it (Zope 2) by name (it's not Voldemort, after all). Someday it will die; but that day is not today. And until that day comes (or it gets renamed, heaven forbid) I would strive for clear and consistent branding (and in this case, I think I would also try to make it clear that Zope 2 is legacy software). Zope 2 was never a brand. It only existed to have a name for the older application server when Zope 3 existed. It led to confusion and still does. The name must go away. It is now the only application server with the Zope name left, and that's a simple, clear and consistent brand. We can help make the Zope 2 name go away by stopping its use on official community sites like the new zope.org. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk3KJIkACgkQRAx5nvEhZLKBOACffi+SkGRq9/3Ars6S4XzJmRV7 tzUAnii+Et4rAsqUcUHRVO8k3WDne3EE =Shk6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Repository cleanup: ZVSL licensed files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2tPCgACgkQRAx5nvEhZLL8YgCgus5vn8TGP8NG4of72QgNd3w2 mrUAnjlhNmoWrGhGVTC14GVffvoVt53p =R0Sq -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Repository cleanup: ZVSL licensed files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 15:19 , Jim Fulton wrote: On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/19/11 08:52 , Michael Howitz wrote: Hello, while making projects in SVN complying to the repository policy I found files which tell that their license is Zope Visible Source License, Version 1.0 (ZVSL). Is this license a valid license in the zope.org repository? If not I'd like to merge the following change in zope.repositorypolicy: http://svn.zope.org/?rev=121436view=rev +1 The ZVSL is a Zope Corporation-specific license that does not meet the requirements for projects hosted by the Zope Foundation. I am surprised you found any files with that license. Those should be in Zope Corporation-owned repositories, or they should be relicensed if ZC agrees. Sorry our (probably my) bad. Those should have been fixed when we moved them from our repo to the zope.org repo. Does the patch fix the files? Or just list them? Hi Jim, It just lists them as part of the weekly repository policy check that flows into the automated test summary email. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2tjN0ACgkQRAx5nvEhZLJmKACfY6GV0XHrlNFvalMlE5qHB7uq MkwAoISBeGWkwOHW4K9CqZDM4tIy5vD0 =yFXe -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New test summarizer format
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/3/11 12:41 , Jens Vagelpohl wrote: On 3/29/11 11:15 , Adam GROSZER wrote: But it seems like it's about bugging Stephan Holek to stop the current one and bugging Jens to start the new one, or? Unless the script is broken. Could you run that script -- worst case we'll have 2 mails for a day -- for testing? Seems like it has the settings for gocept and I don't really have an SMTP server here handy. Thanks to Wolfgang's cleanup work the new script is now in place. It's running once a day at 01:00 AM Eastern Standard Time. @Wolfgang: Something is not working as seen in today's run. If I run the script with -T 2011-04-02 I am getting correct output. But if I run it with -T 2011-04-03 or -T 2011-04-04 I am getting nothing. Can you test this in your sandbox? Thanks! jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2ZZxYACgkQRAx5nvEhZLL7aQCgo6h5CtRLQQeWXrLh7zzILb5F BY0AoLLCmHIyJVVflYNih+s7uEF+wMSo =Bm4U -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New test summarizer format
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/4/11 08:37 , Jens Vagelpohl wrote: On 4/3/11 12:41 , Jens Vagelpohl wrote: On 3/29/11 11:15 , Adam GROSZER wrote: But it seems like it's about bugging Stephan Holek to stop the current one and bugging Jens to start the new one, or? Unless the script is broken. Could you run that script -- worst case we'll have 2 mails for a day -- for testing? Seems like it has the settings for gocept and I don't really have an SMTP server here handy. Thanks to Wolfgang's cleanup work the new script is now in place. It's running once a day at 01:00 AM Eastern Standard Time. @Wolfgang: Something is not working as seen in today's run. If I run the script with -T 2011-04-02 I am getting correct output. But if I run it with -T 2011-04-03 or -T 2011-04-04 I am getting nothing. Can you test this in your sandbox? @Wolfgang: I have checked in some fixes and it works for me now. We'll see the results tomorrow. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2Zvn0ACgkQRAx5nvEhZLI62ACdHgr8dvtV0K0esDkpHxYiy1Qv 5u8AnjqXOdmtmk0+/TbojuQ6uUJwK1Ln =2Rbj -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New test summarizer format
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/29/11 11:15 , Adam GROSZER wrote: But it seems like it's about bugging Stephan Holek to stop the current one and bugging Jens to start the new one, or? Unless the script is broken. Could you run that script -- worst case we'll have 2 mails for a day -- for testing? Seems like it has the settings for gocept and I don't really have an SMTP server here handy. Thanks to Wolfgang's cleanup work the new script is now in place. It's running once a day at 01:00 AM Eastern Standard Time. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAk2YTtAACgkQRAx5nvEhZLJZtACglWfBgjJRhd3r7iIuU7vb09Pf ybYAnjKBhYpGnapLjiotUHTsJIxNLcGT =bE8F -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Draft of new aggregator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/10 08:59 , Wichert Akkerman wrote: On 2010-12-1 07:43, Christian Theune wrote: Here's the draft we ended up with yesterday: http://dpaste.com/281566/ Can you move the non-OK results above the list of reports received? That way you have the most important information first. - -1 on moving. Maybe the non-OK entries could be copied into an additional section at the top instead. If I understood Christian right he wants to keep the full list of entries sorted so everyone knows where to find their items of interest quickly. I think that's valuable, the full list should stay as it is. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkz2AaIACgkQRAx5nvEhZLLlWQCfYe170tCqd2V8t1FIzfshy62Z 0e4AoIHHCd+UFaOvbfFkmOnLNn4zVAcf =kEXo -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Draft of new aggregator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/10 09:28 , Wichert Akkerman wrote: On 12/1/10 09:04 , Jens Vagelpohl wrote: On 12/1/10 08:59 , Wichert Akkerman wrote: On 2010-12-1 07:43, Christian Theune wrote: Here's the draft we ended up with yesterday: http://dpaste.com/281566/ Can you move the non-OK results above the list of reports received? That way you have the most important information first. - -1 on moving. Maybe the non-OK entries could be copied into an additional section at the top instead. If I understood Christian right he wants to keep the full list of entries sorted so everyone knows where to find their items of interest quickly. I think that's valuable, the full list should stay as it is. It does mean that you always have to scroll down 3 pages before you see anything important. No it does not. I said Maybe the non-OK entries could be copied into an additional section at the top instead. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkz2DKAACgkQRAx5nvEhZLLNoQCdE1EM0G603TRYCOfsRXHlIvRX E/EAn2H4WSQt+1B8iJq4s+SrXm8h/U// =6zF7 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Draft of new aggregator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/30/10 16:06 , Christian Theune wrote: Hi, here's a shot at a new format of the aggregated mails. My focus on this draft was: - allow dealing with *lots* of results every day more easily - allow having a graphical overview of how broken something is (group builders by prefix) - have a stable sorting so you can quickly pin-point whether something that you're interested in is broken - reduce the noise Looks good to me, much better than what we have now. I'm guessing the URLs will be fixed to point to http://mail.zope.org... instead of file:///tmp/mail.zope.org..., right? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkz1LqsACgkQRAx5nvEhZLKtsACgjwcVfPvgDqr9UNAwFsnQhkls RdMAn2PEw7gtWKcOdIuS+kQi712CSmwh =zxEc -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Draft of new aggregator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/10 07:43 , Christian Theune wrote: On 11/30/2010 06:04 PM, Jens Vagelpohl wrote: Looks good to me, much better than what we have now. I'm guessing the URLs will be fixed to point to http://mail.zope.org... instead of file:///tmp/mail.zope.org..., right? Yeah. I just mirrored the data to my local machine to get faster results ... Here's the draft we ended up with yesterday: http://dpaste.com/281566/ Even better :-) jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkz18JQACgkQRAx5nvEhZLJ4wQCgsWLEdsCgeaQtJiQl3+5q4OIB f7EAnA5+YkD5WIFIIYR7fDmKmrP7bonD =S/pf -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.13 - release candidate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/10 12:29 , Hanno Schlichting wrote: - zopectl start - doen't work (https://bugs.launchpad.net/zope2/+bug/628448) - Zope2 egg is not available in index (https://bugs.launchpad.net/zope2/+bug/653546) Both of these have been resolved now. The index problem is waiting for a Apache config reload on download.zope.org. I reloaded it. What did you change? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkzJX0QACgkQRAx5nvEhZLLjjwCgvA1kghLJ3kGLa/DDh/VWfIj1 qLUAoLVXPDQQYPg3tRoe4pZPyqVZ/QtF =QM3r -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/6/10 18:33 , Tres Seaver wrote: +1 for dropping the test: if we aren't going to try to fix it to pass, then scrap it. Note that I actually feel the same way about *all* the every-day failures: the value of the every-day mail drops sharply when there are any expected failures. For me personally the value has dropped so far that I am mostly ignoring those emails. They are hard to parse to begin with and there are just too many buildbot entries. I wonder if it would make sense to send separate emails per software package (such as ZTK, Zope2, etc) so that people can pick and choose. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkytbjkACgkQRAx5nvEhZLJ+2wCcCo19KDbb0gWvz6L4K0ggilIg zvAAoISUrp6R9dhMn5S3aTXdb2j3GXjc =VG5q -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Buildbot status on http://docs.zope.org/zopetoolkit/process/buildbots.html
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/30/10 21:16 , Marius Gedminas wrote: On Thu, Sep 30, 2010 at 03:04:09PM +0200, Jens Vagelpohl wrote: On 9/30/10 14:37 , Marius Gedminas wrote: Can someone with admin access add a daily cron script to cd /path/to/ztk/doc/sources touch source/process/buildbots.rst make html ? Without the 'touch' step Sphinx will decide the content hasn't changed and won't update buildbot status. I've added the extra step. Normally updates only happen if the source code for those Sphinx docs has changed in SVN. That's why I asked for a new daily cron script, rather than a modification of the post-update hook. I'm now a bit confused if you did the former or the latter? I added it to the daily cron script. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkylfjsACgkQRAx5nvEhZLLOXgCdGlodYigw9nXVuaLflkPKsAc8 M9UAnif8p+CPhAL0EUekX8DqUn7cALjg =gRZx -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/1/10 10:22 , Charlie Clark wrote: Hi, I'll admit to spending most of my time on new CMF stuff but I did close two bugs that I felt comfortable with. Didn't seem anyone else was hanging around on IRC with bugfixing on their mind. I never made it, busy with other stuff all day :-( jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkylobkACgkQRAx5nvEhZLKuCQCdH/n2vb9Wh58nFhZoEp3ARECB 268An0pOOifWDxJbIBZgnwnluTFRdjD1 =oiQC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Buildbot status on http://docs.zope.org/zopetoolkit/process/buildbots.html
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/30/10 14:37 , Marius Gedminas wrote: http://docs.zope.org/zopetoolkit/process/buildbots.html shows a very neatly organized overview of the status of various buildbots. There's only one problem: the content is outdated (Last updated on Sep 17, 2010). Can someone with admin access add a daily cron script to cd /path/to/ztk/doc/sources touch source/process/buildbots.rst make html ? Without the 'touch' step Sphinx will decide the content hasn't changed and won't update buildbot status. I've added the extra step. Normally updates only happen if the source code for those Sphinx docs has changed in SVN. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkykiskACgkQRAx5nvEhZLLH2ACgsWH7tUzVZdSUhKd5g97VOoqu HOIAn0/pDTwOPo625HeqwU0e3kV8rGng =plEu -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Bug day reports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I worked on the following bugs: Already fixed = https://bugs.launchpad.net/products.zsqlmethods/+bug/440993 Fixed = https://bugs.launchpad.net/products.zsqlmethods/+bug/142689 https://bugs.launchpad.net/products.zsqlmethods/+bug/142501 https://bugs.launchpad.net/zope2/+bug/193122 Moved = https://bugs.launchpad.net/products.zsqlmethods/+bug/210398 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkx0y68ACgkQRAx5nvEhZLIhHACglzETKAdzldsyPK599zEnr1PK ZBUAoKNq1G+M2fCp4u3lnxKtquoNmNQZ =fQdS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Don't get ZODB 3.10 by installing Zope2.13
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/25/10 21:32 , Vladislav Vorobiev wrote: ps: my normal email for this mailings list is **mymir@gmail.com**. I subscribe the list and get emails but I can't send anything. No mail from mymir@gmail.com was accept http://www.dict.cc/englisch-deutsch/accept.html. Please fix it if posible. The reason is very simple: You are subscribed as mymir@gmail.com. However, I see several log entries where the from address is mymir@googlemail.com. The sender address is not accepted, since no one is subscribed with the address mymir@googlemail.com. This is something you need to fix. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkx1khwACgkQRAx5nvEhZLIMAACgnS8FcpP3jFfA5mE5ifjy0enr sxAAn1UrT7GNB9PpBfAYVZMANK+SNj4x =GI9j -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] (Zope2) a proposed tweak to assigning default roles to permissions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/19/10 09:46 , Hanno Schlichting wrote: Can roles currently contain whitespace? Like Awesome People? If so, we should go for nested nodes: permission id=my.NewPermission title=My new permission roleManager/role roleSiteAdmin/role roleAwesome People/role /permission I think this matches the style of some of the GenericSetup handlers which deal with permissions. +1 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxs8PoACgkQRAx5nvEhZLIG8ACePKMag3XuAGaf/JLhm8JOeu/I uzQAn3oE3Ft/Ayp+zi3Wl5kQ2I0p78Q4 =qJx6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retire zope3-checkins list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/9/10 08:58 , Baiju M wrote: On Thu, Apr 8, 2010 at 8:39 PM, Baiju M mba...@zeomega.com wrote: Hi, What about retiring zope3-checkins list ? I send this sometimes back. What needs to be done to retire this list ? I think there are few post-commit hooks in svn for Zope3,zope.testing, zope.formlib and may be few others. Just FYI, he following packages from the svn.zope.org repository send mail to zope3-checkins during the post-commit step: - Zope3 - zope.testing - zope.formlib - ldapauth - messageboard - zdaemon I can remove those hooks if so desired. No mail gets lost, all checkins also send email to the general checkins list[1]. jens [1] https://mail.zope.org/mailman/listinfo/checkins -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxfqXoACgkQRAx5nvEhZLKLfgCgmjlm/bAZiIEffyinYvoiAo4b nMwAn0LXE9c/I+G4Mc+0q8PMALx5JMz4 =GZ4c -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/5/10 00:16 , Willi Langenberger wrote: According to Jens Vagelpohl: before=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) svn up -q $ROOT after=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4) I think svn info $ROOT doesnt give you the newest revision somewhere down the directory tree. You have to use something like svn info -R $ROOT | grep ^Last Changed Rev:| cut -d -f 4 | \ sort -k1n,1 | tail -1 (note the -R flag for the svn info command). Thanks Willi, I'll give that a try when I have a moment. I wouldn't be surprised if that was the case. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxaW6gACgkQRAx5nvEhZLLmxACeLNo3ssUdKOHFRlQpYmnpuI2I B1IAn3Q0aAEqrIB++OtiJCrXf6Ew8meA =anjj -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Chris, I've just been doing some build and release tools for a customer that involve this sort of stuff, I resorted to: snip lots of code Yikes. Maybe the subshell isn't so bad after all :-P jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxZKkQACgkQRAx5nvEhZLKQWACgmwW7mgXSQdj4W64aMXXq/PY9 Z2wAoKHgZs6uYAdvDdoR9MzcegrOm6er =EbE3 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Products in Zope 2.12+
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/4/10 10:52 , Hanno Schlichting wrote: Hi. On Wed, Aug 4, 2010 at 10:31 AM, Chris Withers ch...@simplistix.co.uk wrote: I'm in the process of egg-ifying some Zope 2 Products of mine (first up is MailTemplates) and I'm curious as to how add-in products work in an egg-based Zope setup. Do I need to include anything in zope.conf or some zcml somewhere? If your package is a namespace package in the 'Products' namespace, then it will be picked up automatically, once added to the PYTHONPATH. In essence: If your egg is in the Products namespace you don't need to do anything after adding it e.g. to the list of eggs for a Zope instance in your buildout.cfg. The product will be recognized, installed, and any configure.zcml in the root picked up automatically. That's one reason I stick to that namespace for anything that is indeed a Zope 2 Product. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxZKzQACgkQRAx5nvEhZLK7TgCeI2n6Y+xjagXyPZHeNuEII2V3 xMUAoIJHoErxjlAjZRWYPME8tEPM1S2O =IYFz -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/4/10 11:33 , Chris Withers wrote: Jens Vagelpohl wrote: I've just been doing some build and release tools for a customer that involve this sort of stuff, I resorted to: snip lots of code Yikes. Maybe the subshell isn't so bad after all :-P Yeah ;-) Although getting the right python path set up can be a pain... In my particular case that's not a problem. I simply re-use sys.path from the running interpreter, which is good enough. Something like this: cmd = 'PYTHONPATH=%s %s setup.py --long-description' % ( sys.executable, ':'.join(sys.path)) status, output = commands.getstatusoutput(cmd) jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxZNUcACgkQRAx5nvEhZLKNtwCgqgZcNkJWZlS+qMkn8Ra9brnZ gcgAnjnA/KaraIL93Ue+CvPlVzxwYs10 =ykyG -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 14:55 , Marius Gedminas wrote:
On Wed, Aug 04, 2010 at 11:09:58AM +0200, Jens Vagelpohl wrote:
On 8/4/10 10:57 , Adam GROSZER wrote:
Hello Jens,
Something is wrong with the automatic update of
http://docs.zope.org/zopetoolkit/
Recent changes don't seem to show up.
I rebuilt it now. There's a check in a shell script to see if the
Subversion code is newer than the checked-out code, but it doesn't seem
to be reliable. I'll have to watch it.
If someone could code up something more reliable I'd be very happy.
Can we see the shell script somewhere?
The script (see below) sits at the root of the documentation buildout
(such as the buildout at http://svn.zope.org/zopetoolkit/), which
precreates the necessary sphinx-build script (that's why I am modifying
$PATH). It's run every 15 minutes to detect and incorporate
documentation changes in SVN. I'm not sure why it did stop firing the
way it should.
jens
#!/bin/sh
ROOT=/home/zope/zopetoolkit
export PATH=${PATH}:${ROOT}/bin
before=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4)
svn up -q $ROOT
after=$(svn info $ROOT | grep ^Last Changed Rev: | cut -d -f 4)
if [ $before != $after ]; then
echo Updated from revision $before to $after; rebuilding HTML docs.
cd $ROOT/doc
python bootstrap.py
${ROOT}/doc/bin/buildout -q -q
make -s releaseinfo /dev/null
make -s html /dev/null
fi
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkxZeVMACgkQRAx5nvEhZLJJzwCcCHstIBdBOiPMch+MQw7AYokD
27IAn0lK9AD+O9mMNALTtbxsVjczyANL
=V54Y
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/4/10 17:26 , Wichert Akkerman wrote: I'm wondering: can it be made to skip useless docs such as http://docs.zope.org/zope.hookable/index.html, perhaps by checking for linecount? There are also a lot of packages that only have a changelog and no documentation, for example http://docs.zope.org/zope.contenttype/index.html . Should those be considered good enough to be linked? IMHO trying to come up with some kind of programmatic algorithm to judge a bit of documentation as good enough to show is insane. I'm not going to attempt it. Maybe shitty (for some definition of shitty, as someone else would say) package docs will compel the maintainers to improve them. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxZiWcACgkQRAx5nvEhZLLOTACfWhQ7OQGQW1noXiT1MbTATbhi SAwAoK/a6i+E2qbmfbNUxTalTNO78MoA =T1Kj -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brian, Do you have access to an source distribution (tarball or zip) for the package involved? In the source distribution the PKG-INFO file is always at the top level. No, these are trunk checkouts. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxXuq0ACgkQRAx5nvEhZLKuOwCeKf/h1Sb9oxUoTPOBgexPafRC essAoLISBbIoU+fQhzk9w4syHZVtKbxw =trcX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/3/10 00:19 , Tres Seaver wrote: The 'pkginfo' utility knows how to extract package metadata from stuff installed on the path: http://packages.python.org/pkginfo/distributions.html#introspecting-installed-packages as well as from checkouts: http://packages.python.org/pkginfo/distributions.html#introspecting-development-checkouts Just like the counterparts in setuptools this only works if you pass it a path that has a PKG-INFO or .egg-info directly in that folder. The problem is, with many packages those are not in the root folder of the package after doing a setup.py egg_info. Those packages normally use the package_dir argument to their setup call in setup.py, but that's information I can't get to, it's in the argument list for the setup call. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxXwEYACgkQRAx5nvEhZLLuYACePk94ugHgdaHXN3kHP2k+91vq jHUAnA9QIvT89QqyILg8vIVQfrnwpoYv =i3gm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 15:51 , Stephan Richter wrote: We have put a lot of energy into putting the full documentation of packages into the package's long description and most packages have this layout (I know, because I did it for most. ;-) So it might be good to use the long description of the package, if the other two methods fail. This would turn on documentation for a lot of packages and we can move them over slowly. This is now implemented as fallback, take another look at the package listing, like the ZTK list[1]. I had to resort to executing setup.py - --long-description in a subprocess, unfortunately. Never found out how to do that programmatically. jens [1] http://docs.zope.org/ztkpackages.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxYf0IACgkQRAx5nvEhZLIFegCgg0WwW5KU4pJufwYboaePCcPL 5NAAnjgLa4vG/i2g1m8MPZI2v3g7o9UB =OPU+ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/3/10 22:59 , Marius Gedminas wrote: On Tue, Aug 03, 2010 at 10:42:42PM +0200, Jens Vagelpohl wrote: listing, like the ZTK list[1]. I had to resort to executing setup.py --long-description in a subprocess, unfortunately. Never found out how to do that programmatically. From a source checkout? There's no other way. Many packages compute their long_description by running code (which reads and concatenates multiple text files). I understand that. But it must be possible to do that programatically in my code. I mean, setup.py --long-description obviously executes Python code, which I may be able to execute myself in my current interpreter session by importing and executing stuff from setuptools. Having to invoke another Python interpreter in a subshell because that's too complicated to do any other way is awful. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxYhIEACgkQRAx5nvEhZLLFqwCeNaScimdWCS3sNQv1QgmwuAr8 bR8AnA1+bcXsAdxuvaNP2AhUXD8S+8Qb =ZE+5 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Martijn, http://docs.zope.org/zope.event/ Really cool! Wouldn't it be good to put this under /package/zope.event to avoid potential naming conflicts? I realize they're rare, but I can imagine that a project foo could exist that wants to expose its documentation separately from project foo. Perhaps Zope would be a good example. :) The specific desire was to offer URLs http://docs.zope.org/package, that's why I created it that way. It's not that hard to add a subdirectory, but I'd rather have consensus first. Me personally I like the straight package URLs without an intermediary subfolder. P.S. It'd be good if the ZODB section had at least a link to zodb.org. Links to buildout.org and grok.zope.org might also be useful. Take a look at the Related Links on the left hand side, they're all in there except for grok.zope.org, which I just added. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWsOQACgkQRAx5nvEhZLKZOgCdGGocKi8dFHkAXPP7W1a7Bqn0 0ZcAnRROfJWNE7ET1ngivR2gvnnb8BYC =X2Io -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 75 OK, 15 Failed, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 14:00 , Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Sun Aug 1 12:00:00 2010 UTC to Mon Aug 2 12:00:00 2010 UTC. There were 91 messages: 6 from Zope Tests, 1 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 56 from jdriessen at thehealthagency.com. I have a feeling these buildbots are getting out of control. Specifically, I think it's perfectly sufficient to run each buildbot just once a day instead of once per each check-in, as seems to be the case for at least the ones at thehealthagency.com. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWtE4ACgkQRAx5nvEhZLK0EgCeLxN3vH95BNXMxHJtAGoXKTLI dk0An0EAc5aVva7HaO/lqhdZ33bW5WME =4zq6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 15:51 , Stephan Richter wrote: We have put a lot of energy into putting the full documentation of packages into the package's long description and most packages have this layout (I know, because I did it for most. ;-) So it might be good to use the long description of the package, if the other two methods fail. This would turn on documentation for a lot of packages and we can move them over slowly. I'll have to look at that. Currently, the documentation builder does not do any introspection on the package itself, mostly because I do not want to fully install the package and pull in all dependencies. Maybe there's a simple way that does not require full installation. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWzlMACgkQRAx5nvEhZLJbtgCfQXs8pT87JAVFFzRwoSKnZ4pm QuYAoJ09ArtylS+MUsYXXqmwxo/0Vogr =WBJO -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 16:36 , Stephan Richter wrote: On Monday, August 02, 2010, Jens Vagelpohl wrote: 'll have to look at that. Currently, the documentation builder does not do any introspection on the package itself, mostly because I do not want to fully install the package and pull in all dependencies. Maybe there's a simple way that does not require full installation. I agree. This does not build the package: python setup.py --long-description Thanks for the hint, I'll try that. Can you give me a sample package where the long description is supposed to be the main documentation? And what's the output from that? If it's ReST I'd have to find a way to convert it to HTML on the fly... sigh jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW2OoACgkQRAx5nvEhZLLLlwCeKw5Y6x9r3x+WaOb1YMlJtY2j nUIAniBuzDN0MJNKbpXf6y14e+AR/sU7 =8yM8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 16:48 , Stephan Richter wrote: On Monday, August 02, 2010, Jens Vagelpohl wrote: Thanks for the hint, I'll try that. Can you give me a sample package where the long description is supposed to be the main documentation? And what's the output from that? If it's ReST I'd have to find a way to convert it to HTML on the fly... sigh zope.security (http://pypi.python.org/pypi/zope.security) Once you have docutils installed, you can do: py26 setup.py --long-description | rst2html rst2html have many options that allow you to modify the style, including the ability to specify a stylesheet. OK, I'll see what I can do with that. I'll probably end up using the long description as last fallback. So you will see every package linked to *something*, even if it's just a page with a few words on it. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW26cACgkQRAx5nvEhZLIczgCfamZ/m01aQt3+h7DnQTDXYpUl /3cAn2Ji0K7MQWHNWZFT/QoBENKZ/r3J =HFeU -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 16:50 , Stephan Richter wrote: On Monday, August 02, 2010, Stephan Richter wrote: py26 setup.py --long-description | rst2html rst2html have many options that allow you to modify the style, including the ability to specify a stylesheet. Oh, btw, this is also the method that we used to verify that the long descriptions are proper ReST. ;-) I hereby declare that verifying proper ReST is OUT OF SCOPE for docs.zope.org ;-) jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW2/QACgkQRAx5nvEhZLJHTQCfW3YchH6YZyJA+JlDgV6J6W7j /1cAn14kcIGJLoIm5iF2KBgiou4t4YCt =0JKd -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 17:00 , Stephan Richter wrote: On Monday, August 02, 2010, Jens Vagelpohl wrote: OK, I'll see what I can do with that. I'll probably end up using the long description as last fallback. So you will see every package linked to *something*, even if it's just a page with a few words on it. Just FYI: If there is no long description (which is very unlikely), then the string UNKNOWN is returned from the --long-description call. OK, that's an excellent flag to give up and say this package has no documentation I can deal with. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW3gEACgkQRAx5nvEhZLKfJwCfVC1ogbRfnzAXX7UUz8mTDYIq 4W8An25biGvShwZrZXUdFCZdFKVg+GsU =cGph -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 16:36 , Stephan Richter wrote: On Monday, August 02, 2010, Jens Vagelpohl wrote: 'll have to look at that. Currently, the documentation builder does not do any introspection on the package itself, mostly because I do not want to fully install the package and pull in all dependencies. Maybe there's a simple way that does not require full installation. I agree. This does not build the package: python setup.py --long-description Can someone tell me how to do that when I am in Python code already? Given the path to the checkout, can I use some setuptools/pkg_resources or pkginfo magic to get at this data? My specific problem is this: Many packages define an intermediate folder, like src, in which the actual code path is stored. When someone runs setup.py egg_info then the .egg-info folder ends up in src and not at the root. Trying to use e.g. pkginfo.Develop or pkg_resources.find_distributions with the root folder won't find the .egg-info folder in the src subfolder. I'd have to do something horrible like os.walk to find distributions, which I really don't want. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW41sACgkQRAx5nvEhZLIrzgCeMVQhPaa0QwSZriPxyzTkyApk 6kIAoIbmZ19Rhq4nKOksK5byw5FAwsyg =d3W2 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/2/10 18:26 , Martijn Faassen wrote: http://packages.python.org/distribute/pkg_resources.html You can probably create a Distribution object somehow (handwave) from a path (whether that's the path of the package or the path the package is in, not sure). The issue, just like with pkginfo.Develop, is that I can't find any function or method that finds package information in subfolders. If you look at... http://packages.python.org/distribute/pkg_resources.html#getting-or-creating-distributions ...there's this function find_distributions which supposedly offers subfolder searching, but it just doesn't work. At least it doesn't do what I would expect when I read the documentation. It finds nothing. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW840ACgkQRAx5nvEhZLK0MgCfWNsSL47dimbU9TlIZNSRq07h HLIAoIYYLdYUsA5PhYrtqhu9EaVk8Nip =GbbC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] docs.zope.org automation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, Here's a followup on a docs.zope.org automation task I took over during one of the Zope developer IRC metings[1]. The task was to provide individual package documentation, if it exists, directly underneath docs.zope.org, e.g.: http://docs.zope.org/zope.event/ ... and keep those docs updated from the current trunk documentation. I expanded that task a little bit by generating content that shows the list of packages divided by project and makes it obvious which packages have documentation and which don't. All of that is in a buildout that automatically generates the docs.zope.org website and does away with the single static HTML page with the dead new new new new.zope.org design and uses stock Sphinx design. If you visit docs.zope.org now you'll notice that the content on the main page has not changed much, it's just been updated and re-ordered slightly. What's new are those links I prefixed with Package documentation, those point to the autogenerated index pages for each project. As noted on top of most of these index pages, if a package is listed but not linked it doesn't have documentation the scripts can recognize. Currently the buildout can recognize the standard Sphinx documentation layout with a folder named doc or docs in the package root and a Sphinx configuration and content therein. The buildout can also use a kludge and pull in content that is documented using z3c.recipe.sphinxdoc maintained in a separate buildout, but I'm hoping those project authors would consider using the standard layout as exemplified by e.g. zope.event[2] and championed by e.g. Tres, Christian Theune, and several others (including me). There's a README in the buildout that explains how to do specific tasks[3]. If you have any questions let me know. jens [1] http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100727.html [2] http://svn.zope.org/zope.event/trunk/docs/ [3] http://svn.zope.org/docs.zope.org_website/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxUW7gACgkQRAx5nvEhZLLhAgCgsHQeyHi9/xDc9aYvLELlM1/e Z0sAnirP2CO3zQ/MTntWTixDj7MIStgA =gadb -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] unit test policy questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/29/10 15:57 , yuppie wrote: Hanno Schlichting wrote: On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspelioptilude+li...@gmail.com wrote: On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote: Sure. But do you always run all tests it picks up while working on a specific test file? Or do you use bin/test with options that allow to run specific files? See the -s and -t options. :) Don't forget -m which runs exactly one module (file). I always use commands like: bin/test -s zope.package bin/test -s zope.package -m test_module bin/test -s zope.package -m test_module -t test_some_method If everybody is using this, nobody is using CMF.buildout for development. Huh? I use it. I just don't use -m myself. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxRibYACgkQRAx5nvEhZLIE7wCfePls1EWIlJ5JlXmkk36kw1+y ZJIAoLpNA7ukrhN/bOV5ZfiCf+GhUbXY =h567 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IRC meeting summaries from 2010-07-13 and 2010-07-06
I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IRC meeting summaries from 2010-07-13 and 2010-07-06
Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IRC meeting summaries from 2010-07-13 and 2010-07-06
Thanks Takeshi, that was the problem. I never clicked that link because on the iPad it shows up in Japanese letters so I had no idea what it was. jens On Jul 18, 2010, at 12:43, Takeshi Yamamoto t...@mac.com wrote: Hi Jens, I am afraid that if you are clicking the v.2 link instead of download link. The download link is located just under the file name per file. Takeshi On Jul 18, 2010, at 7:07 PM, Jens Vagelpohl wrote: Hi Takeshi, I can see the listing but when I click on a file download link I get a page saying insufficient privileges. You must be logged in to view this page. jens On Jul 18, 2010, at 11:27, Takeshi Yamamoto t...@mac.com wrote: It sounds strange. The site is set as public. I have tested with different browsers without login and I could download files. Google account should not be required. Do you mean you cannot see the listing of files when you accessed to that URL in your browser? Takeshi On Jul 18, 2010, at 6:08 PM, Jens Vagelpohl wrote: I cannot access the files. Apparently you must have a Google account and log in :-( jens On Jul 17, 2010, at 19:26, Takeshi Yamamoto t...@mac.com wrote: On Jul 16, 2010, at 3:28 PM, Christian Theune wrote: - We need to deal with the fact that some projects in svn.zope.org are likely abandoned and we need to deal with it. Initially we will start annotating the repository policy report with 'last checkin time' and 'frequent committers' to allow everyone to scan through the rather large report and check for projects that they are interested in. I hope my recent survey could help this activity. Please download and take a look for a first couple of files at this location. URL: http://www.retsu.info/files File1: calc3CsvProjCommitterAcct.xlsx File2: calc3CsvProjPatch.xlsx The first Excel data shows you how 779 projects are patched by commit action. Since one commit action could have several patch action against several different projects, the number is counted based on patch(modify, add, rename, delete) action instead of commit. This will help you to determine which projects are active and which are not active recently. The second Excel data has the patch count per committer per project. The patch count per project per committer is also available as you may find several worksheets in it. This will help you to determine the maintainers for a specific project and how many patches the person committed. Other two files, calc3.py and zopeSvnLog2.log.zip files are downloadable for the person who wants to try to do it by oneself. Just make a temporary directory, put these two files, unzip log file, run calc3.py with ./calc3.py or python calc3.py, open generated txt files with Excel or OpenOffice.org, then sort/summarize/making chart etc within spreadsheets. Just for your info: * We(Me, Yuta, Ryosuke) have translated Philipp's Web Component Development with Zope 3 book into Japanese. First half was published last year, and later half was published a week ago. http://www.springer.jp/discipline/computerscience/ * The last file on the download page, a zipped Excel files shows Zope developers world is growing continuously over past 14 years. The code making activity is continuously growing. Mailing list activity is also active though it was shrunk from the bubble. This number is based on commit, not patch since this does not concern project. Regards, Takeshi Yamamoto ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: Zope/branches/2.12/ - LP #143533: Instead of showing 0.0.0.0 as server name when no
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/14/10 16:28 , Wichert Akkerman wrote: On 7/14/10 16:19 , Jens Vagelpohl wrote: Log message for revision 114741: - LP #143533: Instead of showing 0.0.0.0 as server name when no specific listening IP is configured for the HTTP server, do a socket lookup to show the current server's fully qualified name. Can I object to this change? I would much rather always see the IP address than just the hostname since that is a lot more information. If we change this can we please make it show both IP and hostname? Hi Wichert, The IP makes no sense, because 0.0.0.0 is strictly speaking correct as the IP value, since the process is listening on all interfaces. At that point we have no progress at all. 0.0.0.0 doesn't tell the viewer anything about what server it came from, either. If you were to somehow determine a physical IP then you may confuse the admin who wanted the process to listen on all interfaces, but then gets told only about one. As a compromise I used the FQDN instead of an IP. Putting both a name and an IP into that field violates the RFC[1]. jens [1] https://bugs.launchpad.net/zope2/+bug/143533/comments/1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkw9zRcACgkQRAx5nvEhZLLYuACgkh+O8jI2WX11NN8ZkDnhYVMi he8An3mpxVL4ENVb/s6uMX75JB5/zY9B =7AdY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: Zope/branches/2.12/ - LP #143533: Instead of showing 0.0.0.0 as server name when no
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/14/10 17:00 , Andreas Jung wrote: Wichert Akkerman wrote: I don't mind doing this for a SERVER_NAME in the response, but looking at the diff from the commit email you also changed the startup message from Zope 2 with this change. That is the bit I find problematic: I want to be able to immediately see if the Zope instance is bound to a specific IP address or ANY/0.0.0.0. +1 http://svn.zope.org/?rev=114752view=rev http://svn.zope.org/?rev=114753view=rev jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkw91GoACgkQRAx5nvEhZLIfiACfU5qSaehfJwWAGxRcMoIgxOgT RcMAnArhiGoZyxoIpnYJblyIOs00Zd8G =Z2S5 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I worked on Zope2 bugs today. This is what I managed to get done: Fixed = - https://bugs.launchpad.net/zope2/+bug/143273 - https://bugs.launchpad.net/zope2/+bug/143564 - https://bugs.launchpad.net/zope2/+bug/143722 - https://bugs.launchpad.net/zope2/+bug/143533 - https://bugs.launchpad.net/zope2/+bug/143755 Fixed already = - https://bugs.launchpad.net/zope2/+bug/143765 Confirmed = - https://bugs.launchpad.net/zope2/+bug/143516 Invalid === - https://bugs.launchpad.net/zope2/+bug/143663 Incomplete == - https://bugs.launchpad.net/zope2/+bug/143509 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkw99MQACgkQRAx5nvEhZLI+iQCbBioRd/h25B+uiu5x7leZUz9n w7YAoJVHRQt7+mXd3xwEcR/QVmXwAeJj =qpzr -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Invitation to bug day in July
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/6/10 17:53 , Christian Theune wrote: So, next Wednesday (2010-07-14) is the next bug day. Here's a wiki page so you can also register there to indicate participation: http://wiki.zope.org/ztk/BugDay20100714 I'll not that the simple table you chose is impossibly finicky to follow and add data to. I fiddled for 5 minutes to find the right magic number of spaces between my column entries to not make the whole table _disappear_. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwzYPAACgkQRAx5nvEhZLLCaQCfToM2NP8NvicIgkCmM/BSvRRF CqsAnjFRJfWkUr5tZQ75K4OW7O+kTwtG =UhnW -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests list admin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/4/10 10:41 , Adam GROSZER wrote: Hello Shane, Are you the list admin there or you know who it is? Hi Adam, I just looked and Shane's no longer working zope.com address was listed as the only admin. I put myself in instead. Do you need me to do anything? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwwTP4ACgkQRAx5nvEhZLIebACfY7PXyxwYIjMcTW+CxKnbP7hR TAMAoLPvb7A9UjRvx7Ras6LQeydghBGS =ZTYs -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New release of z3c.form
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/1/10 17:36 , Martin Aspeli wrote: On 1 July 2010 21:10, Godefroid Chapelle got...@bubblenet.be wrote: http://packages.python.org/z3c.form Who will get rid of http://docs.zope.org/z3c.form/ ? If you do, can you please make it link or redirect to the new location? There are live links to that kind of thing in lots of documentation I've written. ;-) I have set up a permanent redirect from docs.zope.org/z3c.form to packages.python.org/z3c.form. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwvPTAACgkQRAx5nvEhZLIn1ACfW7OQZeujJ84bZN45tnS4QIiC onIAn3fZfWds/2waxr7tL4EByKV0liI7 =0crl -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.sendmail and critical transaction errors.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/24/10 09:30 , Chris Withers wrote: Tres Seaver wrote: The misconfiguration of the mail host in transactional mode *does* cause the server to go into a lockdown mode (because errors are not supposed to be raised in 'tpc_finish'). There is *no* database corruption, but the transaction manager can't know that, and so it deliberately refuses to commit more transactions until the admin un-futzes the problem (in this case, by fixing the mailhost configuration) and restarts the server. Yeah, what he said... It's not as easy as that, though. Mailhost misconfiguration is just one reason why errors may be raised during the actual sending. The receiver address may be wrong, which is where I tend to see it. This is not a condition I could reasonably test for in my code before attempting to send though the MailHost. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwjDWUACgkQRAx5nvEhZLKf9ACgjfp7Nxf5B+2BwT6Egp6mhuVV yGIAoKhuD8sEGT+mn6NcbTvqlWxduYsi =LIL8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [alert] domain issues zope.org and zopefoundation.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, Unknown to the Zope Foundation and the ZF admins it appears the zope.org and zopefoundation.org domains have expired. The domains were held by Rob Page as Zope Corporation representative. For community members this means services like the different community websites, SVN access, and the mailing lists may be disrupted until the domain situation is corrected. We are in the process of trying to reach Rob Page. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwYusUACgkQRAx5nvEhZLKzRgCfen1pSegA6r7ZigvwsRISM7Tu rBUAnjBmAXwS6HECUYcoF3357z3750pF =MVaV -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Bug day report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I worked on Zope2 bugs today. This is what I managed to get done: Fixed = https://bugs.launchpad.net/zope2/+bug/143946 https://bugs.launchpad.net/zope2/+bug/374818 https://bugs.launchpad.net/zope2/+bug/142535 https://bugs.launchpad.net/zope2/+bug/143403 https://bugs.launchpad.net/zope2/+bug/143619 https://bugs.launchpad.net/zope2/+bug/143639 Marked Confirmed https://bugs.launchpad.net/zope2/+bug/143485 https://bugs.launchpad.net/zope2/+bug/143244 https://bugs.launchpad.net/zope2/+bug/143281 Marked Incomplete = https://bugs.launchpad.net/zope2/+bug/143621 https://bugs.launchpad.net/zope2/+bug/143704 Marked Duplicate https://bugs.launchpad.net/zope2/+bug/143743 Already fixed (marked Fix Released) === https://bugs.launchpad.net/zope2/+bug/143875 https://bugs.launchpad.net/zope2/+bug/142717 https://bugs.launchpad.net/zope2/+bug/143271 Moved to a different project https://bugs.launchpad.net/zope.pagetemplate/+bug/143923 https://bugs.launchpad.net/zope.formlib/+bug/143930 Marked Invalid == https://bugs.launchpad.net/zope2/+bug/143213 jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwZDAMACgkQRAx5nvEhZLJCiACdEjleEjHTSQ+X4NbL3A0uRYXN x4kAn01PzhDHRjqhd07ki+jD0reJyWOA =Rq9Y -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 36 OK, 8 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/3/10 16:29 , Tres Seaver wrote: Zope Tests Summarizer wrote: Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:33:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014779.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 2 09:36:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/014781.html These failures occur only on OSX: I have no idea how to diagnose them. The ComponentLookupError for '__main__.IFooMarker' shouldn't be able to fail at all. I cannot reproduce those failures using the bin/testall script from the Zope2 egg. I'm guessing the buildbot uses the same script since the number of tests executed matches what I see in my sandboxes. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwIrt4ACgkQRAx5nvEhZLKP5ACfVSpfyR6E70GfGq6k2enNf8ev 6fkAn1S78VG/jmnOPPehW7SC8RmAfeSb =OibX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] REMINDER: Planned server and list outage LATER TODAY
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reminder: Today at 20:00 UTC (less than 12 hours from now) one of the Zope Foundation-maintained servers will be physically moved to a different data center by our hosting provider. The server will be shut down at around 20:00 UTC and, according to the hosting provider, become available again no later than 05:30 UTC tomorrow (Friday, May 28). This outage will affect several websites as well as the mailing list service. No mail sent to the lists will be lost, though, it will just be queued up on our secondary mail relay, which is unaffected by this move. Once the main server comes back up it will be delivered. Services affected = - the docs.zope.org website - the download.zope.org website - all zope.org mailing lists and the lists.zope.org website Server shutdown === Thursday, May 27 (TODAY) 20:00 UTC - 22:00 CEST/Berlin - 16:00 EDT/New York - May 28 06:00 EST/Sydney Server start On or before Friday, May 28 (TOMORROW) 05:30 UTC - 07:30 CEST/Berlin - 01:30 EDT/New York - 15:30 EST/Sydney jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkv+LTYACgkQRAx5nvEhZLIg4gCeKpPV3ZZVinNhDA8F9Rj1KV0Q nkMAnj1r+faNJnWhEKIrYqhZYUITipJx =EDSt -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] NOTICE: Planned server and list outage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please note: First of all, apologies for the cross-posting. I wanted to reach as many people as possible. On Thursday, May 27 (2 days from now) one of the Zope Foundation-maintained servers will be physically moved to a different data center by our hosting provider. The server will be shut down at around 20:00 UTC and, according to the hosting provider, become available again no later than 05:30 UTC the next day (Friday, May 28). This outage will affect several websites as well as the mailing list service. No mail sent to the lists will be lost, though, it will just be queued up on our secondary mail relay, which is unaffected by this move. Once the main server comes back up it will be delivered. Services affected = - the docs.zope.org website - the download.zope.org website - all zope.org mailing lists and the lists.zope.org website Server shutdown === Thursday, May 27 20:00 UTC - 22:00 CEST/Berlin - 16:00 EDT/New York - May 28 06:00 EST/Sydney Server start On or before Friday, May 28 05:30 UTC - 07:30 CEST/Berlin - 01:30 EDT/New York - 15:30 EST/Sydney I will send a reminder a few hours before the move. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkv7m9AACgkQRAx5nvEhZLKc6ACdGs5yEK91p/4zqC962mRK1uAE 1ZUAoLX+sS1EoCvvd4lztmpxGwmla8RO =g4v9 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] REMINDER: Planned server outage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reminder: In about 3.5 hours one of the Zope Foundation-maintained servers will be physically moved to a different data center by our hosting provider. The server will be shut down at around 20:00 UTC and, according to the hosting provider, become available again no later than 05:30 UTC tomorrow (May 11). As you can see from the list of services affected below the impact will be minimal. Services affected = - - the zope2.zope.org website - - backup mail services Server shutdown === Monday, May 10 20:00 UTC - 22:00 CEST/Berlin - 16:00 EDT/New York - May 11 06:00 EST/Sydney Server start On or before Tuesday, May 11 05:30 UTC - 07:30 CEST/Berlin - 01:30 EDT/New York - 15:30 EST/Sydney jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkvoNuoACgkQRAx5nvEhZLKLMgCgiLXFniNgMOT4oDxTQgQ3PYG6 BGoAnRCpBy22FzFfN7NcPF8ICfJWyTxv =uVqF -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] NOTICE: Planned server outage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please note: First of all, apologies for the cross-posting. I wanted to reach as many people as possible. On Monday, May 10 (tomorrow) one of the Zope Foundation-maintained servers will be physically moved to a different data center by our hosting provider. The server will be shut down at around 20:00 UTC and, according to the hosting provider, become available again no later than 05:30 UTC the next day (May 11). As you can see from the list of services affected below the impact will be minimal. Services affected = - - the zope2.zope.org website - - backup mail services Server shutdown === Monday, May 10 20:00 UTC - 22:00 CEST/Berlin - 16:00 EDT/New York - May 11 06:00 EST/Sydney Server start On or before Tuesday, May 11 05:30 UTC - 07:30 CEST/Berlin - 01:30 EDT/New York - 15:30 EST/Sydney I will send a reminder a few hours before the move. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkvmjk8ACgkQRAx5nvEhZLI2dgCfdqBZ9mnxxYjP1g4gOWQchNZR L+gAn0VPWNp0dg2wBSVyueWnkrwnVW3h =JpIB -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
