xmpp/design d---------
design: add entity caps proposal

See #171 (https://mellium.im/issue/171)

Signed-off-by: Sam Whited <sam@samwhited.com>
design: add title to MAM proposal

Signed-off-by: Sam Whited <sam@samwhited.com>
design: update service discovery proposal

The previous plan to include a registry was a rather naive
implementation that would have required that the multiplexer and the
registry both have features registered against them, resulting in a lot
of boilerplate and potential for advertising features that don't exist
or failing to advertise features that do exist because we forgot one or
the other registration.

A new plan was created that uses the multiplexer as the registery so
that handlers regstered against the mux that also advertise features
can automatically respond to disco info requests.
The new plan has the added benefit of working with nested multiplexers
without further modification.

Signed-off-by: Sam Whited <sam@samwhited.com>
design: answer question in MAM design doc

The difference between after and after-id is the value of count (if
set), so no changes need to be made and this question can be removed and
counted as answered.

Signed-off-by: Sam Whited <sam@samwhited.com>
design: add MAM design doc

Fixes #110

Signed-off-by: Sam Whited <sam@samwhited.com>
design: fix typo in design doc template

Signed-off-by: Sam Whited <sam@samwhited.com>
xmpp: update docs to point to new chat room

Signed-off-by: Sam Whited <sam@samwhited.com>
design: update proposal 42

Update the integration testing proposal to mention that the new API is
not covered by the compatibility promise since it's in the internal/

Signed-off-by: Sam Whited <sam@samwhited.com>
design: add service discovery proposal

Signed-off-by: Sam Whited <sam@samwhited.com>
design: remove status from design docs

We don't want to have to create a new commit when the status changes.
It's much easier to track this on the issue with a label or tag.
Since the issue is linked in the design doc anyways it's still pretty
easy to find out the status.

Signed-off-by: Sam Whited <sam@samwhited.com>
design: create a formal proposal process

As I design more packages and features, I often find it helps to write
down what I think the solutions will be before actually implementing
them. Formalizing this process for others will give me a place to point
people if I have to ask them to write a design document.

Fixes #44

Signed-off-by: Sam Whited <sam@samwhited.com>
design: adds a design doc for integration testing

See #42

Signed-off-by: Sam Whited <sam@samwhited.com>
design: update stanza mux

Update the mux proposal to solve the last remaining questions, and
clarify that the token stream will always contain the entire stanzas
stream, including the original start element.

Signed-off-by: Sam Whited <sam@samwhited.com>
design: add an open question to stanza mux
design: add new stanzamux design proposal

The previous iqmux design was incomplete, and ended up being cumbersome
in practice. This proposal aims to solve those issues.
design: accept iqmux proposal
design: fix whitespace in markdown docs

Previously there was no line break between the status and discussion
design: rename documents based on issue number

Also add a link to the issue in the docs to make going back and forth
between the document and the discussion simpler.
design: answer a question in iqmux proposal

Update the IQ mux proposal to make it clear that Error and Result type
IQs are also handled by the multiplexer, and add some shortcut functions
for handling them in a reasonable way.
design: rename iqmux proposal

Previously the file had a .txt extension but it is a markdown file.
Changing to a .md extension will allow renderers to show formatting