Hi list:

After following the install process for Convirt 2.0 community version (plus 
patch bundle 1 and some "glitches" with regards of me using a Debian "Lenny" 
server) my test enviro works more or less OK.

But while it seems quite OK for a test environment it seems not so good for a 
production one.  Some questions rise:

1) Is there any FAQ, Howto, etc. with regards of "properly" start convirt 
daemon-mode? i.e.: using apache plus mod_wsgi; not using paster 
with "development.ini"; not having such strong dependencies on environment 
variables but config entries, etc.

2) Install: current install procedures depend heavily on gaining access to the 
Internet and downloading quite a lot of Python modules which may or may not 
be reachable at the moment of installation, pushed forward to a new version, 
etc. all of this on its own tg2env which may or may not be shareable with 
other apps in the box.

3) Upgrade and promotion: is there any outlined protocol for proper upgrade? 
i.e.: upgrading from 0.x to 2.x is a matter of "start anew"; current patch 
policy is cummulative; what will happen when/if you produce a future "patch 
bundle 2"? will it be "pushable" on top of a patch bundle 1 + some patches?  
Will it be a proper migration path from 2.0 to a future 2.1?

4) Feature cutting: on previous releases command line access was avaliable 
while for 2.0, ACLs, command line and programmatic remote access (by means of 
XML-RPC) have been "pushed away" to the "enterprise version" (even more, it 
seems to be a 'post-facto' decision at the view of some "remainders" about 
ACLs and command line on current community code-base), which regreatably 
doesn't offer much confidence to us, third parties, in order to make a strong 
involvement with the tool: no one wants to be "locked in" with a tool less 
and less featured where more and more production-grade features move away to 
a pay-only (and not cheap, by the way) version.

5) End user/distribution license for "enterprise version".  Is it known under 
what license will be the "enterprise version" distributed?  By the fact that 
you ask for giving non-exclusive rights with any patch that any third-party 
could develop it seems obvious that you expect to distribute under a 
double-license model, more probably with the "enterprise versions" being 
under a closed one.  Will this be the case?  Don't you expect this to refrain 
third parties from sharing development with you?


ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
XenMan-Users mailing list

Reply via email to