woofmeow/straywild
woofmeow/straywild
3
5
Fork 2
Code Issues 40 Projects 1 Releases 43 Packages Wiki Activity Actions

Close project to unsolicited contributions

Browse source
This commit is contained in:
Alexander Sellite 2026-08-21 16:39:44 -04:00
parent f45550e46b
commit ba35db1015
4 changed files with 66 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

51
CONTRIBUTING.md
View file

@ -1,29 +1,32 @@
# Contributing
# Contribution policy
NETfishing is currently developed through focused changes on the repository's
active development branch. Coordinate scope with the project owner before
starting substantial work.
NETfishing is an owner-directed Woofmeow project and is not accepting
unsolicited contributions. Please do not submit pull requests, patches, code,
artwork, models, audio, writing, documentation, translations, designs, or
other implementation work. Pull requests are disabled for the official
repositories.
By intentionally submitting material for inclusion, contributors agree to the
applicable grants and representations in
[`CONTRIBUTOR-TERMS.md`](CONTRIBUTOR-TERMS.md). Maintainers must preserve an
affirmative record of that agreement. Contact the owners before submitting if
separate written terms are needed.
Issues remain available for reproducible bug reports and player feedback. An
Issue is not a request for contributed implementation, and attaching or
linking unsolicited work does not make it an accepted Project contribution.
The owners may occasionally invite specific work in writing before it is
created or submitted. [`CONTRIBUTOR-TERMS.md`](CONTRIBUTOR-TERMS.md) is retained
to document previously accepted contributions and govern expressly invited
work; it is not a standing invitation to contribute.
## Contribution forks
The [NETfishing Asset License](ASSET-LICENSE.md) permits a public source-control
fork to retain NETfishing assets when the fork is maintained in good faith to
prepare, test, review, or submit changes for possible inclusion in the official
project. Keep the hosting platform's fork relationship visible, preserve all
license and attribution notices, and do not publish general-audience builds or
use the fork as an independent game or distribution.
The [NETfishing Asset License](ASSET-LICENSE.md) contains limited permissions
for qualifying Contribution Forks. Those permissions do not promise review or
acceptance and do not override the policy above. Keep the hosting platform's
fork relationship visible, preserve all license and attribution notices, and
do not publish general-audience builds or use the fork as an independent game
or distribution.
Private test builds and temporary access-controlled test servers may be shared
with people directly participating in development or review of the proposed
contribution. Submission remains subject to `CONTRIBUTOR-TERMS.md`; permission
to maintain a Contribution Fork does not guarantee that its changes will be
accepted.
only as allowed by that license. Permission to maintain a Contribution Fork
does not authorize unsolicited submission or obligate the owners to review it.
## Change discipline
@ -36,13 +39,15 @@ accepted.
- Keep presentation-only systems out of save files and network messages.
- Store runtime assets under repository-owned paths; never reference a
workstation sync or temporary directory.
- Record the source and license of newly imported assets in
[`docs/ATTRIBUTION.md`](docs/ATTRIBUTION.md).
- Retain source, permission, and license evidence for newly imported assets.
Update [`docs/ATTRIBUTION.md`](docs/ATTRIBUTION.md) when the accepted work
adds or changes a distributed credit or third-party notice; do not add a
file-by-file inventory of ordinary project-owned assets.
- Do not assume the GPL code license applies to project assets; observe
[`ASSET-LICENSE.md`](ASSET-LICENSE.md) and third-party terms.
- Do not commit `.godot/`, test data, logs, captures, or build outputs.
## Before requesting review
## Before committing a maintainer change
```sh
git diff --check
@ -63,7 +68,7 @@ tests are supporting evidence, not a replacement.
- Do not mix generated build artifacts with source changes.
- Do not rewrite published release tags.
- Describe behavior, compatibility impact, validation, and asset provenance in
the review or release record.
the internal review or release record.
## Style