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

Unspecified License (?)

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the BSD-style license reference in config.go at the linked line and check the repository for a LICENSE, COPYING, or substitute file. Confirm the intended BSD license with the maintainers, then document that choice in the repository so downstream packagers can identify it.

Written by the indexing model from the issue text.

Description

Dear LinuxBoot - Team,

I'd like to consider adding corebootnerf to the package wishlist of OS/1337 and subsequently it's planed repository which necessitates a license to be specificed.

  • The config.go file's "BSD-tyle License" nor any LICENSE file (or substitute like COPYING or whatever) is nowhere to be found.

I'd be fine with just a clarification which BSD license it is.

  • Even if it's just 0BSD which I use (or whatever fits your purposes. After all, your project doesn't seem to use copyleft licenses and even if it did that would be fine by me.)...

Yours faithfully,

Kevin Karhan
OS/1337 developer / maintainer

PS: I do like the idea of LinuxBoot very much and would love to make OS/1337 be directly integrateable as a minimalist "toybox + musl / linux distro" to boot into as a low-level integrated recovery system.

  • Also I'd see it as a better "Evaluation-capable OS" since Microsoft Lobbyists made it basically illegal to sell complete PCs without a preinstalled OS in Germany (Which is why HP ships FreeDOS on their cheapest non-Windows preinstalled offerings!)...
Dominant language
Go
Stars
10
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 linuxboot/corebootnerf

All issues in linuxboot/corebootnerf

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.