Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
Description
It would be convenient to remind users about ensuring the repository is properly licensed when making a Pull Request.
Something along the lines of:
- [ ] The repository is licensed (MIT/Apache-2.0 are suggested if not).
This is a rough proof of concept.
Originally created by @DrKJeff16 on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1724
Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
## Description
It would be convenient to remind users about ensuring the repository is properly licensed when making a Pull Request.
Something along the lines of:
```markdown
- [ ] The repository is licensed (MIT/Apache-2.0 are suggested if not).
```
This is a rough proof of concept.
I was about to open the same exact issue. This has 100% my backing.
<!-- gh-comment-id:3419943748 -->
@Penaz91 commented on GitHub (Oct 19, 2025):
> [@Penaz91](https://github.com/Penaz91) Thoughts?
I was about to open the same exact issue. This has 100% my backing.
Maybe we can hint why we want a license. Because otherwise it is copyright so people copying it might be tricky legally.
Possibly:
The plugin has a license. (GPL/MIT/Apache-2.0 are common plugin licenses)
Suggesting feels a little strong, even though it is like that in the maintainers document. The right license for them might depend on different factors. So mentioning common ones might just be enough grounding.
Let me know what you think
<!-- gh-comment-id:3423930302 -->
@rockerBOO commented on GitHub (Oct 20, 2025):
Maybe we can hint why we want a license. Because otherwise it is copyright so people copying it might be tricky legally.
Possibly:
- The plugin has a license. (GPL/MIT/Apache-2.0 are common plugin licenses)
Suggesting feels a little strong, even though it is like that in the maintainers document. The right license for them might depend on different factors. So mentioning common ones might just be enough grounding.
Let me know what you think
I agree @rockerBOO. Though I believe the example still conceals a suggestion, even if a slight one.
I have an idea:
Mention licensing in CONTRIBUTING.md
Or...
- [ ] The plugin is licensed appropriately.
Perhaps?
<!-- gh-comment-id:3424255534 -->
@DrKJeff16 commented on GitHub (Oct 21, 2025):
I agree @rockerBOO. Though I believe the example still conceals a suggestion, even if a slight one.
I have an idea:
- Mention licensing in `CONTRIBUTING.md`
- Or...
```markdown
- [ ] The plugin is licensed appropriately.
```
Perhaps?
---
I would prefer the checkbox, I personally prefer having such important thing always visible.
The wording is something we can discuss about, my priority would probably be having a memo of the main things to check for us maintainers, as well as a memo for contributors about what we're looking for.
<!-- gh-comment-id:3424848550 -->
@Penaz91 commented on GitHub (Oct 21, 2025):
I would prefer the checkbox, I personally prefer having such important thing always visible.
The wording is something we can discuss about, my priority would probably be having a memo of the main things to check for us maintainers, as well as a memo for contributors about what we're looking for.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DrKJeff16 on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/1724
Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
Description
It would be convenient to remind users about ensuring the repository is properly licensed when making a Pull Request.
Something along the lines of:
This is a rough proof of concept.
@DrKJeff16 commented on GitHub (Oct 19, 2025):
@Penaz91 Thoughts?
@Penaz91 commented on GitHub (Oct 19, 2025):
I was about to open the same exact issue. This has 100% my backing.
@rockerBOO commented on GitHub (Oct 20, 2025):
Maybe we can hint why we want a license. Because otherwise it is copyright so people copying it might be tricky legally.
Possibly:
Suggesting feels a little strong, even though it is like that in the maintainers document. The right license for them might depend on different factors. So mentioning common ones might just be enough grounding.
Let me know what you think
@DrKJeff16 commented on GitHub (Oct 21, 2025):
I agree @rockerBOO. Though I believe the example still conceals a suggestion, even if a slight one.
I have an idea:
CONTRIBUTING.mdPerhaps?
@Penaz91 commented on GitHub (Oct 21, 2025):
I would prefer the checkbox, I personally prefer having such important thing always visible.
The wording is something we can discuss about, my priority would probably be having a memo of the main things to check for us maintainers, as well as a memo for contributors about what we're looking for.