Skip to content

DataFusion weekly project plan (Andrew Lamb) - Dec 4, 2023 #8420

Closed
@alamb

Description

@alamb

Follow on to Nov 27 2023:

Boilerplate Overview

The idea of this ticket is make my plans for DataFusion visible, largely for my own personal organizational needs, but also to:

  1. Try some different ways to communicate / coordinate in the community
  2. Help provide an interesting summary of what is happening in DataFusion this week

It would be great if anyone else who has plans like this for DataFusion could try to make them visible somehow as well

My (personal) plans for this week

Project Queue (list of future projects)

Additional major projects I hope to help review and coordinate

Algorithm for (my) prioritizing PR reviews

Note there are many committers who can review and merge PRs as well, so this is not the priorities of the project as a whole, just the approximate algorithm I am using

Priority:

  1. Bug fixes (where something is just incorrect), especially regressions (where it used to work and now does not)
  2. Improvements directly related to features needed for InfluxDB (as I am employed by them)
  3. Documentation and test improvements (I view these as very strategically important)
  4. PRs that I think are strategically important
  5. Other new features / additions to functionality

The current strategically important projects in my head are:

Note that adding new array functionality (e.g. #6980 and its children) is very low on my priority list, not because I don't think they are valuable, but because I think they are less valuable than the other projects going on - it would be great if other people could help pick these up too.

Thus, if you are interested in contributing to DataFusion and are interested in a fast turn around time I would recommend looking into bug fixes / test improvements / documentation / etc.

If you propose adding new functionality, the review cycle will likely be longer. You can make it a shorter cycle by looking at the comments on other recent PRs and following the same model (e.g. ensure there are tests in sqllogictest for example)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions