Approved the PR.
I see the self service portal is already mailing us about requests. I
approved one a few minutes ago.
On Mon, Mar 6, 2023 at 2:02 AM 张铎(Duo Zhang) wrote:
> https://selfserve.apache.org/jira-account.html
>
> The INFRA team has delivered a self serving tool for requesting a jira
https://selfserve.apache.org/jira-account.html
The INFRA team has delivered a self serving tool for requesting a jira
account, so contributors could request a jira account by their own.
I filed HBASE-27689 for updating the README.md to mention this change and
the PR is ready
Did other projects have the same solution for this, sync github issues to
jira issues? Github issues will be useful to get more feedback.
张铎(Duo Zhang) 于2022年12月6日周二 00:13写道：
> The PR for HBASE-27513 is available
>
> https://github.com/apache/hbase/pull/4913
>
> Let's at least tell our users to
The PR for HBASE-27513 is available
https://github.com/apache/hbase/pull/4913
Let's at least tell our users to send email to private@hbase for
acquiring a jira account.
Thanks.
张铎(Duo Zhang) 于2022年12月2日周五 12:46写道：
>
> Currently all the comment on github PR will be sent to issues@hbase,
> like
Currently all the comment on github PR will be sent to issues@hbase,
like this one
https://lists.apache.org/thread/jbfm269b4m24xl2r82l8b0t3pmqr44hr
But I think this can only be used as an archive, to make sure that all
discussions are recorded on asf infrastructure.
For github issues, I'm
Should we have them sent to private@? Just thinking in terms of reducing
spam to users who put their email and full name on a public list.
One thought I had about bug tracking is whether we could use some sort of
github -> jira sync. I've seen them used before, where it automatically
syncs issues
I've filed HBASE-27513 for changing the readme on github.
At least let's reuse the existing mailing list for acquiring jira account.
Thanks.
张铎(Duo Zhang) 于2022年11月29日周二 22:34写道：
>
> Bump and also send this to user@hbase.
>
> We need to find a way to deal with the current situation where
>
Bump and also send this to user@hbase.
We need to find a way to deal with the current situation where
contributors can not create a Jira account on their own...
At least, we need to change the readme on github page, web site and
also the ref guide to tell users how to acquire a jira account...
For me, I think most developers already have a github account, so
enabling it could help us get more feedback. For lots of younger
Chinese developers, they rarely use email in their daily life...
No doubt later we need to modify our readme on github. If we just let
users go to github issues on the
This new situation around JIRA seems very similar to the existing situation
around Slack. A new community member currently must acquire a Slack invite
somehow, usually by emailing one of the lists. Mailing lists themselves
involve a signup process, though it may be possible to email user/-zh/dev
I've forwarded an announcement email from the INFRA team recently
about disabling the public sign ups for jira.a.o because of spamming.
And now the rule is finally applied, when you open jira.a.o, you can
see there is a gray bar on the top to tell you 'Public signup for this
instance is disabled.
11 matches
Mail list logo
