Look at mpark/wg21 on GitHub.
It's not the only way to format documents, but it helps. A paper has a particular structure you should follow, but since yours is not a proposal, you can skip the proposed wording.
Once your paper is "in shape" I'll upload it to the tracker. I'll get you a paper number later today.
Yes, thank you, that would be great. What is the process for publishing in a mailing?
Do you need help publishing this in a mailing?
I've implemented std::error, meeting the requirements laid out in [P1028], and based on this experience, have written up a paper outlining various design decisions and concerns that came up during the implementation, particularly with regard to how std::error might map to existing error mechanisms (dynamic exceptions, std::error_code).
This is not a formal proposal right now. It is intended simply to further discussion around the design, requirements and implementation details of some future std::error specification.
Std-Proposals mailing list