[Zope] Zope 4.5.5 and 5.1.2 released

2021-03-02 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the releases of 
Zope 4.5.5 and 5.1.2.

This bugfix release solves a few minor issues and improves security checking 
for some types of XML-RPC requests. For the full list of changes see the change 
logs at https://zope.readthedocs.io/en/4.x/changes.html#id1 and 
https://zope.readthedocs.io/en/latest/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html and 
https://zope.readthedocs.io/en/latest/INSTALL.html.

Jens Vagelpohl


signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Zope 4.5.5 and 5.1.2 released

2021-03-02 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the releases of 
Zope 4.5.5 and 5.1.2.

This bugfix release solves a few minor issues and improves security checking 
for some types of XML-RPC requests. For the full list of changes see the change 
logs at https://zope.readthedocs.io/en/4.x/changes.html#id1 and 
https://zope.readthedocs.io/en/latest/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html and 
https://zope.readthedocs.io/en/latest/INSTALL.html.

Jens Vagelpohl


signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope] Two low-impact security issues in Products.PluggableAuthService

2021-02-26 Thread Jens Vagelpohl
Hi all,

Two low-impact security issues have been identified in 
Products.PluggableAuthService:

- an information disclosure issue involving the ZODB Role Manager plugin. See 
https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p
 for details.

- an open redirect issue in the Cookie Auth Helper. See 
https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr
 for details.

Both issues are mitigated by updating to Products.PluggableAuthService version 
2.6.1 or higher. The Plone release managers will apply this update with Plone 
bugfix releases they are planning to publish within the next few days.

jens




signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Two low-impact security issues in Products.PluggableAuthService

2021-02-26 Thread Jens Vagelpohl
Hi all,

Two low-impact security issues have been identified in 
Products.PluggableAuthService:

- an information disclosure issue involving the ZODB Role Manager plugin. See 
https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p75f-g7gx-2r7p
 for details.

- an open redirect issue in the Cookie Auth Helper. See 
https://github.com/zopefoundation/Products.PluggableAuthService/security/advisories/GHSA-p44j-xrqg-4xrr
 for details.

Both issues are mitigated by updating to Products.PluggableAuthService version 
2.6.1 or higher. The Plone release managers will apply this update with Plone 
bugfix releases they are planning to publish within the next few days.

jens




signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope] Zope 4.5.4 and 5.1.1 released

2021-02-10 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the releases of 
Zope 4.5.4 and 5.1.1.

This bugfix release solves a few minor issues and updates the shipped versions 
of bootstrap, jQuery and Font Awesome to their latest releases. For the full 
list of changes see the change logs at 
https://zope.readthedocs.io/en/4.x/changes.html#id1 and 
https://zope.readthedocs.io/en/latest/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html and 
https://zope.readthedocs.io/en/latest/INSTALL.html.

Jens Vagelpohl


signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Zope 4.5.4 and 5.1.1 released

2021-02-10 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the releases of 
Zope 4.5.4 and 5.1.1.

This bugfix release solves a few minor issues and updates the shipped versions 
of bootstrap, jQuery and Font Awesome to their latest releases. For the full 
list of changes see the change logs at 
https://zope.readthedocs.io/en/4.x/changes.html#id1 and 
https://zope.readthedocs.io/en/latest/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html and 
https://zope.readthedocs.io/en/latest/INSTALL.html.

Jens Vagelpohl


signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Zope 4.5.3 released

2020-11-16 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the release of 
Zope 4.5.3.

This bugfix release solves an issue introduced in version 4.5.2 for 
installations running under Python 2. For the full list of changes see the 
change log at https://zope.readthedocs.io/en/4.x/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html

Jens Vagelpohl



signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Zope 5.1 released

2020-11-12 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the release of 
Zope 5.1.

This release solves a few small page template related issues and brings back 
the ZMI “Debug Information” Control Panel page. For the full list of changes 
see the change log at https://zope.readthedocs.io/en/latest/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/latest/INSTALL.html

Jens Vagelpohl



signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-Annce] Zope 4.5.2 released

2020-11-12 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the release of 
Zope 4.5.2.

This bugfix release solves a few small page template related issues and brings 
back the ZMI “Debug Information” Control Panel page. For the full list of 
changes see the change log at 
https://zope.readthedocs.io/en/4.x/changes.html#id1

Installation instructions can be found at 
https://zope.readthedocs.io/en/4.x/INSTALL.html

Jens Vagelpohl



signature.asc
Description: Message signed with OpenPGP
___
Zope-Announce maillist  -  Zope-Announce@zope.org
https://mail.zope.org/mailman/listinfo/zope-announce

  Zope-Announce for Announcements only - no discussions

(Related lists -
 Users: https://mail.zope.org/mailman/listinfo/zope
 Developers: https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope] Zope 4.1.1 released

2019-07-02 Thread Jens Vagelpohl
On behalf of Zope developer community I am pleased to announce the release of 
Zope 4.1.1.

It is a bugfix release with the following changes:

* fixed the ZMI for non-root deployments.
* document the zope.conf parameters directly from its schema
* update to more current dependencies

For details of the changes see
https://zope.readthedocs.io/en/latest/changes.html#id1


To install the new version see
https://zope.readthedocs.io/en/latest/INSTALL.html

Jens Vagelpohl



signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Announcement: Zope 4.0-final released

2019-06-14 Thread Jens Vagelpohl
No. You will need to do extensive testing of your application  

jens


> On Jun 14, 2019, at 16:50, Jesus Cea  wrote:
> 
>> On 10/5/19 14:48, Michael Howitz wrote:
>> On behalf of Zope developer community I am happy to announce the
>> final release of Zope 4.
> 
> Great!.
> 
> Am I supposed to be able to just upgrade a Zope 2.13.29 deployment to
> 4.0 without with little if any worries? I will use python 2.7 for now.
> 
> My plan is:
> 
> Python 2.7 + Zope 2 -> Python 2.7 + zope 4 -> (future) -> Python 3
> 
> Is that sensible?.
> 
> -- 
> Jesús Cea Avión _/_/  _/_/_/_/_/_/
> j...@jcea.es - http://www.jcea.es/ _/_/_/_/  _/_/_/_/  _/_/
> Twitter: @jcea_/_/_/_/  _/_/_/_/_/
> jabber / xmpp:j...@jabber.org  _/_/  _/_/_/_/  _/_/  _/_/
> "Things are not so easy"  _/_/  _/_/_/_/  _/_/_/_/  _/_/
> "My name is Dump, Core Dump"   _/_/_/_/_/_/  _/_/  _/_/
> "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
> 
> ___
> Zope maillist  -  Zope@zope.org
> https://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope-announce
> https://mail.zope.org/mailman/listinfo/zope-dev )

___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Zone 4 issue: The 'Paste' distribution was not found and is required by the application

2019-06-14 Thread Jens Vagelpohl
You can run “bin/pip install Paste” in the virtualenv.

jens



> On 14. Jun 2019, at 13:46 , Giampiero Benvenuti 
>  wrote:
> 
> Hello,
> 
> I was wondering if somebody run into this error, and how should I take care 
> of it:
> 
> python3.6 -m venv zope4.0
> cd zope4.0
> bin/pip install -r 
> https://zopefoundation.github.io/Zope/releases/4.0/requirements-full.txt
> bin/mkwsgiinstance -d .
> bin/runwsgi -v etc/zope.ini
> 
> Error:
> File 
> "/Applications/zope4.0/lib/python3.6/site-packages/pkg_resources/__init__.py",
>  line 778, in resolve
>   raise DistributionNotFound(req, requirers)
> pkg_resources.DistributionNotFound: The 'Paste' distribution was not found 
> and is required by the application
> 
> Any idea?
> 
> Thanks so much,
> 
> Giampiero
> ___
> Zope maillist  -  Zope@zope.org
> https://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope-announce
> https://mail.zope.org/mailman/listinfo/zope-dev )



signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Announcement: Zope 4.0-final released

2019-05-10 Thread Jens Vagelpohl

> On 10. May 2019, at 7:48 , Michael Howitz  wrote:
> 
> 
> To install the new version see the instructions for
> either zc.buildout: http://zope.readthedocs.io/en/latest/INSTALL-buildout.html
> or virtualenv/pip: 
> http://zope.readthedocs.io/en/latest/INSTALL-virtualenv.html
> or pipenv: https://zope.readthedocs.io/en/latest/INSTALL-pipenv.html


CORRECTION: The installation documentation is at 
https://zope.readthedocs.io/en/latest/INSTALL.html


jens





signature.asc
Description: Message signed with OpenPGP
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope-CMF] Products.CMFCore release

2013-10-15 Thread Jens Vagelpohl

On Oct 14, 2013, at 23:02 , Harald Friessnegger har...@webmeisterei.com wrote:

 hi jens
 
 i've added a test for my change.
 http://svn.zope.org/Products.CMFCore/branches/2.2/Products/CMFCore/tests/test_SkinsTool.py?rev=130325view=rev
 
 can you fix the other tests and make a new release?


Hi Harald,

You have not forward-ported the test to the trunk. Please do so.

I have created a new release and uploaded it to PyPI.

jens




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] Products.CMFCore release

2013-10-15 Thread Jens Vagelpohl

On Oct 15, 2013, at 9:09 , yuppie y.2...@wcm-solutions.de wrote:

 Jens Vagelpohl wrote:
 I have created a new release and uploaded it to PyPI.
 
  -2.2.8 (unreleased)
  +2.2.8 (2014-10-15)
 
 You've got a time machine? Cheers, Yuppie

Sorry, typo. I have corrected the file in SVN, but IMHO a new egg won't be 
required, right?

I have also managed to fix the issue with the svn.zope.org mail hook, even 
though that's not my job anymore.

jens







signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] Products.CMFCore release

2013-10-14 Thread Jens Vagelpohl

On Oct 14, 2013, at 13:31, Harald Friessnegger har...@webmeisterei.com wrote:

 hi jens
 
 you're right about a missing test for the change.
 however, the method getSkinNameFromRequest is not involved in any unit-test 
 by now.
 if you wont' add the change to the next release w/o a propert test, i'll add 
 it. just let me know

Please do. That would have caught the trunk mess-up, too, so you can see 
there's a good reason to test every change in behavior, even if the behavior is 
not fully tested at present.

jens




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] Products.CMFCore release

2013-10-13 Thread Jens Vagelpohl

On Oct 11, 2013, at 19:11 , Tres Seaver tsea...@palladion.com wrote:

 Signed PGP part
 On 10/11/2013 07:34 AM, Harald Friessnegger wrote:
  hi tres
  
  sorry for the last mail. it got sent accidentally before i could
  finish it.
  
  i did a minor change to cmfcore that i'd love to see in the next
  releases of plone. http://dev.plone.org/ticket/10071#comment:8
  
  could you please review the change and do a new release on pypi?
  
  thanks for your reply and have a nice weekend
 
 I can't get to this before sometime next week.  Hanno and Jens are the
 other two release-makers (CC'ed).

If it was just about making a release I could have done it quickly. However, I 
see two issues I don't have time to look into right now:

- the change has no unit test

- two others are failing:

snip

Failure in test test_getActionObject_oldskool_action_deprecated 
(Products.CMFCore.tests.test_ActionsTool.ActionsToolTests)
Traceback (most recent call last):
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 331, in run
testMethod()
  File 
/usr/local/src/Products.CMFCore-2.2/Products/CMFCore/tests/test_ActionsTool.py,
 line 94, in test_getActionObject_oldskool_action_deprecated
'2.4. Use Action and Action Category objects instead.' in warning)
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 424, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true



Failure in test test_getDiff 
(Products.CMFCore.tests.test_FSPythonScript.CustomizedPythonScriptTests)
Traceback (most recent call last):
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 331, in run
testMethod()
  File 
/usr/local/src/Products.CMFCore-2.2/Products/CMFCore/tests/test_FSPythonScript.py,
 line 274, in test_getDiff
self.assertEqual(list(cps.getDiff()), _DIFF_TEXT.splitlines())
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 515, in assertEqual
assertion_func(first, second, msg=msg)
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 744, in assertListEqual
self.assertSequenceEqual(list1, list2, msg, seq_type=list)
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 726, in assertSequenceEqual
self.fail(msg)
  File 
/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/unittest/case.py,
 line 412, in fail
raise self.failureException(msg)
AssertionError: Lists differ: ['--- original', '+++ modified... != ['--- 
original ', '+++ modifie...

First differing element 0:
--- original
--- original 

- ['--- original',
+ ['--- original ',
?   +

-  '+++ modified',
+  '+++ modified ',
?   +

   '@@ -7,4 +7,4 @@',
   ' ##parameters=',
   ' ##title=',
   ' ##',
   -return 'cps',
   +return 'cps -- replaced']

  Ran 235 tests with 2 failures and 0 errors in 0.541 seconds.
Tearing down left over layers:
  Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Total: 612 tests, 2 failures, 0 errors in 8.445 seconds.

jens




signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-dev] Github tip to get less github spam:

2013-03-13 Thread Jens Vagelpohl

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

2013-02-11 Thread Jens Vagelpohl

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] Announcement: 2013 Zope Foundation Board Elections and General Meeting

2013-02-02 Thread Jens Vagelpohl

On Feb 2, 2013, at 1:49 , Alex Clark acl...@aclark.net wrote:

 Hi Tres,
 
 On 2013-02-01 16:19:55 +, Tres Seaver said:
 An online version of this announcement is available at:
  http://foundation.zope.org/news/2013_election_and_general_meeting
 
 
 I get a 404 on this link FWIW

Sorry about that, the news item had not been created. I have done that now.

jens


___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] help

2013-01-15 Thread Jens Vagelpohl

On Jan 15, 2013, at 14:01 , Daniel Godefroy danielgodef...@videotron.ca wrote:

 Please remove me from the list

Just follow the link that you see at the bottom of every single email from the 
list.

Thanks!

jens



___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope-dev] Zope2 git mirror not updating?

2013-01-11 Thread Jens Vagelpohl

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

2013-01-10 Thread Jens Vagelpohl

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

2013-01-10 Thread Jens Vagelpohl

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

2013-01-10 Thread Jens Vagelpohl

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

2013-01-10 Thread Jens Vagelpohl

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

2013-01-10 Thread Jens Vagelpohl

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.

2012-12-12 Thread Jens Vagelpohl

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 )


Re: [Zope] Zope and security vulnerability: 20121106

2012-11-13 Thread Jens Vagelpohl

On Nov 13, 2012, at 10:16 , Jürgen Herrmann juergen.herrm...@xlhost.de wrote:
 I successfully applied these hotfixes to Zope 2.13 versions
 without any problems. What puzzles me though is why was there
 no announcement for theses fixes here on zope ml? Or are these
 fixes not critical for pure Zope2 users? Or are these all fixed
 in the latest version of Zope2?

There was no announcement here because those patches were prepared by Plone 
developers without our knowledge and announced without our knowledge. The Zope 
developers know as much about these patches (meaning little to nothing) as any 
other Zope user.

jens




smime.p7s
Description: S/MIME cryptographic signature
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


[Zope-CMF] CMF security patches in Products.PloneHotfix20121106

2012-11-09 Thread Jens Vagelpohl
Hi all,

I don't recall any information being provided to the CMF developers about CMF 
fixes in the most recent Plone Hotfix:

http://plone.org/products/plone-hotfix/releases/20121106

For example, there's a monkey patch to make sure getToolByName only returns 
valid tool objects and nothing else, see the attached file.

I'm not sure if there's an oversight of not forwarding this information to us 
or if it was determined this fix is not relevant for the CMF. Would any list 
member who also works on Plone have an insight?

Thanks!

jens



from Products.CMFCore import utils
try:
   from Products.CMFPlone.FactoryTool import FauxArchetypeTool
   HAS_FAT = True
except ImportError:
   FauxArchetypeTool = None
   HAS_FAT = False
from persistent.interfaces import IPersistent
try:
from OFS.interfaces import IItem
except ImportError:
IItem = IPersistent

try:
tool_registry = utils._tool_interface_registry
except AttributeError:
tool_registry = {}

gtbn = utils.getToolByName
def wrapped_getToolByName(obj, name, default=utils._marker):
result = gtbn(obj, name, default)
if IPersistent.providedBy(result) or \
IItem.providedBy(result) or \
name in tool_registry or \
(HAS_FAT and isinstance(result, FauxArchetypeTool)) or \
result is utils._marker or \
result is default:
return result
else:
raise TypeError(Object found is not a portal tool (%s) % (name,))
return result
utils.getToolByName = wrapped_getToolByName

try:
import Products.CMFPlone.utils
Products.CMFPlone.utils.getToolByName = wrapped_getToolByName
except ImportError:
pass




smime.p7s
Description: S/MIME cryptographic signature
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


[Zope-dev] Zope Foundation patch policy

2012-10-09 Thread Jens Vagelpohl
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 )


[Zope] Zope Foundation patch policy

2012-10-09 Thread Jens Vagelpohl
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 maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope-dev] We need to change how code ownership works.

2012-08-20 Thread Jens Vagelpohl

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

2012-08-19 Thread Jens Vagelpohl

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

2012-08-19 Thread Jens Vagelpohl

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

2012-08-19 Thread Jens Vagelpohl

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

2012-08-19 Thread Jens Vagelpohl

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

2012-08-18 Thread Jens Vagelpohl
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

2012-08-18 Thread Jens Vagelpohl
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

2012-08-18 Thread Jens Vagelpohl

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

2012-08-18 Thread Jens Vagelpohl

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

2012-08-18 Thread Jens Vagelpohl

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-CMF] 2.3

2012-04-05 Thread Jens Vagelpohl

On Apr 5, 2012, at 17:08 , Charlie Clark wrote:

 fuchsia:Products.DCWorkflow charlieclark$ bin/sphinx-build docs tmp
 Running Sphinx v1.1.3
 loading pickled environment... done
 No builder selected, using default: html
 building [html]: targets for 0 source files that are out of date
 updating environment: 0 added, 2 changed, 1 removed
 Traceback (most recent call last):rkflow
  File 
 /Users/charlieclark/Sites/CMF/src/Products.DCWorkflow/eggs/Sphinx-1.1.3-py2.6.egg/sphinx/ext/autodoc.py,
  line 321, in import_object
__import__(self.modname)
 
 I'm using the CMF-level api-doc to generate the ReST files. - I suspect 
 this may be where I'm going wrong but I couldn't see anything in the conf.py 
 or Makefile that looked liked it would work the proper magic.

H Charlie,

Before going any further, please stop that usage pattern. The correct way to 
build those Sphinx docs is:

- cd into the docs folder
- make sure the sphinx-build script you want to use, which can be either the 
one inside Products.DCWorkflow or at the toplevel CMF package, is in the path 
and then run make html:

$ cd docs/
$ PATH=../bin:$PATH make html
...

I have a feeling with the way you are doing it you put output and Sphinx build 
state files for different Sphinx buildouts in one and the same place, which 
will not work.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-04-04 Thread Jens Vagelpohl

On Apr 3, 2012, at 14:55 , Charlie Clark wrote:
 I had a go at autogenerating the api documentation but failed miserably - 
 lots of empty pages got generated because Sphinx had trouble with import 
 paths. Does anyone know the appropriate incantations for this?

I have fixed it by creating a small buildout configuration at the root of the 
package that will create a working sphinx-build script under bin/ with all the 
dependencies set up, and by replacing all faulty module references to 
CMFDefault with Products.CMFDefault.

I also cleaned up many Sphinx complaints about bad formatting.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-03-31 Thread Jens Vagelpohl

On Mar 31, 2012, at 17:03 , Charlie Clark wrote:

 Am 21.03.2012, 22:58 Uhr, schrieb Jens Vagelpohl j...@dataflake.org:
 
 The beta eggs are released now.
 
 Jens,
 
 could we have a patch release to include my fallbacks? I'd like to be able to 
 try the beta with a couple of other sites without adding links to trunk in my 
 buildouts.

Products.CMFCore and Products.CMFDefault are now released as version 2.3.0-beta2

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-03-22 Thread Jens Vagelpohl

On Mar 22, 2012, at 13:42 , Charlie Clark wrote:

 PS. I've just run tests on trunk and am getting failures in CMFCore:

The tests only fail on Python 2.7, they run through fine on 2.6. As such, 
they're not functional failures but failures dur to changes in behavior between 
2.6 and 2.7. In one place a DeprecationWarning is not written to the log, in 
another diff output has changed slightly.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-03-21 Thread Jens Vagelpohl

On Mar 21, 2012, at 15:55 , Charlie Clark wrote:

 Am 21.03.2012, 00:36 Uhr, schrieb Tres Seaver tsea...@palladion.com:
 
 Sounds good.  We should review the code for any stuff
 deprecated-and-promised-to-be-remove-in-2.3 before releasing a beta.
 
 I suppose we could also migrate the old Zope Help docs to docs for
 Sphinx generation? I know much of the docs are inaccurate and outdated but
 this might help expose the worst bits which should then be exorcised or at
 least pruned.
 
 Not sure if this would be for 2.3 but I think that CMFCalendar should be
 rolled into CMFDefault. The main reason being that the default profile for
 CMFCalendar uses browser views and explicitly requires the CMFDefault skin
 layer. You then can't use CMFCalendar if you override the default skin
 layer. Plus, CMFCalendar's functionality is extremely limited and
 intimately tied to CMFDefault.

If we keep piling up tasks that are too big to be tackled in a small amount of 
time as part of the release process we'll never get anything released. I would 
classify both these items as nice to have, but not on the critical path.

jens



___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-03-21 Thread Jens Vagelpohl

On Mar 20, 2012, at 23:25 , Jens Vagelpohl wrote:

 
 On Mar 20, 2012, at 16:14 , Charlie Clark wrote:
 
 Hi,
 
 I finally landed my update step for syndication during the PyCon sprints! I 
 thought I had a few more browser views to update to using the 
 EditSettingsForm but on a quick check of the files it seems that this has 
 already been done. Yuppie, I remember that you have commented out some of my 
 views (portal configuration and membership, I think) because of the encoding 
 problem, did you correct them yourself last year and I was simply looking at 
 old source? If that is the case then I think we're good to go with 2.3.
 
 
 If there are no objections I could run through the packages and create 2.3.0 
 betas later this week or this coming weekend.

The beta eggs are released now.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] 2.3

2012-03-20 Thread Jens Vagelpohl

On Mar 20, 2012, at 16:14 , Charlie Clark wrote:

 Hi,
 
 I finally landed my update step for syndication during the PyCon sprints! I 
 thought I had a few more browser views to update to using the 
 EditSettingsForm but on a quick check of the files it seems that this has 
 already been done. Yuppie, I remember that you have commented out some of my 
 views (portal configuration and membership, I think) because of the encoding 
 problem, did you correct them yourself last year and I was simply looking at 
 old source? If that is the case then I think we're good to go with 2.3.


If there are no objections I could run through the packages and create 2.3.0 
betas later this week or this coming weekend.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Jens Vagelpohl

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

2012-02-01 Thread Jens Vagelpohl

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

2012-02-01 Thread Jens Vagelpohl
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

2012-01-03 Thread Jens Vagelpohl

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

2012-01-02 Thread Jens Vagelpohl
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

2012-01-01 Thread Jens Vagelpohl

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

2012-01-01 Thread Jens Vagelpohl
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

2012-01-01 Thread Jens Vagelpohl

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

2011-11-28 Thread Jens Vagelpohl
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

2011-10-27 Thread Jens Vagelpohl

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

2011-10-17 Thread Jens Vagelpohl
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

2011-10-17 Thread Jens Vagelpohl

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

2011-10-14 Thread Jens Vagelpohl
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: [ZWeb] zope.org move

2011-10-14 Thread Jens Vagelpohl

On Oct 12, 2011, at 16:03 , Jim Fulton wrote:

 On Wed, Oct 12, 2011 at 8:59 AM, Jim Fulton j...@zope.com wrote:
 ...
 I suspect there might be releases lurking elsewhere.  I'll run the script
 I used to generate the dump for other parts of the database, just in case.
 
 There were a few releases under Documentation and quite a few under Members.
 
 I've put Documentation.tgz and Members.tgz in app2.zope.org:/home/zope

Thanks Jim. Those files are now stitched into old.zope.org as well.

I'm going to prepare an email to zope-...@zope.org now describing the 
conversion and asking people to check for any files they may depend on 
(buildouts, etc).

jens



___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


[Zope] Conversion old.zope.org to static site

2011-10-14 Thread Jens Vagelpohl
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 maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Conversion old.zope.org to static site

2011-10-14 Thread Jens Vagelpohl

On Oct 14, 2011, at 11:44 , Jaroslav Lukesh wrote:

 Try to use this mirroring software - Metaproducts Offline Explorer 
 Enterprise.

Hi Jaroslav,

I'm not sure what you mean. The conversion is already done. We are not looking 
for software to do it. We're gathering feedback and fixing issues at this stage.

jens



___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Conversion old.zope.org to static site

2011-10-14 Thread Jens Vagelpohl

On Oct 14, 2011, at 12:26 , Jaroslav Lukesh wrote:

 Hi,
 there are no image to view:
 
 http://old.zope.org/Members/heiko.stoermer/ListMate/manual_pics/folder_contents
 
 Image is missing:
 
 http://old.zope.org/Members/heiko.stoermer/ListMate/manual_pics/ListMate_create.gif/image_view
 
 and code:
 
 img src=../ListMate_create.gif

The tutorial page, which uses those files, is now fixed:

http://old.zope.org/Members/heiko.stoermer/ListMate/manual_html

The last broken image at the top doesn't exist on the old site, either.

jens



___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [ZWeb] buildout link broken

2011-10-12 Thread Jens Vagelpohl

On Oct 12, 2011, at 12:09 , Baiju M wrote:

 On Wed, Oct 12, 2011 at 3:34 PM, Sascha Welter zopel...@betabug.ch wrote:
 Hi!
 
 Someone on #zope just noted that on http://www.zope.org/community the
 link to http://buildout.zope.org/ is dead. buildout.zope.org does not
 resolve properly (there is a CNAME record to hetzner03-1.zope.org - but
 name resolution stops there).
 
 The CNAME could be fixed, but I would suggest to use the actual URL, that is
 http://www.buildout.org/

Hi Sascha,

This is my fault, the new CNAME for buildout.zope.org was set wrong when I 
moved all content to the new ZF server. I just corrected it, it may take a fw 
hours to be visible everywhere.

As Baiju says, the canonical domain for that site is www.buildout.org, which 
has worked throughout.

jens



___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [Zope-dev] Missing Zope2 tarballs

2011-10-11 Thread Jens Vagelpohl

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

2011-10-11 Thread Jens Vagelpohl

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: [ZWeb] zope.org move

2011-10-11 Thread Jens Vagelpohl
Hi Jim,

 Great. I have a 400MB tarball.  I put in ~zope on app2.zope.org. I assume you
 have access to that machine. If not, let me know where I should
 put it.
 
 As soon as you bring up a static old.zope.org (and switch dns, of course),
 I'll decommission the current machines.

Others have found a serious issue with the static data: Due to the way the 
software release product and folders were structured, the tarball contains no 
Zope release tarballs/exe-files. The tarball URLs end up as folders containing 
the view templates swreleasefile_view and viewMD5.

jens


___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [ZWeb] zope.org move

2011-10-11 Thread Jens Vagelpohl

On Oct 11, 2011, at 15:45 , Jim Fulton wrote:

 If I can provide a new tar ball that contains just release files in
 folders, can you knit it into the static site?

I think the only way to make them available without breaking all internal links 
to these releases on the static site would be to put them separately and use 
Apache rewrite magic to try and catch any requests for the files themselves, 
which would always end in .../Zope-XXX.[tgz|exe|…]

jens



___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [ZWeb] zope.org move

2011-10-11 Thread Jens Vagelpohl

On Oct 11, 2011, at 16:53 , Jim Fulton wrote:

 On Tue, Oct 11, 2011 at 10:00 AM, Jens Vagelpohl j...@dataflake.org wrote:
 
 On Oct 11, 2011, at 15:45 , Jim Fulton wrote:
 
 If I can provide a new tar ball that contains just release files in
 folders, can you knit it into the static site?
 
 I think the only way to make them available without breaking all internal 
 links to these releases on the static site would be to put them separately 
 and use Apache rewrite magic to try and catch any requests for the files 
 themselves, which would always end in .../Zope-XXX.[tgz|exe|…]
 
 I think you can write a script that just replaces the goofy
 directories with the actual tar balls.

But that's not enough. The internal links on the static site point to items 
*past* the tarball filename, like 

XXX/Zope-2.12.0-final.tgz/swreleasefile_view. 

If I just replace what's currently a folder with the actual tarball I don't 
need to do any Apache magic and the file will be in the right place, but you 
cannot navigate to the release file from within the old.zope.org site anymore. 
The navigation links there will all break.

jens


___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [ZWeb] zope.org move

2011-10-11 Thread Jens Vagelpohl

On Oct 11, 2011, at 17:10 , Jim Fulton wrote:

 On Tue, Oct 11, 2011 at 11:05 AM, Jens Vagelpohl j...@dataflake.org wrote:
 But that's not enough. The internal links on the static site point to items 
 *past* the tarball filename, like
 
 XXX/Zope-2.12.0-final.tgz/swreleasefile_view.
 
 If I just replace what's currently a folder with the actual tarball I don't 
 need to do any Apache magic and the file will be in the right place, but you 
 cannot navigate to the release file from within the old.zope.org site 
 anymore. The navigation links there will all break.
 
 Can you give an example?

Go to http://old.zope.org/Products/Zope/2.11.4/ and notice the link URLs for 
the items Zope-2.11.4-final.tgz and Zope-2.11.4-win32.exe.


 Maybe we need to clean up those links.

Yes, that's another option.

jens



___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [ZWeb] zope.org move

2011-10-10 Thread Jens Vagelpohl
Hi Jim,

 Great. I have a 400MB tarball.  I put in ~zope on app2.zope.org. I assume you
 have access to that machine. If not, let me know where I should
 put it.
 
 As soon as you bring up a static old.zope.org (and switch dns, of course),
 I'll decommission the current machines.

I'll look at it over the next couple days. Thanks!

jens



___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [ZWeb] zope.org move

2011-10-10 Thread Jens Vagelpohl

On Oct 10, 2011, at 08:57 , Jens Vagelpohl wrote:

 Hi Jim,
 
 Great. I have a 400MB tarball.  I put in ~zope on app2.zope.org. I assume you
 have access to that machine. If not, let me know where I should
 put it.
 
 As soon as you bring up a static old.zope.org (and switch dns, of course),
 I'll decommission the current machines.
 
 I'll look at it over the next couple days. Thanks!

Hi Jim,

I've spent a little time looking at the files and doing some cleanup. It works, 
mostly. I've deployed it and changed DNS. Once the DNS change has propagated 
and there is no negative feedback the ZC-hosted version can go away.

Thanks for the tarball!

jens


___
Zope-web maillist  -  Zope-web@zope.org
https://mail.zope.org/mailman/listinfo/zope-web


Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-11 Thread Jens Vagelpohl

On Aug 11, 2011, at 21:10 , Hanno Schlichting wrote:

 On Sun, Aug 7, 2011 at 5:13 PM, Jens Vagelpohl j...@dataflake.org wrote:
 After the wrapping, the discussion item has the wrong path. Even though 
 self, the talkback object, has the correct path when calling 
 getPhysicalPath on it. I can't see anything overly stupid in the 
 DiscussionItem code, so there has to be an issue with that Zope 
 getPhysicalPath change. Reverting that one change in the current Zope trunk 
 fixes the tests.
 
 Thanks for the thorough analysis!
 
 I tracked this down to a missing aq_inner call in the new
 getPhysicalPath and fixed that.
 
 The ValueError: 'Access contents information' not found in inherited
 permissions failures remain, which are next on my list.

Thanks for taking the time, Hanno. I wouldn't have been able to figure than one 
out.

jens



___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-07 Thread Jens Vagelpohl

On Aug 7, 2011, at 07:00 , CMF tests summarizer wrote:
 
 [1]UNKNOWN FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk 
 Python-2.6.6 : Linux
   https://mail.zope.org/pipermail/cmf-tests/2011-August/015089.html

I have tried to pinpoint the reason for some of these test failures. Two of 
these tests are for the CMF Discussions functionality:

Failure in test test_deleteReplies 
(Products.CMFDefault.tests.test_Discussions.DiscussionTests)
Traceback (most recent call last):
  File /usr/local/lib/python2.6/unittest.py, line 279, in run
testMethod()
  File 
/usr/local/py26/cmf_trunk/src/Products.CMFDefault/Products/CMFDefault/tests/test_Discussions.py,
 line 301, in test_deleteReplies
self.assertEqual(len(ctool), 4)
  File /usr/local/lib/python2.6/unittest.py, line 350, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: 6 != 4

Failure in test test_itemCataloguing 
(Products.CMFDefault.tests.test_Discussions.DiscussionTests)
Traceback (most recent call last):
  File /usr/local/lib/python2.6/unittest.py, line 279, in run
testMethod()
  File 
/usr/local/py26/cmf_trunk/src/Products.CMFDefault/Products/CMFDefault/tests/test_Discussions.py,
 line 212, in test_itemCataloguing
% reply.getId()))
  File /usr/local/lib/python2.6/unittest.py, line 325, in failUnless
if not expr: raise self.failureException, msg
AssertionError

Those tests started failing after the following Zope-checkin:

http://svn.zope.org/?rev=122213view=rev

What ends up happening in both cases is discussion replies ending up with a 
wrong idea about their physical path. Normally, they all should have a physical 
path that points to the talkback discussion container object attached to the 
original content item that houses the discussion, like so:

/path/to/content/talkback/12345
/path/to/content/talkback/12346
/path/to/content/talkback/12347
…

All of a sudden a reply to a reply thinks it is stored not in the content 
object's talkback, but in a new talkback attached to the reply the user has 
replied to:

/path/to/content/talkback/12345
/path/to/content/talkback/12345/talkback/12346
/path/to/content/talkback/12345/talkback/12346/talkback/12347

The problem appears in CMFDefault.DiscussionItem.createReply on line 251, where 
the newly created discussion reply is aqcuisition-wrapped in the talkback 
object:

item = DiscussionItem( id, title=title, description=title )
self._container[id] = item
item = item.__of__(self)

After the wrapping, the discussion item has the wrong path. Even though self, 
the talkback object, has the correct path when calling getPhysicalPath on it. 
I can't see anything overly stupid in the DiscussionItem code, so there has to 
be an issue with that Zope getPhysicalPath change. Reverting that one change in 
the current Zope trunk fixes the tests.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-dev] direction

2011-07-06 Thread Jens Vagelpohl
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

2011-07-05 Thread Jens Vagelpohl
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

2011-06-29 Thread Jens Vagelpohl
-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

2011-06-29 Thread Jens Vagelpohl
-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

2011-06-29 Thread Jens Vagelpohl
-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)

2011-05-10 Thread Jens Vagelpohl
-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)

2011-05-10 Thread Jens Vagelpohl
-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)

2011-05-10 Thread Jens Vagelpohl
-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)

2011-05-10 Thread Jens Vagelpohl
-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?

2011-04-19 Thread Jens Vagelpohl
-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?

2011-04-19 Thread Jens Vagelpohl
-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-CMF] GenericSetup: Question on StackOverflow

2011-04-09 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 4/9/11 09:09 , Suresh V. wrote:
 Please see:
 
 http://stackoverflow.com/questions/5603459/genericsetup-what-does-toolset-xml-accomplish-if-toolinit-still-has-to-be-called
 
 I could not create a cmf tag, so if you can please add that to the 
 tags in the question.

Not sure what that site is or does, but the only forums regularly
visited and supported by the CMF developers are this mailing list and
Launchpad. If you would like to ask a question please use those.

jens

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2gFJgACgkQRAx5nvEhZLLKKQCaAkXibYIeDybeH1AxPbI/3tN1
DGkAn20pHJc8TtBWrE2COKxAt2V7vJzM
=gSwo
-END PGP SIGNATURE-
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] GenericSetup: Question on StackOverflow

2011-04-09 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 4/9/11 11:18 , Lennart Regebro wrote:
 On Sat, Apr 9, 2011 at 10:11, Jens Vagelpohl j...@dataflake.org wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 4/9/11 09:09 , Suresh V. wrote:
 Please see:

 http://stackoverflow.com/questions/5603459/genericsetup-what-does-toolset-xml-accomplish-if-toolinit-still-has-to-be-called

 I could not create a cmf tag, so if you can please add that to the
 tags in the question.
 Not sure what that site is or does, but the only forums regularly
 visited and supported by the CMF developers are this mailing list and
 Launchpad. If you would like to ask a question please use those.
 
 But there are some Plone people lurking there, and plone is a good
 tag. But mailing lists will probably be faster than SO for any kind of
 tool that isn't wildly popular.

IMHO it's not a metter of how popular a given tool is. It's a matter of
where the developers/supporters hang out and what channels they use for
accepting questions, bug reports or support requests. For the CMF that
means this list or the Launchpad sites for the various components.

If there's someone who wants to volunteer monitoring and answering
requests on a separate channel, like that website, that's fine. But
until that time people should be warned that posting requests somewhere
else may not yield any results.

jens

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2gJ1kACgkQRAx5nvEhZLJgRQCdE32TMDT4wUvmUM6jEm/mK1H/
OWYAnRzTuV6BvZV4VePRJ2NFmNh1QxKj
=h/BQ
-END PGP SIGNATURE-
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-dev] New test summarizer format

2011-04-04 Thread Jens Vagelpohl
-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

2011-04-04 Thread Jens Vagelpohl
-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

2011-04-03 Thread Jens Vagelpohl
-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-CMF] Versions found on pypi but not in svn tags

2011-04-02 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 4/2/11 12:15 , Suresh V. wrote:
 How come the following versions are not found in svn tags?
 
 Products.CMFCore: Versions 2.2.1, 2.2.2, 2.2.3

I have no idea where you are looking, but those tags exist. See
http://svn.zope.org/Products.CMFCore/tags/ or
http://svn.zope.org/repos/main/Products.CMFCore/tags/.

jens

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk2W+0oACgkQRAx5nvEhZLKGpgCeI5hVINfSQfPaXoveT6dJMqHB
eJgAnjRSU4OmUG8R5d+ZfoBxwV+UQG6Q
=2NCy
-END PGP SIGNATURE-
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope] Forcing zope to preload objects in cache

2011-02-08 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2/8/11 12:11 , Marco Bizzarri wrote:
 I'd like to force Zope to reload the cache; of course, I could access
 various pages using a wget or something liket that; but how can I force Zope
 to 'fill' all connections, and just one?

Fire off several concurrent requests?

jens

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAk1RVNsACgkQRAx5nvEhZLKuOQCgsLbWaXqH83bBL6UQjFE1iJC/
+fEAnAkAYc57k7KOs+DP+hBsPY6ZCKh/
=ABvX
-END PGP SIGNATURE-
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope] Monkey patch for BLOB support in OFS.Image Images and Files

2011-01-08 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 1/7/11 22:28 , William Heymann wrote:
 I have a monkey patch here that I would like comments on it and to see how it 
 works for others.

Hi William,

A huge monkey patch like that makes it very hard to compare it with the
original implementation and see the actual changes. You could help the
review *greatly* by providing a diff to the original implementation
instead, and post that to the Zope bug tracker on Launchpad:

https://bugs.launchpad.net/zope2

jens

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAk0oQ1kACgkQRAx5nvEhZLJk5gCgtnVBC7XF6PbOlOf1NPr6Ge70
gZoAn3VM6J8ecvLvXZzlFP55LQ4/Szr6
=Bfle
-END PGP SIGNATURE-
___
Zope maillist  -  Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope-dev )


Re: [Zope-dev] Draft of new aggregator

2010-12-01 Thread Jens Vagelpohl
-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

2010-12-01 Thread Jens Vagelpohl
-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

2010-11-30 Thread Jens Vagelpohl
-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

2010-11-30 Thread Jens Vagelpohl
-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 )


  1   2   3   4   5   6   7   8   9   10   >