On Monday 20 February 2006 20:09, Andrew Milton wrote:
> So in order to even get your Open Source package LISTED, you have to sign
> over the rights of your code to Zope Corp (currently, Zope Foundation
> later), and then check it into the svn respository.
> Is this is correct?
NO! ABSOLUTELY NOT!
The ZSCP is totally disconnected from the Common Repository. Note that the
ZSCP does not talk about any repositories or technical implementation. It
only talks about the certification goals, requirements and data.
> So you're proposing that the Zope Foundation will not
> even mention other Open Source code that isn't actually owned and
> controlled by the Zope Foundation?
Huh? Where did you get this idea from? Did you actually read the proposal?
> Having a standard Zope package format would be far far more useful to the
> users at large, along with the associated tools (so developers can create
> compliant zope packages, and users can install packages actually using
> Zope). Packaging tools can then enforce certain restrictions automatically
> and create a manifest.
We cannot require something that we do not have. Thus I did not address
packaging or strong dependency meta-data in the proposal. I think once we
investigated eggs and have some initial implementation, the proposal will be
updated in light of this.
> If you had that, then that would certainly ease adding 'stuff' to the
> 'certified' repository, getting to LISTED level would be automatic.
Becoming listed will be a nearly automated process. Also receiving level 1 and
2 will be quick decisions. This is clearly stated in section 2.8.
I have added a questions to the Q&A section clearly stating that the ZSCP does
not require packages in the Common Repository.
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
Zope3-users mailing list