[Container-tools] Creating a download location for ADB Vagrant boxes

[Brian (bex) Exelbierd]

On 10/14/2015 05:28 PM, Lalatendu Mohanty wrote:
> However I think having a separate download location for upstream ADB
> will help in agility of upstream of ADB. For example if we want to
> produce something  which is not ready for the CentOS community (Or SIG)
> we can host it on the ADB download location .

I think this plus KB's comments about target audience are spot on. 
Perhaps we should think of this in layers, like we do with many other 
community projects

Project Atomic - Hosts the development of the adb which produces 
nightlies or another rapidly iterating version and occasionally pushes 
an X.Y release that they consider to be stable.

CentOS/Fedora/Distro du Jour - Hosts their rebuild of the ADB.  This 
could be a direct rebuild, however I think it will most likely be a 
value-add.  For example, the CentOS Atomic SIG could rebuild the latest 
stable ADB from Project Atomic and add a base CentOS docker image to the 
package to encourage the ongoing ecosystem's usage.  Fedora might 
rebuild everything from Fedora code bases.

RHEL/etc. - derive and rebuild/reconfigure as desired from their distro 
of choice.

This will require that Project Atomic get a hosting infrastructure, even 
if the CBS remains the build engine of choice.  I think this also makes 
the story cleaner and easier to tell from each of the communities.

Opinions?

regards,

bex