localstack / localstack/verdin

Consider archiving verdin

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
23
Forks
0
PR merge metrics
No merged PRs in 30d

Description

With the release of Tinybird's own Python SDK tinybirdco/tinybird-sdk-python, we can now consider archiving verdin 🥳

Most things that verdin provided were API wrappers, which are now covered by the tinybird-python-sdk.

The only thing to consider as something that may add value is the worker concept. So verdin could become a re-usable higher-level layer on top of the tinybird sdk.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare verdin's existing API-wrapper scope with the tinybird-sdk-python linked in the issue. Read verdin/worker.py to assess whether the worker concept is a reusable higher-level layer. Done means reaching a clear decision to archive verdin or retain and reshape it around workers.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.