[Container-tools] Agenda (tentative) for Brno f2f meeting next week

[Josef Stribny]

On Thu, Sep 24, 2015 at 1:22 PM, Brian (bex) Exelbierd <bex at pobox.com> 
wrote:
> On 09/22/2015 07:44 AM, Daniel Veillard wrote:
>> 
>>                    Agenda for Brno f2f meeting
>> 
>>   Tentative version, I may have forgotten something, we may be able 
>> to
>> reorganize some of it on the fly especially using Thur afternoon.
>>   Note that there is a bit of preparation for everybody, please be 
>> ready
>> to provide a status and give demo of what you have been working on,
>> and reply to provide suggestion on lightning talks for Tuesday 
>> afternoon.
>>   If we are to make a lunch and learn about the CDK who think he can 
>> do
>> the presentation ?
>> 
>> Tuesday 29
>> 
>> Start 9am
>>    Morning: status and demos
>>      - round around the table, introduction
>>      - what are we working on what is the current status
>>        ideally presentation of recent work, like doing demo
>>        (please send prerequisite in advance so people can
>>         try to have their laptop ready), we should have
>>        a couple of MacBook in the room for those who own one.
>> 
>>        + the CDK, vagrant, o-m-v, VMWare
>>        + some of the new nulecule packages
>>        + the new work on providers
>>        + v2c status/demo
>>        + Eclipse integration
>>        + current status on OpenShift
>>        + features on the work for beta3
>> 
>>    Afternoon:
>>      - developments for nulecule and atomicapp
>>        + in-depth review of the set of trello card
>>          suggest to start with nulecule, then atomicapp
>>        + status for beta3 items
>>        + status for the golang implementation (Dan Walsh, BlueJeans 
>> ?)
>>      - Open Discussion room for development:
>>        + pick topics, possibly make a couple of slides 10-15mn each,
>>             think of a lightning talk session format
>>        + DV: buddy work system, assign a couple of person on each
>>              category, e.g. Dusty and Ian on the developper pipeline,
>> 	    Navid and Charlie on tests, ...
>>        + DV: webifying our code, more read-only, keeping the base 
>> URL for
>>              artifacts, doing URI computations for relative resources
>>        + add your suggestions
> 
> One possible development option (that Navid may be able to speak to 
> in my absence) is to devote some effort to improving the 
> vagrant-libvirt module.  It has some missing functionality and 
> "hacky" implementation compared to VirtualBox.  If we want to be 
> serious about supporting to libvirt we may need to help out here.
> 
> Also, we may want to talk about additional helpers/tooling for 
> Vagrant.  One thing that comes to mind is that it appears (though I 
> am still researching) that you cannot easily package a sample 
> Vagrantfile with a box.  This means that users of the ADB have to 
> either go to a separate place for a file or manually enable the 
> exposure of the docker daemon. Should we discover if there are more 
> of these challenges and write an `atomic` for vagrant?
> 


What do you mean by including a sample Vagrantfile? A one that ships 
with the box itself (that's possible)? Or the one generated on 'vagrant 
init'?

Regards
Josef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/container-tools/attachments/20150925/1d12c295/attachment.htm>