Teams: Rephrase task on helping with specific MDAKits #430
Conversation
From team reviews: “Manage helping with MDAKits who need assistance” is an unclear goal, and possibly an unrealistic one as the registry grows. We suggest rephrasing the responsibility to “offer input on MDAKit issues where possible” as a more realistic responsibility.
| @@ -3,7 +3,7 @@ tasks: | |||
| - Managing submissions to MDAKits registry | |||
| - Managing manual review process of new MDAKits | |||
| - Managing automated test and badge infrastructure of all MDAKits | |||
| - Manage helping with MDAKits who need assistance | |||
| - Offer input on MDAKit issues where possible | |||
There was a problem hiding this comment.
I'm starting to think this shouldn't be the team's responsibility at all. We can help folks during the review process and if they fail in a way that is picked up with the registry, but we shouldn't be stewards of MDAKits outside the registry.
There was a problem hiding this comment.
I think we need to be open to helping with any issues that are related to the registry and that impact MDAKits, e.g., if we're changing the metadata format in some way or if the way we are running tests changes fundamentally and now MDAKit tests break that worked before. To some degree we should also listen if some of the tooling breaks that we shipped with the cookiecutter.
We can't really support "how do I write more tests" or debug incompatibilities with latest MDA releases.
Perhaps
| - Offer input on MDAKit issues where possible | |
| - Offer input on failures due to the MDAKit registry |
|
Adding listed team members as reviewers. Thanks, @IAlibay, for already chiming in! |
There was a problem hiding this comment.
With no funding for MDAKits at the moment, we have to cut back and I agree with @IAlibay that we should limit the amount of support we're committing to. However, I feel that removing any kind of support seems quite harsh so we should discuss here.
From team reviews: “Manage helping with MDAKits who need assistance” is an unclear goal, and possibly an unrealistic one as the registry grows. We suggest rephrasing the responsibility to “offer input on MDAKit issues where possible” as a more realistic responsibility.
Relatedly, we will need to develop a post-EOSS4 plan to ensure the registry is maintained.