f9e38f3

.tickets/README.md modified (view file)

@@ -1,20 +1,13 @@-Pinchord's tickets!+Pinchord's tickets -All of these need worked on, if you're looking for somewhere to contribute :D+All of these need worked on, if you're looking for somewhere to contribute :p  If something isn't here, don't hesitate to suggest it to me!  ## Tickets -Important things that need done before release:+See release.md for things that need done before release -- mods-dict.md-- chord-format.md-- contractions.md-- plover-plugin.md-- emit-all-misstrokes.md-- fix-brief-affixes.md--Things to figure out:+Other things to figure out:  - space-naked-finals.md

.tickets/chord-format.md modified (view file)

@@ -1,5 +1,22 @@ A standard format for Pinchord chords. +## Symptoms++There are currently two main implementations of Pinchord being maintained alongside each other.+This is not only much more work to maintain for me, but also forces Pinchord derivations to choose+between two bad choices: support their derivation for a single platform (plover or javelin), or+maintain them both, which, from experience, slows down development more than it should.++Really, there is no way to mod Pinchord without choosing one (or maintaining two) format.++## Why++- There is no single format that can be used to mod Pinchord+- Pinchord sits on 2 hosts - Plover and Javelin, which are two very different engines+- Pinchord wants the lowest barrier to adoption possible, and choosing only one host reduces the number of people that can use Pinchord+- Not all keyboard firmwares can be modified to run Pinchord, and not everyone wants to mess with their firmware, many would rather just install an app.+  The opposite is true for other people, who would rather have the system run on their keyboard without the hassle of needing to run an app.+ Goals: 1. Allow you to trivially mod Pinchord 2. Work across both Plover and Javelin

.tickets/release.md added (view file)

@@ -0,0 +1,18 @@+Checklist for releasing Pinchord.++Release means that a version is stable and you can continue to use it forever without issue.++It doesn't mean that nothing can change after that, though of course a lot more care should be taken to changing things.++Generally, after release, it will be intended that people stick with the version they learn even if a new one comes out.+They can switch if they'd like to, but it probably wouldn't be worth the effort.++Checklist:+- [ ] chord-format.md+- [ ] mods-dict.md++From README.md:+- contractions.md+- plover-plugin.md+- emit-all-misstrokes.md+- fix-brief-affixes.md