[Zope3-dev] Re: More in zope.app: securitypolicy and wiki

[Martijn Faassen]

Jim Fulton wrote:

> Martijn Faassen wrote:
>
>> I think actually this confusion is good evidence we need another 
>> repository where people can freely hack away,
>> away from the Zope 3 repository. This way people won't even get a 
>> faint impression whatever is in this other repository is part of the 
>> 'core'. 
>
>
> I don't agree.  We had a separate respository in the past, and that 
> merely led to dead products.  Of course, when Zope 3 stops changing so 
> fast, this will become less of an issue.
>
Yes, Zope 3 changing fast makes developing separate products difficult.

Anyway, saying you had a separate repository in the past is not true. 
This was all happening in the Zope 3 CVS repository, which has a 
particular set of restrictions and policies before you can check in. I'm 
not complaining about this, but I think an alternative will be useful 
for extension developers.

> I think that this confusion will be reduced by having package meta 
> data that shows a packages's status.  Fred is working this out now.

I still think a separate repository for extensions makes sense, where 
people can freely hack away without worrying about it being core or not. 
A repository with relaxed guidelines over who can participate makes it 
easier for people to just jump in. They don't have to worry about 
getting into the hair of Zope 3 core developers at all.

Anything that gets checked into the Zope 3 tree will at some level 
affect Zope 3 core developers -- possibly failing unit tests and CVS 
checkin messages if nothing else. Anything checked into this Zope 3 tree 
is treated as something that in some way gets maintained together with 
Zope 3, I last heard, too.

Of course the plans to make the new repository a subversion repository 
will raise this barrier to participation a bit again, but I hope it 
won't be too much.

Regards,

Martijn