Fallout-build / Fallout-build/Fallout

Pitch Fallout to the German tech press

Open
#605 0 comments 0 reactions 0 assignees View on GitHub
enhancement target/backlog
Dominant language
C#
Stars
154
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
15

Description

### Problem

Fallout has no press coverage. Both large German IT outlets accept outside contributions, and both have covered .NET build tooling before. heise Developer ran a news item when Cake joined the .NET Foundation, so build automation is on their beat.

### Outcome

At least one pitch is sent to a German outlet, and the result is recorded here either way.

### Acceptance criteria

- [ ] A topic proposal is sent to at least one outlet.
- [ ] The reply, including a rejection, is recorded on the relevant sub-issue.

### Constraints

- Both outlets publish in German. Chris writes the copy.
- heise Developer accepts **exclusive contributions only**. If the same piece is pitched to another outlet, that must be disclosed in the cover letter. So heise and Golem cannot receive the same article at the same time without saying so.
- Do not frame any pitch as NUKE being abandoned. Verified on 2026-07-30: NUKE released 10.1.0 on 2025-12-02, has had no commits since, has 122 open issues, and is not archived. That is stalled, not dead. The repository is public and the claim is checkable.
- Repo rule: never write an `@` before the former maintainer's handle, anywhere, including article drafts and pitch emails. Credit NUKE's origin by name or a plain profile link, matching how `README.md` already does it.

### Notes

Drafts of the pitch email and the article outline are held outside this repository on purpose. This repo is public, and a pitch is weaker if an editor can find it.

Contributor guide

Open the contributing guide

Research direction

Review README.md to match the project's existing crediting style and verify the current NUKE status before preparing a German topic proposal. Send it to at least one eligible outlet, respecting heise Developer's exclusivity constraint, and record the reply—including a rejection—on the relevant sub-issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
content
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.