Jump to: navigation, search

Difference between revisions of "Meetings/diskimage-builder"

(Long Term Topics: Remove pylint (which was already merged) and resorted list.)
(next meetings dates)
Line 4: Line 4:
  
 
'''MEETING TIME: Every other Thursday 20:00 UTC (#openstack-meeting)'''
 
'''MEETING TIME: Every other Thursday 20:00 UTC (#openstack-meeting)'''
 +
 +
Logs, ICS file, etc see [http://eavesdrop.openstack.org/#Diskimage_Builder_Team_Meeting]
  
 
= Next Meeting Dates =
 
= Next Meeting Dates =
  
* June 1st (Thursday) 2000 UTC, <code>#openstack-meeting</code> (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170601T200000)
+
Meetings are held in <code>#openstack-meeting</code>
 +
 
 +
Meetings alternate between 20:00 and 15:00 UTC
 +
 
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170629T200000 June 29 2017 20:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170713T150000 July 13 2017 15:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170727T200000 July 27 2017 20:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170810T200000 August 10 2017 15:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170824T150000 August 24 2017 20:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170910T200000 September 07 2017 15:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170921T150000 September 21 2017 20:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20171005T200000 October 05 2017 15:00]
 +
* [http://www.timeanddate.com/worldclock/fixedtime.html?iso=20171019T150000 October 19 2017 20:00]
  
 
== Agenda for next meeting ==
 
== Agenda for next meeting ==
Line 28: Line 42:
 
* Internal vs. external caching: there is *some* code that (tries) to handle caching. Is this still worth it in times of squid / apt-cacher-ng? (andreas-f)
 
* Internal vs. external caching: there is *some* code that (tries) to handle caching. Is this still worth it in times of squid / apt-cacher-ng? (andreas-f)
 
* DIB 3.0: feature list
 
* DIB 3.0: feature list
 
== Agenda from previous meeting (2016-11-10) ==
 
 
* images for CI (ianw 13/10)
 
* ansible patch (ianw 13/10)
 
 
* Bugs process
 
** Do we want to continue using launchpad for bugs? If so, this needs cleanup.
 
** Do we want to add a bugs section to our regular meetings?
 
 
* Dib 2.0
 
** We have a feature branch!
 
** Should we cut an RC?
 
 
* Open Discussion
 
  
 
= Previous meetings =
 
= Previous meetings =
 
2016: http://eavesdrop.openstack.org/meetings/diskimage_builder/2016/
 
2016: http://eavesdrop.openstack.org/meetings/diskimage_builder/2016/

Revision as of 23:39, 27 June 2017

Diskimage Builder

This is the bi-weekly meeting for those interested in Diskimage Builder!

MEETING TIME: Every other Thursday 20:00 UTC (#openstack-meeting)

Logs, ICS file, etc see [1]

Next Meeting Dates

Meetings are held in #openstack-meeting

Meetings alternate between 20:00 and 15:00 UTC

Agenda for next meeting

Please edit this page to add items to the next meeting agenda.

  • TBD

Long Term Topics

There are a couple of long term topics we should / want to discuss. They can be discussed when the daily business topics are done.

  • UEFI boot: the never ending story. How to cope with the situation here? (andreas-f)
  • Refactoring of elements: having a new structure for at least Ubuntu and Debian specific elements. Currently there is a lot duplication. (andreas-f)
  • *-nano elements for minimalist docker images? (andreas-f)
  • Cleanup patches? (currently about 110 open) (andreas-f)
  • DIB vs. bindep vs. instack vs. *-puppet: Functional overlap. Is there the need to support them all? Can we possible merge some of them? (andreas-f)
  • Local vs. CI testing: (docker / vm) matrix build. Double work or step forward? (andreas-f)
  • python vs. bash: should we start refactoring bash code in python (maybe reusing the instack approach)? (andreas-f)
  • (python) replacement of dib-run-parts? (andreas-f)
  • Internal vs. external caching: there is *some* code that (tries) to handle caching. Is this still worth it in times of squid / apt-cacher-ng? (andreas-f)
  • DIB 3.0: feature list

Previous meetings

2016: http://eavesdrop.openstack.org/meetings/diskimage_builder/2016/