|
| 1 | +# Support cpp-linter with a T-shirt |
| 2 | + |
| 3 | +cpp-linter is **not** opening a general T-shirt store right now. |
| 4 | + |
| 5 | +Instead, we want one shared project fund so support goes to the project as a whole, not to only one maintainer. That makes it much easier to cover printing, shipping, and the occasional T-shirt thank-you gift fairly. |
| 6 | + |
| 7 | +## Why a shared fund comes first |
| 8 | + |
| 9 | +If supporters donate to individual maintainers separately, it creates an awkward problem: one person may receive the money while someone else is expected to handle the shirt, inventory, or shipping. |
| 10 | + |
| 11 | +Our preferred model is: |
| 12 | + |
| 13 | +1. Support goes into one public project account. |
| 14 | +2. The core maintainers manage it together. |
| 15 | +3. Shirt fulfillment is offered manually when budget, stock, and shipping make sense. |
| 16 | + |
| 17 | +This keeps expectations clear and avoids turning project support into private side payments. |
| 18 | + |
| 19 | +## Shared funding path |
| 20 | + |
| 21 | +!!! tip "Preferred setup" |
| 22 | + Support cpp-linter through our shared Open Collective account: [opencollective.com/cpp-linter](https://opencollective.com/cpp-linter) |
| 23 | + |
| 24 | +[Support cpp-linter on Open Collective](https://opencollective.com/cpp-linter){ .md-button .md-button--primary } |
| 25 | + |
| 26 | +Why Open Collective: |
| 27 | + |
| 28 | +- It gives the project a shared public account instead of sending funds to only one person. |
| 29 | +- It makes incoming funds and project expenses easier to track transparently. |
| 30 | +- It gives the maintainers a cleaner way to share responsibility for project spending. |
| 31 | + |
| 32 | +We may still add GitHub Sponsors later, but this Open Collective page is now the **canonical shared destination** for project support. |
| 33 | + |
| 34 | +## What supporters should expect |
| 35 | + |
| 36 | +!!! important "No active checkout yet" |
| 37 | + There is no public order form or direct purchase flow at the moment. |
| 38 | + |
| 39 | +If you want to support cpp-linter, the intended model is: |
| 40 | + |
| 41 | +- Donate through [Open Collective](https://opencollective.com/cpp-linter). |
| 42 | +- If we are offering shirts at that time, we will confirm availability manually. |
| 43 | +- A shirt is a **thank-you perk**, not an automatic purchase entitlement. |
| 44 | + |
| 45 | +That means fulfillment may depend on: |
| 46 | + |
| 47 | +- available stock |
| 48 | +- shipping destination |
| 49 | +- sizing availability |
| 50 | +- current project budget |
| 51 | + |
| 52 | +## T-shirt policy |
| 53 | + |
| 54 | +We still like the idea of project shirts, but only in a lightweight and sustainable way. |
| 55 | + |
| 56 | +Our working policy is: |
| 57 | + |
| 58 | +1. The shirt is meant to thank notable supporters of the project. |
| 59 | +2. We will confirm each shipment manually before collecting size and address details. |
| 60 | +3. We will avoid promising fulfillment unless the shared fund can cover it. |
| 61 | +4. Limited quantity, international shipping, and cost changes may affect availability. |
| 62 | + |
| 63 | +## If you want one |
| 64 | + |
| 65 | +The shared fund is live, and the best starting point is: |
| 66 | + |
| 67 | +- [Open Collective for cpp-linter](https://opencollective.com/cpp-linter) |
| 68 | + |
| 69 | +If you specifically want to express interest in a shirt, the best follow-up channels are: |
| 70 | + |
| 71 | +- [GitHub Discussions](https://github.com/cpp-linter/cpp-linter/discussions) |
| 72 | +- [Issues in this site repository](https://github.com/cpp-linter/cpp-linter.github.io/issues) |
| 73 | + |
| 74 | +If enough people are interested, we can publish a clearer supporter policy around shirt availability and supporter tiers. |
| 75 | + |
| 76 | +## Next steps |
| 77 | + |
| 78 | +The remaining rollout is: |
| 79 | + |
| 80 | +1. Add this same support link to the main repository. |
| 81 | +2. Publish the maintainer policy for how project funds are used. |
| 82 | +3. Define when a supporter may be offered a shirt. |
| 83 | +4. Add GitHub Sponsors later only if it still points people back to the shared funding model. |
| 84 | + |
| 85 | +Thanks for supporting cpp-linter and helping us keep the project fair for everyone involved. |
0 commit comments