[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] draft of Every-two-week Fedora Atomic Host change proposal
- From: Nick Coghlan <ncoghlan gmail com>
- To: James <purpleidea gmail com>
- Cc: "atomic-devel projectatomic io" <atomic-devel projectatomic io>
- Subject: Re: [atomic-devel] draft of Every-two-week Fedora Atomic Host change proposal
- Date: Wed, 17 Jun 2015 20:50:15 +1000
On 17 June 2015 at 18:11, James <purpleidea gmail com> wrote:
> Another perspective is this: I think I'm a fairly advanced Vagrant
> user, and this tool helps *me* get things done faster, better, etc...
> It was initially built to scratch an itch. Others are welcome to join
> the party.
That's fine, but OMV represents an extra dependency that isn't going
to help reach some of the audiences we want to be able to reach (e.g.
folks like me that have decided to get started with Vagrant based on
the standard tutorials and the plethora of Vagrantfile examples that
are out there, and folks that already have their own ways of working
with Vagrant).
OMV's declarative configuration approach is a valuable option for
folks to have available, but it can't be the *only* way of working
with Vagrant that we support. As a result, our default instructions
should assume imperative Vagrantfiles, since those can then be mapped
to OMV the same way any other configuration settings get mapped.
Regards.
Nick.
--
Nick Coghlan | ncoghlan gmail com | Brisbane, Australia
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]