You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/13 14:56:48 UTC
[GitHub] [superset] rusackas opened a new issue #18031: SIP-78: Guidelines for PMC Membership
rusackas opened a new issue #18031:
URL: https://github.com/apache/superset/issues/18031
## [SIP-78] Guidelines for PMC Membership
### Motivation
Superset wants to promote the growth and sustainability of a vibrant PMC (Project Management Committee) for the Apache Superset project. To this end, we need to create a set of standards to help act as an onramp/guideline for nominating top participants from the project's Committer roster into the PMC.
Similarly, we need to standardize how we gauge any given PMC member's absence or inactivity on the project and consider the conditions under which they may be removed from the PMC (retaining their Committer access). As per Apache guidelines, it's worth nothing that merit is for life, and while committership is essentially for life (certain restrictions may apply), PMC members should uphold reasonable expectations of ongoing involvement, and these expectations should be upheld consistently across all members.
### Proposed Change
With the passage of this SIP, these standards will be published on the Superset Wiki, and referred to as necessary. If adjustments are to be made to these in the future, they should be proposed on the dev@ list for lazy consensus before making changes on the Wiki. If lazy consensus cannot be easily reached, a subsequent SIP may be proposed/voted.
### New or Changed Public Interfaces
N/A
### New dependencies
N/A
### Migration Plan and Compatibility
Standing Committers may be audited and gauged against these standards, and new nominations may be proposed/voted on the private@ list. Existing PMC members may also be gauged according to these standards, and a VOTE may be held to remove them from the PMC.
### Rejected Alternatives
Not having published or consistent standards.
___
`Proposal:`
# Guidelines for promoting Committers to Superset PMC
1. Consistent voting on RCs for at least past 3 release lifecycles
2. Has been actively voting on SIPs or creating them and leading their implementation
3. Visibility on discussions on the dev mailing list
4. Spreading the word for “Superset” - talk on meetups/conferences/videos/blogs (Help spread the word about Superset)
5. Actively involved in Reviewing Pull Requests & merging them
6. Actively involved in filing/supporting/triaging/resolving Github Issues
7. Has been a committer for at least 3 months and has still been an active community member since becoming a committer
8. Is active in growing the community by mentoring new members
To become a PMC member the committers should meet all *general prerequisites*. Apart from that the person should demonstrate distinct *community involvement* or *code contributions*. When putting someone up for a vote, these attributes (or any special exemptions thereof) should be noted in the nomination email.
### General prerequisites:
* Has been a committer for at least 3 months
* Has remained an active community member, and has voiced or demonstrated an intent for ongoing engagement
### Community involvement:
* Visibility in discussions on the dev mailing list, Slack workspace, and/or GitHub
* Spreading the word about “Superflow” via:
* Talks at meetups, conferences, etc
* Creating content (videos, blogs etc)
* Growing the community:
* Mentors new members/contributors
* Answers users/contributors via Github issues, dev list or Slack
### Code contribution:
* Consistent voting on RCs for at least past 3 releases lifecycles
* Engagement in Superset Improvement Proposals (SIPs) by either:
* Actively voting on SIPs
* Proposing and/or leading their implementation
* Actively involved in code contributions:
* Code reviews
* Merging pull requests
* Fixing bugs and implementing improvements
# Guidelines for removing Committers from the Superset PMC
As per Apache [guidelines](https://www.apache.org/dev/pmc.html), a PMC may have a process of removing inactive members, as long as that standard is applied consistently. Using the above standards for becoming a PMC member as a baseline, the following standards and process are hereby proposed for removing inactive members from the Superset PMC.
* General requirements (at least one of the following must be met)
* Active contribution to the codebase within the last 6 months
* Active in discussions on the dev mailing list, Slack workspace, and/or GitHub
* Active in testing and voting on RCs within the past 3 release lifecycles
* Actively involved in reviewing/merging pull requests or triaging/labeling/supporting Github Issues
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] etr2460 commented on issue #18031: SIP-78: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
etr2460 commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012391011
Perhaps let's remove the numbered list now since you've categorized these guidelines into required and preferred categories below? It was a bit tricky to read as is.
Also under "Guidelines for removing Committers from the Superset PMC", perhaps we should word it as "meeting none of the below general requirements may result in removal from the Superset PMC"?
Otherwise, +1!
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] geido commented on issue #18031: SIP-78: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
geido commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012221882
Strong +1!!
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-78: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012354708
I'm adding "(required)" and ("preferred") parenthetical statements to clarify that only the General Prerequisites are what's *required*
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] eschutho commented on issue #18031: SIP-78: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
eschutho commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012348514
This is awesome! Is it going to be a prerequisite for someone to give talks and write blogs in order to be a PMC? Also one thing that I think we can add is participation in Superset meetups and one of the Operational Model teams.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] villebro commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
villebro commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012946561
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).
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.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012421614
> Perhaps let's remove the numbered list now since you've categorized these guidelines into required and preferred categories below? It was a bit tricky to read as is.
Indeed, that was largely redundant. Thanks for the fresh eyes. I've removed it, and migrated any nuance/differences into the other subdivided list.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] michael-s-molina commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
michael-s-molina commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1017586752
I really liked the idea! Big +1!
I'm wondering how some of the requirements are going to be tracked? Some are pretty straightforward like code reviews, merging PRs, etc. but how about talks at meetups, conferences, videos/blog creation? I'm just putting on the hat of the auditor right now and thinking about the auditing process.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] srinify closed issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
srinify closed issue #18031:
URL: https://github.com/apache/superset/issues/18031
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1026247823
> Do we have another set of standards in voting new contributors into a Project Committer (which gives them access to stamp and merge PR)?
Not yet, but that's certainly a worthwhile effort! I can try to put that together next unless someone else is particularly interested.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] michael-s-molina edited a comment on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
michael-s-molina edited a comment on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1017586752
I really liked the idea! Big +1!
I'm wondering how some of the requirements are going to be tracked? Some are pretty straightforward like code reviews, merging PRs, etc. but how about talks at meetups, conferences, videos/blog creation? I'm just putting on the hat of the auditor right now and thinking about the auditing process. The tracking process is also important for transparency.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] srinify commented on issue #18031: SIP-78: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
srinify commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1012256551
Love this idea, +1!
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] srinify commented on issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
srinify commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1031453785
Closing this issue, as the VOTE thread has passed!
- Results mailing list thread: https://lists.apache.org/thread/r4f0wxf5n0vwrnt5tbkrn0d3dymv8dz4
- Status updated on SIP Board as well: https://github.com/apache/superset/projects/7#card-76721105
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1040885195
Posted to wiki [here](https://github.com/apache/superset/wiki/Guidelines-for-promoting-Committers-to-Superset-PMC)
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] cgivre edited a comment on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
cgivre edited a comment on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1018059838
I hate to be the one to point this out, but as an Apache Top Level project, this proposal kind of flies in the face of the Apache Way.[1] Specifically:
> Earned Authority: all individuals are given the opportunity to participate, but their influence is based on publicly earned merit – what they contribute to the community. **Merit lies with the individual, does not expire**, is not influenced by employment status or employer, and is non-transferable (merit earned in one project cannot be applied to another).
So, while I understand the desire to keep the PMC and committer pool populated with active members, I really don't see the harm in allowing people to take a hiatus and return when they so desire. There's no limit to PMC members and as long as someone isn't detracting from the project, I really don't think this is necessary at all.
So, -1 from me. (non-binding)
[1]: https://www.apache.org/theapacheway/
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] ktmud commented on issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
ktmud commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1022497462
Do we have another set of standards in voting new contributors into a Project Committer (which gives them access to stamp and merge PR)?
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas edited a comment on issue #18031: SIP-79: Guidelines for Superset PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas edited a comment on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1018069094
> > Earned Authority: all individuals are given the opportunity to participate, but their influence is based on publicly earned merit – what they contribute to the community. **Merit lies with the individual, does not expire**, is not influenced by employment status or employer, and is non-transferable (merit earned in one project cannot be applied to another).
Per [Apache docs](https://www.apache.org/dev/pmc.html), "Projects can establish their own policy on handling inactive members, as long as they apply it consistently."
> So, while I understand the desire to keep the PMC and committer pool populated with active members, I really don't see the harm in allowing people to take a hiatus and return when they so desire. There's no limit to PMC members and as long as someone isn't detracting from the project, I really don't think this is necessary at all.
I don't think this flies in the face of the Apache Way, but rather conforms to it by attempting to establish a consistent bar.
The proposal also outlines a process in which if a member is deemed inactive, we simply reach out to them... then if they reply that they're still interested, it's assumed (via lazy consensus) that they'll retain their membership. Basically, they just have to respond "yes" to that email and it's over.
> So, -1 from me. (non-binding)
It's still in the discussion phase, but we'll be opening a vote soon on the dev@ list.
In the meantime, I'm curious if there are any changes that would mitigate your concern... perhaps:
* Changing the maximum cadence of the audit to be annual? Then people only have to reply to the email defending their status once a year.
* Adding an email template or other further elaboration on the removal?
* Creating an easier process for prior members to re-enter the PMC in the event of a lapse, since indeed, merit never expires?
Also, I think the idea of using this to onramp PMC members is perhaps more important than the (albeit more controversial/complex) inactivity auditing process.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] cgivre commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
cgivre commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1018059838
I hate to be the one to point this out, but as an Apache Top Level project, this proposal kind of flys in the face of the Apache Way.[1] Specifically:
> Earned Authority: all individuals are given the opportunity to participate, but their influence is based on publicly earned merit – what they contribute to the community. **Merit lies with the individual, does not expire**, is not influenced by employment status or employer, and is non-transferable (merit earned in one project cannot be applied to another).
So, while I understand the desire to keep the PMC and committer pool populated with active members, I really don't see the harm in allowing people to take a hiatus and return when they so desire. There's no limit to PMC members and as long as someone isn't detracting from the project, I really don't think this is necessary at all.
So, -1 from me. (non-binding)
[1]: https://www.apache.org/theapacheway/
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] rusackas commented on issue #18031: SIP-79: Guidelines for PMC Membership
Posted by GitBox <gi...@apache.org>.
rusackas commented on issue #18031:
URL: https://github.com/apache/superset/issues/18031#issuecomment-1018069094
> > Earned Authority: all individuals are given the opportunity to participate, but their influence is based on publicly earned merit – what they contribute to the community. **Merit lies with the individual, does not expire**, is not influenced by employment status or employer, and is non-transferable (merit earned in one project cannot be applied to another).
Per [Apache docs](https://www.apache.org/dev/pmc.html), "Projects can establish their own policy on handling inactive members, as long as they apply it consistently."
> So, while I understand the desire to keep the PMC and committer pool populated with active members, I really don't see the harm in allowing people to take a hiatus and return when they so desire. There's no limit to PMC members and as long as someone isn't detracting from the project, I really don't think this is necessary at all.
I don't think this flies in the face of the Apache Way, but rather conforms to it by attempting to establish a consistent bar.
The proposal also outlines a process in which if a member is deemed inactive, we simply reach out to them... then if they reply that they're still interested, it's assumed (via lazy consensus) that they'll retain their membership. Basically, they just have to respond "yes" to that email and it's over.
> So, -1 from me. (non-binding)
It's still in the discussion phase, but we'll be opening a vote soon on the dev@ list.
In the meantime, I'm curious if there are any changes that would mitigate your concern... perhaps:
* Changing the maximum cadence of the audit to be annual? Then people only have to
* Adding an email template or other further elaboration on the removal?
* Creating an easier process for prior members to re-enter the PMC in the event of a lapse, since indeed, merit never expires?
Also, I think the idea of using this to onramp PMC members is perhaps more important than the (albeit more controversial/complex) inactivity auditing process.
--
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-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org