Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Feature: Add authentic NATO (APP‑6 / MIL‑STD) & OPFOR/BLUFOR markers — include licensing/legal checklist

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
android, kotlin
领域
documentation, mobile-dev

调研方向

先阅读 MilitarySymbolPicker.kt、TacticalUnitsMapOverlay.kt、LocationEntity 和 TacticalUnitEntity，梳理现有的符号字段和 fallback 行为。在选择内部制作或采用宽松许可证的符号源之前，检查 asset pipeline 和项目测试设置。完成意味着 picker 和地图渲染支持符号、归属、修饰符、持久化和 fallback marker，具备测试或 QA 检查，并记录 asset 许可信息。

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

描述

enhancement help wanted priority: low UI/UX

Summary

Add authentic NATO-style military symbols (APP‑6 / MIL‑STD family) and OPFOR/BLUFOR marker variants to the map symbol set and symbol picker. Ensure all assets are permissively licensed (or created in-house) and documented with a licensing checklist.

Why

  • Current markers are simplified (colored circle + letter + arrow). The UI already discovers drawables with prefix ic_mapicon_ (MilitarySymbolPicker.kt) and supports symbol fields in the DB (LocationEntity/TacticalUnitEntity).
  • Authentic symbols improve clarity and realism for tactical workflows and training.
  • We must ensure assets are free-to-use or have proper attribution to avoid legal issues.

Proposed work

  1. Add a canonical set of vector-based NATO / MIL‑STD symbols (SVG → Android VectorDrawable or runtime vector render). Prefer CC0/MIT/Apache or create in-house icons.
  2. Extend MilitarySymbolPicker to preview and select real symbols, affiliation colors, and modifiers.
  3. Update TacticalUnitsMapOverlay to render vector symbols with affiliation coloring and fall back to circle markers when none assigned.
  4. Add DB migration or mapping scripts if needed, tests, QA checks, and sample data.

Acceptance criteria

  • Picker saves a NATO symbol + affiliation into symbolSet, symbolEntity, symbolAffiliation, symbolColor.
  • Map displays vector-drawn NATO symbols (units + static locations) with correct color and modifiers; heading arrows still render for applicable units.
  • Legacy circle-letter markers remain as fallback.
  • All new symbol assets include license metadata or are created in-house and documented.
  • README/docs updated with asset origin and licensing guidance.
  • Tests and QA checklist completed (zoom/rotation/high-density scenarios).

Tasks

  • Research permissive MIL‑STD/APP‑6-compatible symbol sources (record licenses & links).
  • Convert chosen SVGs to Android VectorDrawable or add runtime SVG renderer.
  • Update MilitarySymbolPicker.kt to show symbol previews and affiliation colorings.
  • Implement symbol rendering in TacticalUnitsMapOverlay.kt (vector draw + color + modifiers).
  • Add migrations or mapping code for existing icons -> new symbol fields.
  • Add integration/UI tests and manual QA checklist.
  • Add /assets/licenses with attribution & license files.
  • Legal review / sign-off for third-party assets (if used).

Licensing & legal checklist

  • Prefer CC0 / MIT / Apache 2.0 assets or create icons in-house.
  • For third-party assets: include source link, license file, and required attribution in /assets/licenses or NOTICE.
  • Avoid trademarked logos (e.g., NATO crest) unless permission is granted.
  • If uncertain, create a stylized in-house APP‑6 compatible set to avoid legal risk.
主要语言
Kotlin
星标
41
派生
4
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

arn-c0de/InteractiveChecklists 的其他 Issue

查看 arn-c0de/InteractiveChecklists 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

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