[P3][Creative] Small music/literary release story pack without merging public personas

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
content

Research direction

Start by reading the implementations or notes for media manifest #51 and editorial check #53, then trace how PatchPitch selects sources and edits channel drafts. Test the experiment with one owner-approved existing release and its verified facts, credits, rights, and destination links. Done means two publishable drafts preserve the artist identity and factual attribution; if producing them takes more setup than writing a post, mark the experiment NOT_USEFUL and stop.

Written by the indexing model from the issue text.

Description

enhancement бэклог

Purpose and fit test

The owner also publishes human-made music and literary texts through distinct creative identities, with some existing musicto/Spotify campaign preparation. A narrowly scoped release-announcement/story pack may reuse PatchPitch's existing source-selection and channel editor, but becoming a music distributor, pitching service or one identity graph would be a pivot.

Research/MVP (ship only after one real approved test)

  • Accept owner-supplied verified track/release facts, exact artist persona, album/track title, credits/rightsholders, canonical Spotify/SoundCloud/owned links, the background story that can be publicly disclosed, lyric excerpt only with explicit rights and needed AI disclosure.
  • Outputs: one short genuine artist post, one longer story/press note, one reviewer/curator note without claims of acceptance, and one media/checklist of approved cover/art/audio links.
  • Keep public identities separate; the maker/gamer identity must not automatically cross-post a literary or music project. No persona-merging from shared owner metadata.
  • Truthful attribution: original human-made music and main artwork when the owner verifies it; do not generate invented credits, collaborators, streaming counts, audience size or playlist placement. Never assume Spotify identity from fuzzy name search.
  • Reuse media manifest #51 and editorial check #53; NO uploads to streaming services, song generation, fake outreach or mass curator emails.

Acceptance and stop rule

One owner-approved existing track/release yields 2 publishable drafts with correct destination links and factual credits, without mixing artist identities. If making those drafts involves more setup than simply writing a post, mark the experiment NOT_USEFUL and do not develop a dedicated music UX.
P3 conditional research, not part of the next game/OSS release version.

Dominant language
Python
Stars
1
Forks
0
Avg merge
1h 56m
Merged PRs (30d)
7

Getting set up

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/PatchPitch

All issues in drevendev/PatchPitch

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.