Feature/arch analysis

[Jacck]

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.

Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[github-actions]

A label of 'needs-attention' was automatically added to this PR in order to raise the
attention of the committers. Once this issue has been triaged, the triage label
should be removed to prevent this automation from happening again.

[mumrah]

Hello @Jacck, thanks for the patch!

Could you explain this change in a bit more detail? What exactly are these scripts doing and what is the benefit to Kafka?

[Jacck]

My intent is to analyse Kafka architecture, especially to measure coupling, after each commit

[mumrah]

Gotcha, ok. This kind of analysis is interesting, albeit a bit academic. It's doesn't exactly give us actionable information. I think the contributors are already quite aware of the class and module level coupling that exists in Kafka :)

So I'm a bit hesitant to add this to our build. I would suggest that you run this on a fork of apache/kafka or pull in the Kafka sources as a submodule on your own project. That would let us see the results and determine if it's worth including.

[github-actions]

This PR is being marked as stale since it has not had any activity in 90 days. If you
would like to keep this PR alive, please leave a comment asking for a review. If the PR has
merge conflicts, update it with the latest from the base branch.

If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact).

If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.