[Zope3-dev] Package is the wrong name for the things I called "Zope Packages".

[seb bacon]

Shane Hathaway wrote:
> seb bacon wrote:

> As I understand it, when end users install a collection of software, 
> they don't get a 'C', they get a 'B'.  In that light, should 'B' be 
> called a "closed workspace"?  Do we want to emphasize the user's ability 
> to change the collection of software?

I don't like 'closed workspace,' though I'm not sure why.  But I *do* 
like 'workspace' generally.  I don't see a need to emphasise the fact 
that you can customize the software collection, because in most 
applications for most people, they will install a "bundle" and customise 
it using a customised UI, I would think.

Why do we need to 'close' a workspace at all?  Is it just a state which 
indicates that the source is pristine or of a release standard?

Here are some combinations of ideas so far:

=========================================
Distribution-type  | Development-type
=========================================
Closed Zope package| Open Zope package
Bundle             | Workspace
Locked workspace   | (Unlocked) Workspace
Closed workspace   | (Open) workspace
Closed bundle      | (Open) bundle
Bundle             | Customized bundle
Workspace          | Customized workspace
Released workspace | Development workspace
-------------------------------------------

>> I don't like "Persistent Package" and "Persistent Module" because they 
>> are too ZODB-developer-centric.  Ideally a TTW developer should not 
>> need to know what persistence is.  I would prefer "Zope Package" and 
>> "Zope Module".  But I suspect I might be alone in that ;-)
> 
> 
> I think you are. :-)  Persistent modules are merely Python modules in 
> the database.  Actually, in the UI I think we'd only reveal the modules, 
> and we'd just call them modules, not persistent modules.

OK.  If in the UI they are called modules, I'm happy - I just object to 
introducing newbies to words like 'persistence' earler than is necessary.

>> Finally, why is everyone ducking when the word "Product" is mentioned? 
>> It has the benefit of already meaning something to most Zope users.

> Because it means different things to every Zope user.  

Really?  I would be suprised if much of the installed user base thinks 
of a "product" as anything other than "an optional piece of software you 
download and install which makes Zope do useful stuff"

 > It would muddy any attempt to clarify Zope 3 packaging.

Conversely, we must be careful in our zeal to clarigy not to alienate Z2 
users by completely eradicating names they have got used to..?

seb