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

Agree on notation for far UVC

Open
#94 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
documentation

Research direction

Review the issue’s examples of code identifiers and written forms, then check the repository for current usage to understand the inconsistency. The issue asks contributors to agree on a consistent notation, but the discussion has had no comment for 249 days and does not record a decision; done would require a settled convention.

Written by the indexing model from the issue text.

Description

low priority

In code I have seen far_uvc and uvc.

In writing (including comments) I have seen far UVC, Far UVC, Far-UVC, Far UvC.

Could we vote on which to use and be consistent?

I vote uvc and "far UVC".

Reason: in code we don't need to be specific that it's "far" -- who is going to be confused? In writing, I'm not sure why Far is being capitalised and I don't see reason for -.

Dominant language
R
Stars
8
Forks
4
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 petal-code/helios

All issues in petal-code/helios

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.