Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Reader 0.2 release repair and ready-backlog consolidation

Open
  • Is something wrong?
#275 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@andy-zen-dev is already working on this.

Since Oct 18, 2026.

  • #276 by @andy-zen-dev — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start with the existing scrip-site-two-full-work-gallery branch at c411e29030e7e778f99cd9689441d348f75a7715, the Reader integration in #274, and site_renderer.py; inspect open PR #276 before touching the work. Verify the publisher crash recovery and concurrent publication regressions, then run full repository CI, an installed wheel smoke test, and a deterministic site rebuild on the successor's exact head. Done means the stated acceptance criteria pass together while preserving the branch histories and current master changes.

Written by the indexing model from the issue text.

Description

Owner-requested delivery cleanup, 2026-10-18. #268 and #272 are now merged into master; #267/#271 closed. The remaining executable product issues are #269 and #273. #265 has separate missing administration/branch-deletion capabilities, not an analyzer blocker.

Delivery claim

Reuse the existing un-PR'd scrip-site-two-full-work-gallery branch at c411e29030e7e778f99cd9689441d348f75a7715 for one successor PR against current master. Preserve its three unique gallery files, adopt the existing Reader integration from #274 without reimplementation, fix the exact site_renderer.py syntax regression and verify the pending crash-safe publisher patch. Preserve the original histories and all current master changes. #270/#274 stay as provenance until the successor is accepted; do not start another competing integration.

Acceptance

  • One runnable installable Reader with all existing 29 metrics, private bounded UTF-8 input, JSON/HTML/CSV and canonical five-route site.
  • Full repository CI, clean installed-wheel smoke and deterministic site rebuild on the successor's exact head. Crash recovery/concurrent publication regressions; no weakened tests or publication allow-list.
  • Reuse and verify the two-work source-free gallery; no new literary text or parity claim.
  • Refresh the existing compact queue, reconcile delivery-oriented ownership into local instructions, and add the next key roadmap tasks with acceptance and scoped dependencies.
  • No same-run merge of the repaired semantic change. No scheduler, access, visibility, administrative or external registry change.

M1-M5 completion remains unclaimed; M2 remains 0/5.

Dominant language
Python
Stars
4
Forks
0
Avg merge
10h 58m
Merged PRs (30d)
78

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from drevendev/Scriptorium

All issues in drevendev/Scriptorium

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.