I created an umbrella issue to track this and other decisions and tasks we
have to make this switch happen:
https://github.com/apache/arrow/issues/14542
Please comment (or edit if you can) freely.
Neal
On Wed, Oct 26, 2022 at 3:39 PM Ian Cook wrote:
> I updated this user mapping list to
I updated this user mapping list to include both the "key" and "name"
fields for each Jira account. These fields sometimes do not match, and
the "key" field sometimes contains unfriendly values like
JIRAUSER123456. To follow further discussion about this, please see
Todd said:
>User identifiers differ between systems...
To help with this, I created a couple of small scripts [1] that
extract details from resolved Arrow Jira issues and the associated
merged GitHub PRs, then perform some cleaning, to generate a list [2]
of matching Jira user identifiers and
Thanks Todd! That's really helpful.
Neal
On Tue, Oct 25, 2022 at 7:47 PM Todd Farmer
wrote:
> I'm beginning to track decisions needing to be made and problems needing to
> be solved in the Arrow project GitHub issues, prefixing all such issues
> with "MIGRATION: ..". They can be found here:
>
I'm beginning to track decisions needing to be made and problems needing to
be solved in the Arrow project GitHub issues, prefixing all such issues
with "MIGRATION: ..". They can be found here:
https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+MIGRATION
I feel this will be a better
I'll start a vote on this in the next day or so since it seems like we have
consensus on the main issue (moving from Jira to GitHub Issues) and are
working out the finer points on how we'll migrate and how we'll map Jira
concepts to Issues.
Speaking of the migration: now would be an *excellent*
On Tue, Oct 25, 2022 at 1:55 AM Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:
>
> I think the main thing we will miss are the Links (relation between
> issues), but we can try to promote some consistent usage of adding
> "Duplicate of #...", "Related to #..." in top post of an
w/pulls?q=is%3Apr+is%3Aopen+label%3Alang-c%2B%2B
> > > > > * Affects version: Create new labels such as "affect-10.0.0"?
> > > > > * Fix version: We can use GitHub's milestone feature
> > > > > * I tried creating the "11.0.0" milestone:
gt; * Fix version: We can use GitHub's milestone feature
> > > > * I tried creating the "11.0.0" milestone:
> > > > https://github.com/apache/arrow/milestone/1
> > > > * Type: GitHub's label feature or custom field in GitHub's
> > > > project feature?
> &g
> https://github.com/apache/arrow/milestone/1
> > > * Type: GitHub's label feature or custom field in GitHub's
> > > project feature?
> > > * I tried creating a GitHub project for Apache Arrow:
> > > https://github.com/orgs/apache/projects/148
> &g
ect for Apache Arrow:
> > > https://github.com/orgs/apache/projects/148
> > > * All Apache Arrow committers have Admin role. You can
> > > change anything to learn GitHub's project feature.
> > > * Issue links: It seems that we can't do this.
>
in GitHub's
> > project feature?
> > * I tried creating a GitHub project for Apache Arrow:
> > https://github.com/orgs/apache/projects/148
> > * All Apache Arrow committers have Admin role. You can
> > change anything to learn GitHub's project feature.
&g
b's project feature.
> * Issue links: It seems that we can't do this.
> * Priority: GitHub's label feature or custom field in GitHub's
> project feature?
>
>
> Thanks,
> --
> kou
>
> In <82d49482-706d-081b-32e7-f692bc282...@python.org>
> "Re: [DISC
-
kou
In <82d49482-706d-081b-32e7-f692bc282...@python.org>
"Re: [DISCUSS] Move issue tracking to " on Sat, 22 Oct 2022
16:19:14 +0200,
Antoine Pitrou wrote:
>
> Hi Neal,
>
> Le 22/10/2022 à 15:35, Neal Richardson a écrit :
>> Their email says:
>&
It is unclear why the infrastructure team cannot allow a variety of
authentication mechanisms - Gitee for example enables SMS authentication
and validation by any validated Gitee user to obtain basic
functionality. My expectation is that any committer or validated
contributor (not just PMC)
It is my opinion that github issues have served us very well in the Arrow
Rust implementation. I haven't heard anyone complain about github or
suggest we should look for alternatives.
One of the major benefits is that everyone who contributes to the project
already has to have a github account,
I can't claim experience migrating to GitHub issues, but I've done some
work with Jira APIs and import/export tools. I'm happy to help draft a
proposal or proof-of-concept to validate if nobody else expresses interest,
or to assist anybody who does.
Todd
On Sat, Oct 22, 2022 at 12:08 PM Neal
I would guess that mostly could be handled with labels, though that does
turn into lots of labels. GitHub also seems to have grown some useful
features for this, like Projects [1] and Milestones, and we should look
into how to make them work for us.
While I agree that those features in the
We enabled discussions a while back, and it has been ineffective so far. We
have only had a few discussions created and we are slow to respond to them,
which I think is due to lack of notifications but I could be wrong.
On Sat, Oct 22, 2022 at 8:00 AM Ivan Ogasawara
wrote:
> IMHO I think that
Hi Neal,
Le 22/10/2022 à 15:35, Neal Richardson a écrit :
Their email says:
Infra knows this process change places an increasing burden on PMC members
for managing contributors, and makes it harder for people to contribute
bug reports.
We suggest projects consider using GitHub Issues for
IMHO I think that it makes total sense to have all in the same platform,
for the reasons already mentioned.
Question: does it make sense to enable github discussions for questions?
On Sat, Oct 22, 2022, 09:55 Andy Grove wrote:
> I believe that using GitHub issues has reduced overhead for us in
I believe that using GitHub issues has reduced overhead for us in the Rust
projects and lowered the barrier for new contributors. As shown in the blog
post for the latest DataFusion release alone [1], there were 62
contributors and 31 of them contributed a single PR, so I think that
demonstrates
Hi all,
ASF Infra has announced [1] that, due to spam account creation, it will no
longer be possible for people to sign themselves up for a Jira account to
report issues as of November 6. Instead, the PMC will have to request the
creation of Jira accounts.
Their email says:
> Infra knows this
23 matches
Mail list logo
