[NFC] github: Add code owners for some components

[AnthonyLatsis]

I’m an external contributor, so this is highly subjective and unrefined. Please share your thoughts and let me know if you want to be included or excluded from anywhere, or if I’ve missed something! Especially you, Suyash, since I haven’t included you anywhere yet.

[xedin]

Looks like a reasonable start!

[ktoso]

If we'd be able to I'd love to utilize this to be notified about all Distributed changes, though as they're pretty spread out, it'd have to cover all these:

./include/swift/AST/DistributedDecl.h
./include/swift/SILOptimizer/Utils/DistributedActor.h
./lib/AST/DistributedDecl.cpp
./lib/IRGen/GenDistributed.cpp
./lib/IRGen/GenDistributed.h
./lib/SILGen/SILGenDistributed.cpp
./lib/SILOptimizer/Utils/DistributedActor.cpp
./lib/Sema/CodeSynthesisDistributedActor.cpp
./lib/Sema/DerivedConformanceDistributedActor.cpp
./lib/Sema/TypeCheckDistributed.cpp
./lib/Sema/TypeCheckDistributed.h

can we glob this like lib/Sema/.*Distributed.*, lib/IRGen/.*Distributed.* etc... And the simple ones like stdlib/public/Distributed/ test/Distributed.

Though this can be done later, just asking if such globbing would work or not?

[AnthonyLatsis]

@ktoso No worries, I’ll see to it. Thanks for reacting!

[AnthonyLatsis]

just asking if such globbing would work or not

Sorry, missed this part. Yes, that will work, except in a slightly different format, like a .gitignore.

[theblixguy]

Especially you, Suyash, since I haven’t included you anywhere yet.

For now I don't want to be mentioned anywhere, but perhaps in the near future I will request to be added to some files 😄

[AnthonyLatsis]

@ktoso Have I missed anything (see the last commit)?

@xedin Could you have another look at this? I have tuned ownership in some areas and added quite a bit to address feedback.

---

Note that I am deliberately adding sections per component or directory rather than per feature, e.g. I did not add a "Distributed owners" section. There are several reasons:

• If we keep adding code owners per feature, it will become a lot harder to
  • track what has and has not been covered
  • spot ownership-breaking additions due to the "last matching pattern" rule.
• The way I imagine this to work is that we add default code owners for everything inside a directory and tune ownership with respect to the current file hierarchy under those directories.

[ktoso]

Thank you, this looks very good :) The rationale on how we add those also makes sense, thanks!

[xedin]

Makes sense to me, thank you!

[xedin]

@CodaFi Do you want to be mentioned to any of these?

[CodaFi]

Works for me

[AnthonyLatsis]

@slavapestov Do you have any objections concerning the areas I have assigned you to?

[AnthonyLatsis]

@hborla ping

[AnthonyLatsis]

@swift-ci please smoke test