Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Write-up, README, demo video, launch

Aperta
  • Qualcosa non va?
#93 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
huggingface
Ambito
documentation, machine-learning, mobile-dev

Direzione di ricerca

Start with docs/WRITEUP.md, the README, and the linked design and issue-plan documents after #90 and #92 are complete. Verify one evaluation run from a fresh clone using only the README, and link each claim to a results file, evidence folder, or HF card. Done means the reproduction works and the README/write-up, video, links, and resume bullet are backed by committed evidence.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:docs

Part of the JobTrail v2 rebuild · design doc · all drafts · draft #32

Depends on: #90, #92

Scope

  • Write-up (blog + docs/WRITEUP.md): "Can a 270M model replace an API call?" — problem, market gap, data, ladder, fine-tune, quantization on a budget phone, failure taxonomy, what didn't work.

  • README: headline number, live link, APK/Play link, 90-second airplane-mode video, reproduce-in-one-command, architecture diagram.

  • Resume bullet with real numbers.

  • Optional, owner's call: share the write-up in ML communities (e.g., r/LocalLLaMA, Hugging Face). Describe testing honestly as developer role-play, not user research.

Acceptance criteria

  • Every claim in README/write-up links to an artifact (results file, evidence folder, HF card).

  • Fresh-clone reproduction of one eval run verified by following README only.

Definition of done (all issues)

Definition of done (every issue):

  • Acceptance criteria met with evidence linked in the closing comment (test run, results JSON, screenshot/recording).

  • needs-device issues: benchmark JSON + short screen recording from the named device committed under evidence/<issue#>/.

  • No claim in README/docs that isn't backed by a committed artifact.

  • CI green.

Device shorthand: Note 9S = Redmi Note 9S 6 GB (Snapdragon 720G, CPU-only), the minimum-spec device. iPhone = iPhone 16 Pro.

Budget rule: free tiers first (Gemini API free tier, Kaggle/Colab free GPUs, HF Hub, Vercel Hobby). Any script calling a cloud model must throttle to free-tier limits, checkpoint/resume, and log token usage. Paid spend only with owner approval, capped at a few dollars.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
14h 46m
PR unite (30g)
21

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Taleef7/JobTrail

Tutte le issue di Taleef7/JobTrail

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.