Re: [Zope-dev] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
Hi, On 04/09/2010 07:38 PM, Zvezdan Petkovic wrote: On Apr 9, 2010, at 10:57 AM, Fred Drake wrote: On Fri, Apr 9, 2010 at 10:43 AM, Tres Seavertsea...@palladion.com wrote: It seems reasonable to me that it *should* work, though I'm not sure how to write the code which tests that. See my later follow-up as well. In particular, while it *may* be reasonable to set the ZF as maintainer, it's not clear that it's the right thing either. Why shouldn't some Grok Team be listed as the maintainer for the grok packages, with an appropriate email? That seems preferable to me. I think the *right* thing to do is update the copyrights to reflect the copyright ownership, but not to otherwise change package metadata. Why was the check for author even included in the checker/fixer scripts? Can you point us to the Zope Foundation bylaws or a policy document that requires this? I cannot find this in a contributor agreement. Pondering it this is an overzealous misunderstanding on my part. I'm removing the assertion. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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: ZConfig/trunk/setup.py correct metadata: I really did write this.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fred Drake wrote: Log message for revision 110702: correct metadata: I really did write this. Setting the ZF as maintainer appears sufficient to appease the policy checker. Hmm, that doesn't work for me: $ svn co $ZSVN/ZConfig/trunk ZConfig $ cd ZConfig $ ../zope.repositorypolicy/bin/zope-org-check-project . setup.py: author not declared as Zope Foundation and Contributors \ (found: Fred L. Drake, Jr.) It seems reasonable to me that it *should* work, though I'm not sure how to write the code which tests that. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku/PP8ACgkQ+gerLs4ltQ4lFwCgzVbximbdm3lLwLkBTNhI+nzK GjEAnRZQAXCcVPQce8UDI1K59ZZLUodn =Tunh -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] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Fri, Apr 9, 2010 at 10:43 AM, Tres Seaver tsea...@palladion.com wrote: It seems reasonable to me that it *should* work, though I'm not sure how to write the code which tests that. See my later follow-up as well. In particular, while it *may* be reasonable to set the ZF as maintainer, it's not clear that it's the right thing either. Why shouldn't some Grok Team be listed as the maintainer for the grok packages, with an appropriate email? That seems preferable to me. I think the *right* thing to do is update the copyrights to reflect the copyright ownership, but not to otherwise change package metadata. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Fri, Apr 9, 2010 at 10:57 AM, Fred Drake fdr...@gmail.com wrote: I think the *right* thing to do is update the copyrights to reflect the copyright ownership, but not to otherwise change package metadata. +1 -- Benji York ___ 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: ZConfig/trunk/setup.py correct metadata: I really did write this.
On Apr 9, 2010, at 10:57 AM, Fred Drake wrote: On Fri, Apr 9, 2010 at 10:43 AM, Tres Seaver tsea...@palladion.com wrote: It seems reasonable to me that it *should* work, though I'm not sure how to write the code which tests that. See my later follow-up as well. In particular, while it *may* be reasonable to set the ZF as maintainer, it's not clear that it's the right thing either. Why shouldn't some Grok Team be listed as the maintainer for the grok packages, with an appropriate email? That seems preferable to me. I think the *right* thing to do is update the copyrights to reflect the copyright ownership, but not to otherwise change package metadata. Why was the check for author even included in the checker/fixer scripts? Can you point us to the Zope Foundation bylaws or a policy document that requires this? I cannot find this in a contributor agreement. Zvezdan ___ 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 )
