starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Gain CII Best Practices certification #2939

New Issue
Closed
opened 2025-12-29 18:23:46 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:23:46 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Oct 8, 2019).

Proposed Changes

Review our processes and policies to ensure we are in compliance with Linux Foundation CII Best Practices. This deals more with project administration than the code itself.

Justification

While obtaining the badge itself doesn't carry any particular significance, the criteria established by the plan provides an excellent benchmark for a mature project. We likely already meet most criteria, and achieving full compliance shouldn't take much work.

Originally created by @jeremystretch on GitHub (Oct 8, 2019). ### Proposed Changes Review our processes and policies to ensure we are in compliance with Linux Foundation [CII Best Practices](https://bestpractices.coreinfrastructure.org/en). This deals more with project administration than the code itself. ### Justification While obtaining the badge itself doesn't carry any particular significance, the [criteria established by the plan](https://github.com/coreinfrastructure/best-practices-badge/blob/master/doc/criteria.md) provides an excellent benchmark for a mature project. We likely already meet most criteria, and achieving full compliance shouldn't take much work.
adam added the type: housekeeping label 2025-12-29 18:23:46 +01:00
adam closed this issue 2025-12-29 18:23:46 +01:00
adam commented 2025-12-29 18:23:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 15, 2019):

After review, I think we meet nearly all of the requirements with the exception of strong static code analysis. We run pycodestyle as part of our CI process, but that only enforces style rules. Something like pylint would be more robust. However, it would also take a good amount of effort to bring the entire code base into compliance. This might be something to undertake during a beta period.

@jeremystretch commented on GitHub (Nov 15, 2019): After review, I think we meet nearly all of the requirements with the exception of strong static code analysis. We run `pycodestyle` as part of our CI process, but that only enforces style rules. Something like `pylint` would be more robust. However, it would also take a good amount of effort to bring the entire code base into compliance. This might be something to undertake during a beta period.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2939
Delete Branch "%!s()"

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?