Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

VMNL/vmnl-net

Sign in to follow View on GitHub

Networking library in C, part of the VMNL project

Is VMNL/vmnl-net beginner-friendly?

In the last 30 days, VMNL/vmnl-net merged 28 of 28 pull requests from outside contributors, and its maintainers usually reply within 1 day. No beginner-friendly issue is open right now; the list below has the other issues we hold for it.

Stars
0
Forks
0
Open beginner issues
0
Indexed issues
17
Avg merge
25m
Merged PRs (30d)
28
Dominant language
C
License
MIT
Last GitHub push
Oct 18, 2026
Latest indexed
Oct 21, 2026
Contributing guide
No code of conduct
Beginner labels
good first issue help wanted

How to contribute to VMNL/vmnl-net

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Your contributions will be published under the project's MIT license.
  3. Follow the repository to hear when a new beginner-friendly issue opens, or look through the other issues below.
Beginner friendly Everything
Open All

Issues somebody may already be working on are listed last. List everything by date

  • docs: show a Python binding of the C ABI with ctypes
    Open
    • Is something wrong?
    area:docs help wanted type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 76/100

    VMNL/vmnl-net#57 ·

    Maintainers usually reply within 1 day

  • test: write the benchmarks of the version and the error messages
    Open
    • Is something wrong?
    area:core area:error good first issue impact:performance type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 85/100

    VMNL/vmnl-net#55 ·

    Maintainers usually reply within 1 day

  • test(context): write the benchmarks of the context
    Open
    • Is something wrong?
    area:context good first issue impact:performance type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 88/100

    VMNL/vmnl-net#54 ·

    Maintainers usually reply within 1 day

  • test(clock): write the benchmarks of the clock
    Open
    • Is something wrong?
    area:clock good first issue impact:performance type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 88/100

    VMNL/vmnl-net#53 ·

    Maintainers usually reply within 1 day

  • docs: rewrite the clock example for the reworked core
    Open
    • Is something wrong?
    area:clock good first issue type:documentation

    Difficulty 2/5 1-3 hours Newbie friendliness 88/100

    VMNL/vmnl-net#52 ·

    Maintainers usually reply within 1 day

  • cicd: benchmark the features at each release
    Open
    • Is something wrong?
    area:ci area:release impact:performance type:enhancement

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    VMNL/vmnl-net#45 ·

    Maintainers usually reply within 1 day

  • feat(log): add logging hooks
    Open
    • Is something wrong?
    area:log impact:api type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 42/100

    VMNL/vmnl-net#44 ·

    Maintainers usually reply within 1 day

  • feat(error): map the system errors to the error codes
    Open
    • Is something wrong?
    area:error impact:portability type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 49/100

    VMNL/vmnl-net#43 ·

    Maintainers usually reply within 1 day

  • feat(socket): add UDP sockets
    Open
    • Is something wrong?
    area:socket impact:api type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 50/100

    VMNL/vmnl-net#42 ·

    Maintainers usually reply within 1 day

  • feat(socket): add TCP sockets
    Open
    • Is something wrong?
    area:socket impact:api type:enhancement

    Difficulty 5/5 Over a week Newbie friendliness 30/100

    VMNL/vmnl-net#41 ·

    Maintainers usually reply within 1 day

  • feat(socket): add a non-blocking wrapper over Winsock2 and BSD sockets
    Open
    • Is something wrong?
    area:socket impact:api impact:portability type:enhancement

    Difficulty 5/5 Over a week Newbie friendliness 35/100

    VMNL/vmnl-net#40 ·

    Maintainers usually reply within 1 day

  • feat(timer): rework the timers for the network loop
    Open
    • Is something wrong?
    area:timer impact:api impact:breaking type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 45/100

    VMNL/vmnl-net#39 ·

    Maintainers usually reply within 1 day

  • feat(buffer): rework the buffer API around flat, ring and chunk buffers
    Open
    • Is something wrong?
    area:buffer impact:api impact:breaking type:enhancement

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    VMNL/vmnl-net#38 ·

    Maintainers usually reply within 1 day

  • feat(error): add the error codes of the network layer
    Open
    • Is something wrong?
    area:error impact:api type:enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    VMNL/vmnl-net#37 ·

    Maintainers usually reply within 1 day

  • feat(allocator): replace the allocator for the whole library
    Open
    • Is something wrong?
    area:allocator impact:api impact:breaking type:enhancement

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    VMNL/vmnl-net#36 ·

    Maintainers usually reply within 1 day

  • refactor: follow the naming conventions of the VMNL repository
    Open
    • Is something wrong?
    impact:api impact:breaking type:maintenance

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    VMNL/vmnl-net#35 ·

    Maintainers usually reply within 1 day

  • feat(buffer): view buffers as any number of segments
    Open
    • Is something wrong?
    area:buffer impact:api impact:breaking type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 48/100

    VMNL/vmnl-net#34 ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.