Archive fleetdm/fleet-infra

[mikermcneil]

Goal

Fleet uses as few repos as possible:

• fleetdm/fleet
• fleetdm/confidential
• fleetdm/classified

Infrastructure code and config are OK to exist at the confidential access level at Fleet, so fleetdm/fleet-infra can be archived and its contents (and any integrations pointing to it) can move to fleetdm/confidential instead.

Definition of done

• Archive fleetdm/fleet-infra
• Move content and integrations to fleetdm/confidential instead
  • Update CODEOWNERS file in fleetdm/confidential to reflect new stuff.
  • Update website/config/custom.js in fleetdm/fleet to reflect new stuff in fleetdm/confidential. (Check that file and give it a read first, will probably make sense, but check w/ eashaw or mikermcneil if unsure)
• Update any mentions of fleetdm/fleet-infra in the handbook, in the docs, and in the fleetdm/fleet-infra repo itself.
  • Here's an easy way to search docs, handbook, and issue templates.
• Anything I'm forgetting?

More context

When possible, can you switch to using fleetdm/confidential and archive fleetdm/fleet-infra? 🙇

Robert Fairburn
30 minutes ago
Looks like that got me set for now. I'll talk with everyone about getting that moved. We might be able to bulk move it all and sub it under an infrastructure path in confidential to start. From there we could analyze what actually needs to be confidential (such as cloud with customer names and the like) vs what might be able to be made public.
I'll see what everyone thinks is the best way to move forward there and won't unilaterally make the decision.

mikermcneil
3 minutes ago

bulk move it all and sub it under an infrastructure path in confidential to start.

👍 Make sense to me!

I'll see what everyone thinks is the best way to move forward there and won't unilaterally make the decision.

Thanks for the thoughtfulness Robert. No need.

Speed is a startup's advantage. For the sake of expediency, let's keep it simple and move everything as quickly as possible to fleetdm/confidential and archive the extraneous repo. I wrote up a few steps here to cover the steps that jumped out to me: #10330

Further declassification to make public-friendly bits public can be a future aspiration. (We weren't able to start off public by default in this case, and declassification is hard and risky. Next time, let's make it public by default.)

We might … I'll talk with everyone about getting that moved.

Moving everything to fleetdm/confidential and shutting down fleetdm/fleet-infra is the primary goal we're solving for here, since we made the decision to use as few repos as possible in 2020 at the start of the company.

To be successful long term, and especially to reach its next stage of growth against market odds, Fleet needs to be able not just to quickly make decisions, but to stick to them. Decisions can always be questioned in future iterations by discussing with the DRI.

[rfairburn]

https://github.com/fleetdm/fleet-infra/blob/master/README.md now indicates that it has been migrated to confidential.

[rfairburn]

I think everything is done here. marking as complete

[fleet-release]

Fewer repos, more secure
Clouds glowing in the air
Fleet's strength grows strong

[mikermcneil]

Nice work, thank you @rfairburn.