Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teams: Rephrase task on helping with specific MDAKits #430

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Teams: Rephrase task on helping with specific MDAKits #430

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _data/team/roles/mdakit_registry.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Suggested change
- Offer input on MDAKit issues where possible
- Offer input on failures due to the MDAKit registry

current_members:
- "[Irfan Alibay](https://github.com/IAlibay)"
- "[Fiona Naughton](https://github.com/fiona-naughton)"
Expand Down
Loading