59 lines
2.1 KiB
Markdown
59 lines
2.1 KiB
Markdown
# A Promise
|
|
## Description
|
|
|
|
In the distant future where corporations rule most of Earth and space, Talon is
|
|
a software developer at Eastern Hills Space Company, one of the leading space
|
|
travel and defense corporations in the world. Eilidh is a runner, someone who
|
|
actively causes mayhem for corporate interests. After being blessed by a
|
|
goddess, Talon finds himself in a new role, learning magic and protecting
|
|
corporate secrets. Eilidh finds herself being forced into a role alongside
|
|
Talon. Romance blossoms. Secrets are revealed. Promises are made.
|
|
|
|
---
|
|
|
|
This is the LaTeX formatted source-code for _A Promise_, a trans-lesbian story
|
|
set in the space-faring future of 2157. With Magic. Because fuck you why not?
|
|
|
|
_A Promise_ pulls very loose inspiration from _Ryn of Avonside_ and _Digital
|
|
Galaxies_ both by the fantastic transbian fiction author QuietValerie.
|
|
|
|
## Documentation
|
|
|
|
The universe documentation, among other various tidbits can be found over at
|
|
the [promise wiki](https://man.sr.ht/~spicywolf/promise).
|
|
|
|
## Author
|
|
|
|
- Kararou Ren
|
|
- [github](https://github.com/karaiwulf)
|
|
- [sourcehut](https://sr.ht/~spicywolf)
|
|
- [blog](https://lesbianunix.dev/)
|
|
- [scribblehub](https://www.scribblehub.com/profile/61134/karaiwulf/)
|
|
|
|
## License
|
|
|
|
This work is licensed under the CreativeCommons Attribution NonCommercial
|
|
ShareAlike International License version 4. You can read the full licensing
|
|
terms by reading the contents of LICENSE located at the root of this
|
|
repository.
|
|
|
|
## Contributing
|
|
|
|
If you wish to modify and contribute, you must follow the style guide, found
|
|
below. From there, issue a pull request with your changes. All PRs will be
|
|
reviewed by the current editor(s) and the author(s).
|
|
|
|
Modifications to the build system are expected to have been tested, but will be
|
|
tested again.
|
|
|
|
### Git Arch
|
|
|
|
We are now leveraging the fact that we have a git server. Development and
|
|
editing will be done on the same branch, one for each new chapter.
|
|
|
|
canon should only contain ready to ship chapters.
|
|
|
|
Edits in clones of the repo can be done however, and pull requests must be to
|
|
canon.
|
|
|