Jan Bronicki

Hey everyone, I’ve just renamed the default branches and merged the PRs for the following repositories: mayday – https://github.com/flatcar/mayday/pull/16 flatcar-cloud-image-uploader – https://github.com/flatcar/flatcar-cloud-image-uploader/pull/25 flatcar-release-mirror flatcar-packer-qemu However, I don’t have the necessary...

List of to be archived repos so far (this list was compiled semi-automatically so it needs review): ~~- [ ] https://github.com/flatcar/torcx~~ ~~- [ ] https://github.com/flatcar/sysroot-wrappers~~ ~~- [ ] https://github.com/flatcar/go-omaha~~ -...

Thanks for confirming that guys! Any ideas about go-omaha and sdnotify-proxy?

In september the LTS versions that use some of those old repos will not be supported, this is a good time to go back to trying to archive deprecated repos

> Should https://github.com/flatcar/go-omaha be archived? This seems to still be heavily utilized by Nebraska? Yep, it shouldn't

- Making sure all repos have proper permissions set - Adding to CNCF service - https://github.com/cncf/foundation/ - create a pull request (similar to https://github.com/cncf/foundation/pull/1075) - Adding to the flatcar-maintainers group...

Add access to meet.flatcar and to the calendar

Assign to various maintainer PR groups (depends on the person) such as flatcar-ci. nebraska-maintainers etc...

https://calendar.google.com/calendar/ical/c_ii991mqrpta9en8o7ofd4v19g4%40group.calendar.google.com/public/basic.ics Add the Flatcar calendar to yours (the link not the file)

https://docs.google.com/document/d/1canF8URl5LsdcvwoE0823O2we6wJxHtcDTbmmubmTew/edit?pli=1&authuser=2 Shouldnt all new maintainers have access to this? from: https://github.com/flatcar/flatcar-linux-infra#:~:text=Please%20refer%20to%20Kinvolk%20Change%20Management%20procedure.