Organizing work as a team
=========================
[bootc]
- Welcome Nobu and Kazu!
- use BTS ownership to track people working on bugs (owner/noowner commands)
- use salsa for issue/MR tracking / assingning work BUT try not to overlap BTS; use task owners while actively working on things, solicit feedback via comments etc...
- remind me (bootc specifically) about and then steal my things if it looks like I've abandoned something; I'm more likely to react to mail directly to me or IRC than bugs or Salsa issues
- maybe split from debian-boot? defer until we've stabilised things
- a stretch point release is a TODO, axhn currently owns


Open tasks
==========
- stretch point release (axhn)
- BTS triage
- Salsa MRs
- kFreeBSD / hurd support?
- convert to gbp repo layout?
  - current layout is not too different to gbp patches-unapplied layout
  - axhn to describe his packaging practices
  - axhn to look at gbp docs to see if it can be configured in a similar way
  - question in particular is about how the upstream branch is managed (e.g. commit vs upstream based)
  - bootc to propose a way to make it happen

New ideas
=========
- separate initramfs package(same as Ubuntu)?
  -- https://launchpad.net/ubuntu/+source/busybox
- co-installability of various flavours?
- "-full" flavour with everything switched on?
- ship busybox configs in the packages, like the kernel does?
- enable Salsa-CI pipelines (depends on gbp repo layout)?