Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xuanwo Weekly Plan since 2024-08-12 #5

Closed
Xuanwo opened this issue Aug 12, 2024 · 2 comments
Closed

Xuanwo Weekly Plan since 2024-08-12 #5

Xuanwo opened this issue Aug 12, 2024 · 2 comments

Comments

@Xuanwo
Copy link
Owner

Xuanwo commented Aug 12, 2024

My Goal: Rewrite Bigdata in Rust

It would be great for other open source contributors to make them visible somehow as well 🙏 (feel free to copy / modify the format of this ticket)

Algorithm for my prioritizing PR reviews

Priority:

  • CI fixes (CI is the crucial link between maintainers and contributors)
  • Bug fixes (where something is just incorrect), especially regressions (where it used to work and now does not)
  • Improvements directly related to features needed
  • Documentation and test improvements (I view these as very strategically important)
  • PRs for other features I think are strategically important (See below)
  • Other new features / additions to functionality (note this is the lowest on purpose)

The top strategically important projects in my head are:

  • Improved performance (with benchmarks -- this is higher in my mind now)
  • Anything that improves code quality such as bug fixes, and improved / expanded tests, etc
  • Anything that makes it easier to use as a user (docs, examples, better APIs, etc)

Thus, if you are interested in contributing to projects I maintained and are interested in a fast turn around time I would recommend looking into bug fixes / test improvements / documentation or the projects named above.

If you propose adding new functionality, especially if the PR is large/complex and not connected to a wider need, 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, the CI passes, includes documentation, etc)

Background

Follow up of #4

The idea is used for my own personal organizational needs, but also to:

  • Communicate / coordinate in the community
  • Help provide an interesting summary of what is happening in my projects this week (both for my future self and others)
@Xuanwo
Copy link
Owner Author

Xuanwo commented Aug 12, 2024

@Xuanwo Xuanwo pinned this issue Aug 12, 2024
@Xuanwo Xuanwo closed this as completed Aug 19, 2024
@Xuanwo Xuanwo unpinned this issue Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant