nhcarrigan/docs
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 2 Pull Requests 6 Actions Releases 1 Activity

docs(mentorship): clarify style guide and IP ownership for flagship projects #30

Merged
naomi merged 1 commits from fix/style into main 2026-02-27 14:24:17 -08:00
Conversation 0 Commits 1 Files Changed 2
+8 -4
hikari commented 2026-02-27 14:18:44 -08:00
Owner
Copy Link
Copy Source

Summary

Mentorship programme participants were confused about whether NHCarrigan's style guide (including copyright headers and Naomi's Public Licence) applied to their own flagship projects. This PR adds clear clarifications in the relevant docs:

  • dev/style.md: Tightened scope language to "NHCarrigan-maintained repositories" and added an explicit note for mentorship participants that the style guide (including Section 2.1 copyright/licensing) does not apply to their flagship projects
  • mentorship/07-writing-code.md: Updated the scope note to remove Style Guide and Contributor Covenant requirements; replaced with a clear statement that participants must follow the Community Code of Conduct and Community Guidelines, and must not use their repository for illegal, harmful, discriminatory, or bigoted content; added Section 7.3 explicitly stating that NHCarrigan makes no IP claim over flagship projects and participants are free to choose their own licence and style standards

✨ This PR was created with help from Hikari~ 🌸

## Summary Mentorship programme participants were confused about whether NHCarrigan's style guide (including copyright headers and Naomi's Public Licence) applied to their own flagship projects. This PR adds clear clarifications in the relevant docs: - **`dev/style.md`**: Tightened scope language to "NHCarrigan-maintained repositories" and added an explicit note for mentorship participants that the style guide (including Section 2.1 copyright/licensing) does not apply to their flagship projects - **`mentorship/07-writing-code.md`**: Updated the scope note to remove Style Guide and Contributor Covenant requirements; replaced with a clear statement that participants must follow the [Community Code of Conduct](/community/coc) and [Community Guidelines](/community/guide), and must not use their repository for illegal, harmful, discriminatory, or bigoted content; added Section 7.3 explicitly stating that NHCarrigan makes no IP claim over flagship projects and participants are free to choose their own licence and style standards ✨ This PR was created with help from Hikari~ 🌸
hikari added 1 commit 2026-02-27 14:18:44 -08:00
docs(mentorship): clarify style guide and IP ownership for flagship projects
Node.js CI / CI (pull_request) Successful in 1m4s
Details
Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m24s
Details
c4eef609ec
naomi merged commit b6b3ef01ad into main 2026-02-27 14:24:17 -08:00
naomi deleted branch fix/style 2026-02-27 14:24:17 -08:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/docs#30
Delete Branch "fix/style"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?