I think there are a lot of good thoughts/pain points shared on this
thread. I would like to see if we can maybe spin off some of them onto
different threads and focus on the implications of Andrew's PR.
I think two points have been raised or implied that are worth discussing:
1. What are the gui
Hi all,
Reminder that our biweekly call is coming up at
https://meet.google.com/vtm-teks-phx. All are welcome to join. Notes will
be shared with the mailing list afterward.
Neal
Thanks!
On Tue, Mar 2, 2021 at 5:02 PM Andrew Lamb wrote:
> You need to be added to a separate list -- I will take care of it. Thank
> you!
>
> On Tue, Mar 2, 2021 at 5:18 PM Eric Burden
> wrote:
>
> > I've created the JIRA issue, how do I assign it to myself?
> >
> > On Tue, Mar 2, 2021 at 3:5
Hi Andrew,
Sorry for increasing scope of this topic.
As a reviewer of your PR
https://github.com/apache/arrow/pull/9598, I was not sure we
can really keep following "The Apache Way" with the PR's
approach. The workflow proposed by the PR creates an
associated JIRA issue for a PR when the PR is me
You need to be added to a separate list -- I will take care of it. Thank
you!
On Tue, Mar 2, 2021 at 5:18 PM Eric Burden wrote:
> I've created the JIRA issue, how do I assign it to myself?
>
> On Tue, Mar 2, 2021 at 3:59 PM Andrew Lamb wrote:
>
> > Thanks Eric! A JIRA issue and PR would be most
I've created the JIRA issue, how do I assign it to myself?
On Tue, Mar 2, 2021 at 3:59 PM Andrew Lamb wrote:
> Thanks Eric! A JIRA issue and PR would be most appreciated ! If you need
> help, just let us know
>
> Andrew
>
> On Tue, Mar 2, 2021 at 4:24 PM Eric Burden
> wrote:
>
> > Having dug in
Thanks Eric! A JIRA issue and PR would be most appreciated ! If you need
help, just let us know
Andrew
On Tue, Mar 2, 2021 at 4:24 PM Eric Burden wrote:
> Having dug into it a bit, I think I've identified the issue here[1]. This
> would be my first time contributing to Arrow, should I create an
To be clear, I have no objection to JIRA and I like the point that a little
friction on contribution may encourage more structured contribution and
planning.
As Neil mentioned, my original goal with this thread was to understand any
non-technical reason that prevented automating the creation of JI
Having dug into it a bit, I think I've identified the issue here[1]. This
would be my first time contributing to Arrow, should I create an issue on
JIRA first before starting in on it?
[1]
https://docs.rs/arrow/3.0.0/src/arrow/array/array_primitive.rs.html#242-271
On Tue, Mar 2, 2021 at 1:03 PM
The vote carries with 6 +1 votes from the PMC, no -1 votes, and 4
additional +1 votes from the community. Thanks everyone!
Neal
On Sun, Feb 28, 2021 at 8:38 PM Fan Liya wrote:
> +1
>
> On Sun, Feb 28, 2021 at 12:17 PM Ying Zhou wrote:
>
> > +1 (non-binding)
> >
> > > On Feb 27, 2021, at 11:19
With regards to the actual work of merging patches. I have merged
3,234 patches in this project [1], so I think this qualifies me to
have an opinion about this. I don't think that the merge tool is
problematic -- I use a little bash helper function [2] which cuts down
my work merging a patch down t
A few thoughts:
* Given the cost of switching issue trackers (even if we were to identify
one we thought was better), I think it's extremely unlikely that we would
abandon JIRA. So rather than dumping on JIRA (an easy target, of course),
we should focus on how we can make the workflows we have smo
It also seems like we're describing two different issues. The first,
a barrier to entry for new development. The second, overhead imposed
on an active developer. I'm personally not so worried about the
overhead imposed, perhaps because I can't write code that fast
anyways, so I'll stay out of th
Hi Antoine,
Can you expand a bit on this? In particular, which aspects of using
> JIRA feel bureaucratic? Is it the requirement to create a new issue
> for each PR? Or is it other concerns (such as the UI for entering or
> searching issues)?
>
First of all, thank you for taking my concerns and
It seems to me the panic on printing out the array is a bug.
I think the code should have either errored out in the builder
(date_32_builder.append_value()) or passed successfully.
It wasn't immediately clear to me from the arrow format definition[1]
envisions signed integers, but the rust code u
Hi,
I'd just like to mention that we already have a fair amount of tooling
around jira,
so switching to another issue tracker would require some additional
development effort:
- automatized pull-request issue linkage
- merge script
- various release scripts
- cherry-pick tooling for patch releases
> FWIW, the amount of bureaucracy that goes into JIRA is a major contributing
> factor for the reduction of my time commitment to this project by 80%+.
This seems a bit overly dramatic to me =) Let's dig more into what are
the actual problems. I admit that adding people to the Contributor
role in
As it says on the subject line. I encountered this issue attempting to
store dates prior to the epoch (1970-01-01). I checked for an issue in JIRA
and GitHub, but I didn't see anything related and wanted to raise it as a
discussion before I filed an issue.
MRE:
fn test_date32_builder() {
let
Made https://issues.apache.org/jira/browse/ARROW-11838 to track. If someone
adds me as a Contributor (Joris Peeters / jmgpeeters) I'm happy to assign
it to myself.
-J
On Tue, Mar 2, 2021 at 9:34 AM Antoine Pitrou wrote:
>
> Hi Joris,
>
> On Mon, 1 Mar 2021 19:04:08 +
> Joris Peeters wrote:
Have we ever considered GitHub issues to Jira sync?
This way users could choose to use GitHub but Jira would still be the
single source of truth.
Rok
On Tue, Mar 2, 2021 at 1:15 PM Adam Lippai wrote:
> Antoine,
>
> you are right I'm directly challenging the statement that any issue
> tracker, f
Arrow Build Report for Job nightly-2021-03-02-0
All tasks:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-02-0
Failed Tasks:
- test-build-vcpkg-win:
URL:
https://github.com/ursacomputing/crossbow/branches/all?query=nightly-2021-03-02-0-github-test-build-vcpkg-w
Antoine,
you are right I'm directly challenging the statement that any issue
tracker, forum or chat is as good as GitHub.
I'm not speaking about tools and efficiency. In those terms you are
absolutely right and most of the solutions are clearly superior to GitHub.
I was talking about reach, commu
On Tue, 2 Mar 2021 11:10:23 +0100
Adam Lippai wrote:
>
> All the (multiple) mailing lists, stack overflow and JIRA are definitely
> barriers for new contributors.
I'm not sure what Stack Overflow has to do with this? Interaction with
Stack Overflow isn't required to contribute to Arrow.
(also,
Hi Fernando,
On Tue, 2 Mar 2021 10:10:45 +
Fernando Herrera wrote:
>
> Adding my two cents to this thread. I would suggest that the Jira format
> imposes a high wall for newcomers. Since I have been trying to help with
> the project, I have to get familiar with Jira to be able to help with
Hi,
Adding my two cents to this thread. I would suggest that the Jira format
imposes a high wall for newcomers. Since I have been trying to help with
the project, I have to get familiar with Jira to be able to help with
little changes.
I cannot imagine how much more work others that are contributi
I've seen multiple Apache projects using GitHub for issue tracking, but are
not really positive examples.
Often they don't use the milestones and labels available, I'd be sad if
we'd end up with that style.
GitHub on it's own is usually good enough if used correctly, when it's
helped with bots.
Th
Hi Joris,
On Mon, 1 Mar 2021 19:04:08 +
Joris Peeters wrote:
>
> Given the above,
> - does it sound sensible to contribute only read for now, or should we aim
> wider and do write as well?
It does sound reasonable to contribue only read.
> - should this be a new JIRA or fall under
> http
Hi Jorge,
On Tue, 2 Mar 2021 08:55:03 +0100
Jorge Cardoso Leitão wrote:
> Hi,
>
> FWIW, the amount of bureaucracy that goes into JIRA is a major contributing
> factor for the reduction of my time commitment to this project by 80%+.
Can you expand a bit on this? In particular, which aspects o
Hi Eduardo,
Thanks for chiming in. Just one precision:
On Tue, 02 Mar 2021 06:41:54 -
Eduardo Ponce wrote:
> In my experience there is no single SIMD library that wraps all possible set
> of vector instructions across the most common architectures and at the same
> time provides support
I prefer keeping Jira. Simply because I'm familiar with it and use it in daily
work.
I will log detailed progresses, findings and todos for non-trivial tasks in
Jira comments. It does helps me.
Yibo
From: Sutou Kouhei
Sent: Tuesday, March 2, 2021 9:47 AM
To: de
30 matches
Mail list logo
