[Zope-dev] Help updating the copyright attributions

[Christian Theune]

On 06/03/2010 04:12 PM, Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jan-Wijbrand Kolman wrote:
>> On 6/3/10 8:40 AM, Christian Theune wrote:
>>> On 06/02/2010 05:19 PM, Tres Seaver wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Jan-Wijbrand Kolman wrote:
>>>>> On 6/2/10 15:11 , Christian Theune wrote:
>>>>>> Hi,
>>>>>>
>>>>>> the ZF needs to finish updating the copyright attributions to state that
>>>>>> the Zope code now belongs to the foundation.
>>>>>>
>>>>>> I've prepared some scripts to help with monitoring which packages need
>>>>>> to be updated and also a helper to update most cases.
>>>>> Can you point me to these scripts?
>>>>     $ svn co svn+ssh://svn.zope.org/repos/main/zope.repositorypolicy/trunk\
>>>>       ~/projects/Zope/zrp
>>>>     $ cd zrp
>>>>     $ /opt/Python-2.6.5/bin/python bootstrap.py&&    bin/buildout
>>>>     $ cd /path/to/other/project
>>>>     $ ~/projects/Zope/zrp/bin/zope-org-check-project
>>>>     ...
>>>>     $ ~/projects/Zope/zrp/bin/zope-org-fix-project
>>>>     ...
>>>>     $ ~/projects/Zope/zrp/bin/zope-org-check-project
>>>>     (should be empty)
>>>>     $ bin/test -v --all
>>>>     $ svn add LICENSE.txt COPYRIGHT.txt
>>>>     $ svn commit -m "Conform to repository policy."
>>> How do you deal with packages that have broken tests due to broken
>>> dependencies?
>>
>> I had z3c.recipe.paster with failing tests. These failed both before and
>> after the copyright-fix. So, assumed I could go ahead with the copyright
>> fix itself.
>>
>> I do want to help out on the important copyright fixing, but I do not
>> have the time right now to also fix each of the packages that I come across.
>>
>> Maybe we could/should make note of the broken packages somewhere.
>
> Perhaps if the package's tests are broken before the cleanup, we should
> leave the cleanup un-done.  We defeinitely want to isolate the
> "abandoned" projects into a separate list, so leaving them in the
> nightly nag-mail list helps keep them on the radar for that.

Hmm. With the goal of getting the copyright attributions up do date as 
soon as possible, I think running the tests is a good sanity check. If 
the same (amount of) tests fail after the fix as before, then I'd go ahead.

I agree we should track abandoned projects, though, but I'd separate 
that issue from the (C) update. This needs to get to a point where we 
can talk about the whole repository and say "it's been updated".

Christian

-- 
Christian Theune · ct at 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