-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Add field "staff_maintained" #36
Comments
(i assume mentioned should be maintained?) I think it can be automated, just by using the maintainer of each pkg against an array of staff names. I think any you maintain @maelle should be included |
thanks. I think this should happen at registry creation to allow us to add any exception if needed, and also because we might need the info in other places. |
sckott
added a commit
that referenced
this issue
Aug 26, 2020
sckott
added a commit
that referenced
this issue
Aug 26, 2020
thank you 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@sckott according to the curation policy packages mentioned by staff should be marked as such, and there is now a badge for that in the new website design. I think this means packages by you and @jeroen (not sure I can vouch for my packages as staff because of the definition of my tasks 🤔 ).
Cc @noamross
The text was updated successfully, but these errors were encountered: