livepeer / livepeer/go-livepeer

Console Output (and Code (and Comments)) still refer to "Broadcaster"

Open
#3,789 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: triage
Dominant language
Go
Stars
586
Forks
226
Avg merge
1d 17h
Merged PRs (30d)
19

Description

Describe the bug

There are still references to the "Broadcaster" actor in the code, comments and operation. This is confusing for people using the software, and also to developers wanting to contribute to the software.

To Reproduce

Look at the code, watch the console output, look for references to "Broadcaster". Alternatively, do a search in github for the word "broadcaster" and see how many you can find.

Expected behaviour

I expect that all references to "Broadcaster" are replaced with references to "Gateway". This should be done as a refactoring exercise throughout, in function names and other code, comments, text strings. It need to be consistent and clear and not confusing.

Screenshots

Image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

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

Search the repository for "Broadcaster" and "broadcaster", then inspect each code reference, console string, function name, comment, and operation mentioned in the issue. Replace applicable references with "Gateway" consistently and verify that no unintended Broadcaster references remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.