rusackas commented on issue #18031: URL: https://github.com/apache/superset/issues/18031#issuecomment-1017145074
> I really like this! I wonder if we should make the PMC cleanup an annually recurring task? If there's no process in place for it, I assume it will probably never happen in practice. Also, maybe members members that are flagged for removal should be notified so that they can make a case for inclusion, despite inactivity (I'm thinking parental leave or other good reason for being temporarily inactive). This spurred a lot of thinking I added two paragraphs at the end about (a) cadence, (b) process for contesting removal (c) gathering consensus if removal IS contested, (d) reinstatement opportunity, and (e) a means to keep track of the audit event/cadence. > Finally, should we also make a similar guideline for committership, with a similar cleanup process? AFAIK there are already some informal guidelines for becoming a committer, but it would be good to formalize that process to make it clear what the requirements are for those who want to step up their role in the project. Possibly, yes.... but let's see how this plays out first, and then evolve it a bit if it goes OK. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
