Roadmap: ecosystem profiles for every kind of project

未关闭
  • 哪里不对？
#105 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
cmake, python
领域
tooling

调研方向

Read project_validator/ecosystems/<name>.py, project_validator/rules.py, and tests/test_ecosystem_contract.py to understand the profile design and its contract. The roadmap lists many separate ecosystem profiles and checks, while #107 defines execution order; use it to identify an actionable step. Done means implementing the selected profile with its well-configured and bare fixtures, passing the contract test.

由索引模型根据 Issue 内容生成。

描述

Roadmap for judging every kind of project by its own ecosystem's tools. The design is in place on ecosystem-profiles: ecosystem profiles (project_validator/ecosystems/<name>.py), typed rules (project_validator/rules.py), generic @practice checks, build-system rules, plugin ecosystems, CI job attribution, and a contract test (tests/test_ecosystem_contract.py) holding each profile to a well-configured and a bare fixture. Built in so far: C/C++ (CMake, Meson), Python, Rust, Go.

Adding an ecosystem means one profile module and two fixtures, with no change to project_validator/checks/.

Core
  • #62
  • #63
  • #64
Languages, wave 1
  • #65
  • #66
  • #67
  • #68
  • #69
  • #70
Languages, wave 2
  • #71
  • #72
  • #73
  • #74
  • #75
  • #76
  • #77
  • #78
  • #79
  • #80
  • #81
  • #82
  • #83
Data, schemas and documents
  • #84
  • #85
  • #86
  • #87
  • #88
  • #89
  • #90
  • #91
  • #92
Infrastructure
  • #93
  • #94
  • #95
  • #96
  • #97
  • #98
Checks for every project
  • #99
  • #100
  • #101
  • #102
  • #103
  • #104
Checks that grow with each profile

Built, and judged by each profile's rules: tests-run, coverage, code-formatting, compiler-warnings, warnings-as-errors, hardening (binary hardening only, #61), security-scanning (each language's security lints), dependency-audit, function-limits, vcs-ignore, platform-matrix, ci-build-types.

Planned: #10 #13 #16 #21 #24 #30 #31 #56 #57 #58 #60

Order of execution

See #107 for the order this work is done in, and the rules every step follows.

主要语言
Python
星标
4
派生
1
平均合并
10 小时 41 分钟
30 天内合并 PR
79

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

cpp-best-practices/project_validator 的其他 Issue

查看 cpp-best-practices/project_validator 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。