State of the repository?

Open
#63 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, cpp
Domain
api, backend

Research direction

No source file, test, or entry point is named. Start by reviewing the master branch history and the v7.. and v8.0.0 tags; done means the repository's maintenance status and a supported C/C++ schema-registry interaction path are documented.

Written by the indexing model from the issue text.

Description

Can anyone shed some light on the state of this repository? It looks like maybe a Jenkins bot went nuts and merged and tagged a bunch of things?

There is a v8.0.0 tag in the repository, but most recently on the master branch (2023-04-6), there were a bunch of merges. And a bunch of tags all on the same commit. For instance, it look like there are man v7.. tags all pointing to the top of tree, and all strangely newer than v8.0.0.

Is this code abandoned? Is there any plan to revive it? Is there any other way to sanely interact with the schema registry from C/C++?

Dominant language
C
Stars
12
Forks
62
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from confluentinc/libserdes

All issues in confluentinc/libserdes

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.