[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Snaps sub-project
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Thu, 16 Dec 2010 16:02:56 +0000
- Delivered-to: email@example.com
Snaps runs on top of Virgo. Snaps directly references plenty of third-party dependencies such as Spring framework.
On 16 Dec 2010, at 15:51, Wayne Beaton wrote:
> What is the nature of the relationship between Snaps and Virgo? Does
> Snaps "run on top of" Virgo? What third-party libraries from Virgo does
> Snaps directly reference?
> On 12/16/2010 10:15 AM, Dmitry Sklyut wrote:
>> The weight of extra administrative work kills an idea of subproject.
>> Would snaps still be able to have a releases outside of web-server release
>> On Thu, Dec 16, 2010 at 9:55 AM, Glyn Normington <gnormington@xxxxxxxxxx>wrote:
>>> I took an action at the Virgo F2F to explore the cost associated with
>>> making snaps a subproject of Virgo. Unfortunately, it seems that
>>> sub-projects cannot inherit IP records such as CQs from their parent
>>> projects, so I think the extra work would be significant. We would have to
>>> raise and maintain a bunch of piggy-back CQs for a snaps subproject.
>>> I'm not convinced the benefits are worth the cost. Dmitry is now a full
>>> Virgo committer so snaps is already in better shape than we were at the F2F.
>>> So I propose that we do not explore a snaps sub-project further. Anyone
>>> feel we should?
>>> virgo-dev mailing list
>> virgo-dev mailing list
> virgo-dev mailing list