Make the Hermes VFD non-terminal

Open
  • Is something wrong?
#522 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points. First map the existing VFD implementation and its backend-routing architecture, then clarify the expected non-terminal behavior and acceptance criteria for routing data to backends such as S3.

Written by the indexing model from the issue text.

Description

Non-terminal VFD allows Hermes to route data to different backends, such as S3, without any additional programming.

Dominant language
C++
Stars
34
Forks
19
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 HDFGroup/hermes

All issues in HDFGroup/hermes

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.