[ZF] manuel access

Tres Seaver tseaver at palladion.com
Wed Feb 20 15:58:15 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/20/2013 10:55 AM, Jim Fulton wrote:
> On Wed, Feb 20, 2013 at 10:42 AM, Tres Seaver <tseaver at palladion.com>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 02/20/2013 09:49 AM, Benji York wrote:
>>> On Wed, Feb 20, 2013 at 8:31 AM, Chris Withers 
>>> <chris at simplistix.co.uk> wrote:
>>>> On 20/02/2013 14:18, Jim Fulton wrote:
>>>>> I think there should be a process for moving projects out of
>>>>> the ZF.
>>>> 
>>>> For this one, can I suggest the following lightweight process:
>>>> 
>>>> Benji forks from the zopefoundation repo on GitHub.
>>>> 
>>>> Someone from Zope Foundation (Stefan?) then does a commit in
>>>> the zopefoundation GitHub repo that deletes all files on master
>>>> and replaces with a README.txt pointing to Benji's fork.
>>>> 
>>>> Work then happens in Benji's repo going forward, and he controls
>>>> who has access to what.
>>> 
>>> That sounds like a reasonable plan that, as far as I can tell, 
>>> accounts for the legalities involved.  I.e., the ZF has the code
>>> but doesn't want it any more and I "fork" the project and
>>> continue development.
>> 
>> Go ahead with the fork.  We will vote to approve the separation at 
>> Thursday's board meeting.
> 
> Is approval required?  I don't think the ZF can prevent forks, given
> the ZPL.
> 
> OTOH, Jen's raised some valid concerns last August about the 
> representation of the ZF's interest in forks.  I'd like to see this
> clarified.

I meant to have the board approve the removal of the code, not the fork.
 Since the code was checked in under a contributor agreement, the
Foundation has joint ownership of the copyright:  effectively, we will be
abandoning that interest.


Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlEk8pcACgkQ+gerLs4ltQ4M4wCfUgxsjM03kkEhSEI/37CGZR0T
EbUAniSXDsUR48W5rRD4ozIDyohmPu9F
=oR+T
-----END PGP SIGNATURE-----


More information about the foundation mailing list