You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2026/03/30 18:27:17 UTC
[DISCUSS] Use of CommunityInviter for Slack invite
Hi folks,
To avoid spam/flood, the Slack invite link we create is only valid for 30
days (that's a "protection" from Slack).
It means that we should update the website every month to update the invite.
Some Apache projects (like Apache Pinot) are using Community Inviter:
https://communityinviter.com/
Here's the example for Apache Pinot:
https://communityinviter.com/apps/apache-pinot/apache-pinot
The principal is that we register an "admin" email address (basically the
PMC/private mailing list).
People can ask for the invite on communityinviter and then the PMC
approve/decline the request.
No need to update the Slack invite directly on the website anymore, the
communityinviter link is always valid (and moderated).
Thoughts ?
PS: for the Iceberg community member, Iceberg Slack has exactly the same
"issue". I would be happy to propose the same approach to the Iceberg
community.
Regards
JB
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Russ
In the Slack documentation, I see:
"Each invite link is active for 30 days, and can be used by up to 400
people. If your invite link expires, find an owner or admin who can
manage invite links in Slack. Keep in mind, anyone who clicks the link
will be able to join your workspace."
However, on Polaris Slack workspace I just changed the link to never
expires (it was set to 30 days, the default).
For the record, here's what I did:
- on the Polaris workspace menu, click on "Invite people to Apache-Polaris"
- Click on "Invite link", then "Edit link settings" appear
- Set to "Never expires" for "Link set to expire after ..."
The invite link is:
https://join.slack.com/t/apache-polaris/shared_invite/zt-3txht5g9x-9NYK98fK6hk40bOaWGW83Q
I guess we have to update the website as the link changed.
It should be good enough.
Let's see if it's sufficient.
Thanks
Regards
JB
On Mon, Mar 30, 2026 at 10:03 PM Russell Spitzer
<ru...@gmail.com> wrote:
>
> You should be able to make non-expiring links, they do have a 400 joiners
> per link limit though. Still an issue but not really that bad imho. Would be
> nice to have something automatedly check if the link is expired (which
> anyone with admin credentials can do) and raise a new pr for a new one if is
> out of invites.
>
> On Mon, Mar 30, 2026 at 1:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi folks,
> >
> > To avoid spam/flood, the Slack invite link we create is only valid for 30
> > days (that's a "protection" from Slack).
> >
> > It means that we should update the website every month to update the
> > invite.
> >
> > Some Apache projects (like Apache Pinot) are using Community Inviter:
> >
> > https://communityinviter.com/
> >
> > Here's the example for Apache Pinot:
> > https://communityinviter.com/apps/apache-pinot/apache-pinot
> >
> > The principal is that we register an "admin" email address (basically the
> > PMC/private mailing list).
> > People can ask for the invite on communityinviter and then the PMC
> > approve/decline the request.
> >
> > No need to update the Slack invite directly on the website anymore, the
> > communityinviter link is always valid (and moderated).
> >
> > Thoughts ?
> >
> > PS: for the Iceberg community member, Iceberg Slack has exactly the same
> > "issue". I would be happy to propose the same approach to the Iceberg
> > community.
> >
> > Regards
> > JB
> >
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Yufei Gu <fl...@gmail.com>.
> The principal is that we register an "admin" email address (basically the
PMC/private mailing list). People can ask for the invite on
communityinviter and then the PMC approve/decline the request.
Would this process be more labour-intensive since PMC must approve every
request?
Yufei
On Mon, Mar 30, 2026 at 2:02 PM Dmitri Bourlatchkov <di...@apache.org>
wrote:
> Hi Russell,
>
> I like the idea of a non-expiring link with a limit on the number of joins.
> I think it's less labour-intensive on the PMC.
>
> However, the image did not pass through the ML system (attachment lost).
>
> Cheers,
> Dmitri.
>
> On Mon, Mar 30, 2026 at 4:07 PM Russell Spitzer <russell.spitzer@gmail.com
> >
> wrote:
>
> > Should look like
> > [image: image.png]
> >
> >
> > On Mon, Mar 30, 2026 at 3:02 PM Russell Spitzer <
> russell.spitzer@gmail.com>
> > wrote:
> >
> >> You should be able to make non-expiring links, they do have a 400
> joiners
> >> per link limit though. Still an issue but not really that bad imho.
> Would be
> >> nice to have something automatedly check if the link is expired (which
> >> anyone with admin credentials can do) and raise a new pr for a new one
> if is
> >> out of invites.
> >>
> >> On Mon, Mar 30, 2026 at 1:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >>
> >>> Hi folks,
> >>>
> >>> To avoid spam/flood, the Slack invite link we create is only valid for
> 30
> >>> days (that's a "protection" from Slack).
> >>>
> >>> It means that we should update the website every month to update the
> >>> invite.
> >>>
> >>> Some Apache projects (like Apache Pinot) are using Community Inviter:
> >>>
> >>> https://communityinviter.com/
> >>>
> >>> Here's the example for Apache Pinot:
> >>> https://communityinviter.com/apps/apache-pinot/apache-pinot
> >>>
> >>> The principal is that we register an "admin" email address (basically
> the
> >>> PMC/private mailing list).
> >>> People can ask for the invite on communityinviter and then the PMC
> >>> approve/decline the request.
> >>>
> >>> No need to update the Slack invite directly on the website anymore, the
> >>> communityinviter link is always valid (and moderated).
> >>>
> >>> Thoughts ?
> >>>
> >>> PS: for the Iceberg community member, Iceberg Slack has exactly the
> same
> >>> "issue". I would be happy to propose the same approach to the Iceberg
> >>> community.
> >>>
> >>> Regards
> >>> JB
> >>>
> >>
>
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Dmitri Bourlatchkov <di...@apache.org>.
Hi Russell,
I like the idea of a non-expiring link with a limit on the number of joins.
I think it's less labour-intensive on the PMC.
However, the image did not pass through the ML system (attachment lost).
Cheers,
Dmitri.
On Mon, Mar 30, 2026 at 4:07 PM Russell Spitzer <ru...@gmail.com>
wrote:
> Should look like
> [image: image.png]
>
>
> On Mon, Mar 30, 2026 at 3:02 PM Russell Spitzer <ru...@gmail.com>
> wrote:
>
>> You should be able to make non-expiring links, they do have a 400 joiners
>> per link limit though. Still an issue but not really that bad imho. Would be
>> nice to have something automatedly check if the link is expired (which
>> anyone with admin credentials can do) and raise a new pr for a new one if is
>> out of invites.
>>
>> On Mon, Mar 30, 2026 at 1:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> Hi folks,
>>>
>>> To avoid spam/flood, the Slack invite link we create is only valid for 30
>>> days (that's a "protection" from Slack).
>>>
>>> It means that we should update the website every month to update the
>>> invite.
>>>
>>> Some Apache projects (like Apache Pinot) are using Community Inviter:
>>>
>>> https://communityinviter.com/
>>>
>>> Here's the example for Apache Pinot:
>>> https://communityinviter.com/apps/apache-pinot/apache-pinot
>>>
>>> The principal is that we register an "admin" email address (basically the
>>> PMC/private mailing list).
>>> People can ask for the invite on communityinviter and then the PMC
>>> approve/decline the request.
>>>
>>> No need to update the Slack invite directly on the website anymore, the
>>> communityinviter link is always valid (and moderated).
>>>
>>> Thoughts ?
>>>
>>> PS: for the Iceberg community member, Iceberg Slack has exactly the same
>>> "issue". I would be happy to propose the same approach to the Iceberg
>>> community.
>>>
>>> Regards
>>> JB
>>>
>>
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Russell Spitzer <ru...@gmail.com>.
Should look like
[image: image.png]
On Mon, Mar 30, 2026 at 3:02 PM Russell Spitzer <ru...@gmail.com>
wrote:
> You should be able to make non-expiring links, they do have a 400 joiners
> per link limit though. Still an issue but not really that bad imho. Would be
> nice to have something automatedly check if the link is expired (which
> anyone with admin credentials can do) and raise a new pr for a new one if is
> out of invites.
>
> On Mon, Mar 30, 2026 at 1:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi folks,
>>
>> To avoid spam/flood, the Slack invite link we create is only valid for 30
>> days (that's a "protection" from Slack).
>>
>> It means that we should update the website every month to update the
>> invite.
>>
>> Some Apache projects (like Apache Pinot) are using Community Inviter:
>>
>> https://communityinviter.com/
>>
>> Here's the example for Apache Pinot:
>> https://communityinviter.com/apps/apache-pinot/apache-pinot
>>
>> The principal is that we register an "admin" email address (basically the
>> PMC/private mailing list).
>> People can ask for the invite on communityinviter and then the PMC
>> approve/decline the request.
>>
>> No need to update the Slack invite directly on the website anymore, the
>> communityinviter link is always valid (and moderated).
>>
>> Thoughts ?
>>
>> PS: for the Iceberg community member, Iceberg Slack has exactly the same
>> "issue". I would be happy to propose the same approach to the Iceberg
>> community.
>>
>> Regards
>> JB
>>
>
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Russell Spitzer <ru...@gmail.com>.
You should be able to make non-expiring links, they do have a 400 joiners
per link limit though. Still an issue but not really that bad imho. Would be
nice to have something automatedly check if the link is expired (which
anyone with admin credentials can do) and raise a new pr for a new one if is
out of invites.
On Mon, Mar 30, 2026 at 1:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi folks,
>
> To avoid spam/flood, the Slack invite link we create is only valid for 30
> days (that's a "protection" from Slack).
>
> It means that we should update the website every month to update the
> invite.
>
> Some Apache projects (like Apache Pinot) are using Community Inviter:
>
> https://communityinviter.com/
>
> Here's the example for Apache Pinot:
> https://communityinviter.com/apps/apache-pinot/apache-pinot
>
> The principal is that we register an "admin" email address (basically the
> PMC/private mailing list).
> People can ask for the invite on communityinviter and then the PMC
> approve/decline the request.
>
> No need to update the Slack invite directly on the website anymore, the
> communityinviter link is always valid (and moderated).
>
> Thoughts ?
>
> PS: for the Iceberg community member, Iceberg Slack has exactly the same
> "issue". I would be happy to propose the same approach to the Iceberg
> community.
>
> Regards
> JB
>
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Yufei Gu <fl...@gmail.com>.
Awesome! Approved. Thanks JB!
Yufei
On Mon, Mar 30, 2026 at 8:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Here's the PR to update the website:
>
> https://github.com/apache/polaris/pull/4088
>
> Regards
> JB
>
> On Mon, Mar 30, 2026 at 8:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >
> > Hi folks,
> >
> > To avoid spam/flood, the Slack invite link we create is only valid for
> 30 days (that's a "protection" from Slack).
> >
> > It means that we should update the website every month to update the
> invite.
> >
> > Some Apache projects (like Apache Pinot) are using Community Inviter:
> >
> > https://communityinviter.com/
> >
> > Here's the example for Apache Pinot:
> https://communityinviter.com/apps/apache-pinot/apache-pinot
> >
> > The principal is that we register an "admin" email address (basically
> the PMC/private mailing list).
> > People can ask for the invite on communityinviter and then the PMC
> approve/decline the request.
> >
> > No need to update the Slack invite directly on the website anymore, the
> communityinviter link is always valid (and moderated).
> >
> > Thoughts ?
> >
> > PS: for the Iceberg community member, Iceberg Slack has exactly the same
> "issue". I would be happy to propose the same approach to the Iceberg
> community.
> >
> > Regards
> > JB
>
Re: [DISCUSS] Use of CommunityInviter for Slack invite
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Here's the PR to update the website:
https://github.com/apache/polaris/pull/4088
Regards
JB
On Mon, Mar 30, 2026 at 8:27 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi folks,
>
> To avoid spam/flood, the Slack invite link we create is only valid for 30 days (that's a "protection" from Slack).
>
> It means that we should update the website every month to update the invite.
>
> Some Apache projects (like Apache Pinot) are using Community Inviter:
>
> https://communityinviter.com/
>
> Here's the example for Apache Pinot: https://communityinviter.com/apps/apache-pinot/apache-pinot
>
> The principal is that we register an "admin" email address (basically the PMC/private mailing list).
> People can ask for the invite on communityinviter and then the PMC approve/decline the request.
>
> No need to update the Slack invite directly on the website anymore, the communityinviter link is always valid (and moderated).
>
> Thoughts ?
>
> PS: for the Iceberg community member, Iceberg Slack has exactly the same "issue". I would be happy to propose the same approach to the Iceberg community.
>
> Regards
> JB