GitHub

Planning Meetings

Public planning meetings are held biweekly on odd calendar weeks from 14:00 to 14:30 on Microsoft Teams. The purpose is to provide an overview of our current projects and priorities, as well as to discuss new topics and issues within the group.

Our development planning board can be found on GitHub.

You can use this link to join. If you want to get an invitation to the event, please drop us a line on our Slack channel.

Planning meetings are currently not recorded. The meetings are held either in English or German depending on the attendees.

Info

Note that anyone can contribute to metal-stack without participating in planning meetings. However, if you want to speed up the review process for your requirements, it might be helpful to attend the meetings.

Agenda

Here is the agenda that we generally want to follow in a planning meeting:

  • Possibility to bring up news that are interesting for every developer of the metal-stack org
  • Check Done column and archive cards
    • Attendees have the chance to briefly present achievements if they want
  • Check the In Progress column and discuss whether these tasks are still worked on, there were significant blockers or they can be lower-prioritized
  • Check new issues labelled with triage and prioritize them
  • Allow attendees to bring up issues and prioritize them
    • Attendees have the chance to briefly present these new issues

Idea Backlog

The backlog contains ideas of what could become part of the roadmap in the future. The list is ordered alphabetically. Therefore, the order does not express the importance or weight of a backlog item.

We incorporate community feedback into the roadmap. If you think that important points are missing in the backlog, please share your ideas with us. We have a Slack channel. Please check out metal-stack.io for contact information.

Danger

By no means this list is a promise of what is being worked on in the near future. It is just a summary of ideas that was agreed on to be "nice to have". It is up to the investors, maintainers and the community to choose topics from this list and to implement them or to remove them from the list.

  • Add metal-stack to Gardener conformance test grid
  • Autoscaler for metal control plane components
  • CI dashboard and public integration testing
  • Improved release and deploy processes (GitOps, Spinnaker, Flux)
  • Machine internet without firewalls
  • metal-stack dashboard (UI)
  • Offer our metal-stack extensions as enterprise products (accounting, cluster-api, S3) (neither of them will ever be required for running metal-stack, they just add extra value for certain enterprises)
  • Partition managed by Kubernetes (with Kubelets joining the control plane cluster)
  • Public offering / demo playground