search

dotnet / arcade

Tools that provide common build infrastructure for multiple .NET Foundation projects.
MIT License
673 stars 347 forks source link

What does it mean to open source the engineering system? #8810

Closed dotnet-bot closed 2 years ago

dotnet-bot commented 2 years ago

Migrated from https://github.com/dotnet/core-eng/issues/14795

@ChadNedzlek wrote:

Why?

Given the recent public sentiment about the .NET Foundation, a gesture of goodwill is in order, I think. Exposing just how much work goes on in the background to keep everything running, and showing why it's not as easy as just "fork the repo and ship my own .NET" seems like a good idea.

Which repos?

What is there to do?

  1. Ensure that we have repo licenses
  2. Ensure we have license headers in files
  3. Ensure we have good readme and contribution instructions (though I don't actually expect any contributions).
  4. Examine PR build flows to make sure they are safe to execute in the public, and, if not, modify them
  5. Ensure there are no secrets in code (we've been really good on this for years, but one last check is warranted)
  6. Ensure git history is safe to post, if not, we'll just seed with current state
  7. Clean up any dangerous references in docs/wiki
  8. Work with PM around public messaging

Recently Triaged Issues

All issues in this section should be triaged by the v-team into one of their business objectives or features.

mmitche commented 2 years ago

Closing for now. Will reopen if we have good motivation to open source the Helix service infrastructure.