[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[provisioning-dev] Provisioning going forward
- From: "Philippe Ombredanne" <pombredanne@xxxxxxxxx>
- Date: Tue, 17 Apr 2007 10:50:50 -0700
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:reply-to:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:importance; b=eVYw4GcMsn2v9VHvEGpjgDDVVIQc6eAm3K/S62n0vCVGaBHYzQJZeGG/mYfoXIBgnIRMe0fXnc2w9EzEZRs8tuIvJztLK6fS2BHPPXnPv2Bwq0Hnr64MGaobkbFasE9bl82man5aFTE3mzTV4YyTTkqVPyVxs+KlKP6aPMp2wBI=
- Importance: Normal
I could not join the provisioning workshop last week, so I did read all
the posts I could find and here is how I have reformulated the
conclusion for me:
- Equinox is the way to go for provisioning and will be the core
platform way. Everyone will contribute and/or migrate to that.
- Maya does address some specific use cases and provides a non
Equinox-based solution for now, but will also migrate to Equinox
provisioning in a near future, and have specific use cases for Equinox.
So we all need to focus and concentrate our energies behind Equinox,
since it will be lowest common denominator.
http://easyeclipse.org - http://phpeclipse.net - http://eclipse.org/atf
philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com
nexB - Open by Design (tm) - http://www.nexb.com