add MAINTAINERS.md file to each repository in Spin project

[michelleN]

The governance document was just merged and requires a MAINTAINERS.md file in each repo:

New maintainers MUST be nominated by existing maintainers. Maintainers are to discuss and agree in a private setting adding a new maintainer. Once a descision has been made, a maintainer may be added to the project via a pull request to the relevant MAINTAINERS.md file.

This issue tracks the work to make that change.

[michelleN]

Core Spin:

• Spin: add MAINTAINERS.md #2683

SDKs:

• Spin Python SDK:add maintainers file spin-python-sdk#112
• Spin JavaScript SDK: add MAINTAINERS.md file spin-js-sdk#256
• Spin Rust SDK: add MAINTAINERs.md file spin-rust-sdk#32
• Spin .NET SDK: add MAINTAINERS.md spin-dotnet-sdk#59
• Spin Nim SDK: add MAINTAINERS.md spin-nim-sdk#4

Plugins:

• Spin Plugins Index Repository: add MAINTAINERS.md spin-plugins#64
• Spin Test Plugin: add MAINTAINERS.md spin-test#112
• Spin Cloud GPU Plugin: add maintainers file spin-cloud-gpu#22

Triggers:

• Spin Command Trigger: add maintainers file spin-trigger-command#40
• Spin SQS Trigger: add maintainers file spin-trigger-sqs#42
• Spin Cron Trigger: add maintainers file spin-trigger-cron#20

[itowlson]

@michelleN If all the repos are now done except for the Nim SDK, might it be good to close this issue and open one specifically in the Nim SDK? Or do you want to keep this open here for higher visibility?

[radu-matei]

+1 to @itowlson's suggestion to move this to the project as an issue.

From the governance document:

Project maintainers MUST remain active on the project. If they are unresponsive for > 3 months, they will lose project maintainer-ship, unless the remaining project maintainers of the given project and the Spin Governance Committee agree to extend the period to be greater than 3 months.

Given the inactivity in the repository, my suggestion (as the only other contributor to that repo) would be to propose we archive the project unless we find contributors interested in the Nim SDK.

Thoughts?

[michelleN]

+1 to closing this and opening an issue in the nim sdk project.

+1 to archiving the project. We don't have process around that just yet. I propose we open a PR removing it from the projects list in the governance doc and discuss there. As a separate task, we should also add some text (probably in the governance document) around what it means to archive a project and how to do it.

[michelleN]

archive proposal: #2849
governance task: #2850