all-contributors VS re_data

Want to learn more? You can watch my video or directly head over the all-contributors website.

There are many ways to recognize contributions outside of GitHub repositories. Tools such as All Contributors provide a common way to recognize many different types of contributions, from code, to docs, and more. Contributions can also be recognized in the form of shoutouts on social media, upgraded roles on Discord or Slack channels, and access to internal chats for more focused conversations. These external interactions go a long way in building community and engagement around your project and encourage future contributors to come onboard.

Starlite is a community driven project - it's a core pillar of Starlite to have multiple maintainers and be as open, inviting and accessible for contributions as we can be. The project follows the all-contributors specification and we attribute all types of contribution - code, testing, refactoring, code reviews, documentation, design of the docs, writing and evangelizing etc.

To emphasize how important this is to us, Starlite now follows the all-contributors specification!

The developers at Smart Walkie Pte. Ltd. are full time maintainers of the code. So if you have issues or find bugs, don’t hesitate to report to us. We also welcome all contributions from the community, not just code, but any contribution, for example updating the documentation or hinting a typo.

This project follows the all-contributors specification. Contributions of any kind welcome!

There’s also this open source tool I think is doing kind of what the OP is looking for, re_data. The source code lives here: https://github.com/re-data/re-data

What are the 5 hottest dbt Repositories one should star on Github 2022?

dbt is a software framework that sits in the middle of the ELT process. It represents the transformative layer after loading data from an original source. Dbt combines SQL with software engineering principles.

Here are my top5!

- Lightdash (https://github.com/lightdash/lightdash): Lightdash converts dbt models and makes it possible to define and easily visualize additional metrics via a visual interface.

- ⏎ re_data (https://github.com/re-data/re-data): Re-Data is an abstraction layer that helps users monitor dbt projects and their underlying data. For example, you get alerts when a test failed or a data anomaly occurs in a dbt project.

- evidence (https://github.com/evidence-dev/evidence): Evidence is another tool for lightweight BI reporting. With Evidence, you can build simple reports in "medium style" using SQL queries and Markdown.

- Kuwala (https://github.com/kuwala-io/kuwala): With Kuwala, a BI analyst can intuitively build advanced data workflows using a drag-drop interface on top of the modern data stack without coding. Behind the Scenes, the dbt models are generated so that a more experienced engineer can customize the pipelines at any time.

- fal ai (https://github.com/fal-ai/fal): Fal helps to run Python scripts directly from the dbt project. For example, you can load dbt models directly into the Python context which helps to apply Data Science libraries like SKlearn and Prophet in the dbt models.

re_data ( https://github.com/re-data/re-data ) Re_data is an abstraction layer that helps users monitor dbt projects and their underlying data. For example, you get alerts when a test failed or a data anomaly occurs in a dbt project and which underlying metric is affected. In addition, the lineage graph is also intuitively displayed. Re-data is one of two others frameworks focusing on the observability aspect of lengthy pipelines in dbt (check also out: open-metadata and Elementary).

- ⏎ re_data: Re-Data is an abstraction layer that helps users monitor dbt projects and their underlying data. For example, you get alerts when a test failed or a data anomaly occurs in a dbt project.

Some things you might be interested in are re_data and Elementary Data.

Around a year ago I launched re_data (an open-source data reliability tool) here. After some pivots, we seem to be getting traction and this is how it looks now: https://www.getre.io/. Super interested in getting your feedback and suggestions on the direction :)

Nice project, at re_data we just got over a lot of your new updates and it seems a quite large part of your project is "inspired" by code from our library https://github.com/re-data/re-data. Even with parts, we are not especially proud of ;)

If you decide to copy not only ideas but a big part of internal implementation, I think you should include that information in your LICENSE.

Cheers

It's more convenient when you are already using dbt and don't want to set up a separate workflow for testing data when it can be done with dbt inside the data warehouse. Also the thing re_data does well is letting you create time-based metrics about your data quality instead of just tests (a lot of the tests can be rewritten to that) That allows you to do a couple of things more than GE, you can for example easily visualize or look for anomalies in those. You can also compute tests much more efficiently. Research about computing metrics as a good way of doing data quality was actually done by the team behind deequ: http://www.vldb.org/pvldb/vol11/p1781-schelter.pdf I'm the author, so obviously I'm a bit biased :)