Invoice #162975 to Asciidoctor
Asciidoctor Tabs, PDF, and AsciiDoc Language Specification
Paid
Invoice #162975
Submitted by Dan Allen•Approved by Sarah White
Sep 25, 2023
Invoice items
In addition to ongoing support for the Asciidoctor community in the project chat and issue tracker, and applying regular documentation updates, we published several releases of Asciioctor Tabs and Asciidocgtor PDF and continued work on the AsciiDoc Language Specification. In Asciidoctor Tabs, we addressed several issues that were preventing nested tabs from working correctly, fixed support for custom roles on a tab set and custom attributes on an open block enclosure, and upgraded the test suite from Mocha to the built-in test runner in Node.js. In Asciidoctor PDF, we fixed compatibility with Ruby 3.2, removed extra space when index term is used in a heading, added support for fit=none on an image, fixed caption placemement on (un)breakable tables, and fixed image alignment when document has columns. We also continued work on the upcoming Asciidoctor PDF 3 release. On the AsciiDoc Language Specification, we did all the work (but not the release) for the Milestone 0.3.0 build of the Specification, which primarily focused on the following Specification Decision Records (SDRs): SDR-6 define rules for stable backslash escaping, SDR-7 define how document attributes are represented in the ASG, SDR-8 clarify syntax and parsing rules for continuing an attribute entry value across multiple lines, and numerous lesser decisions about parsing rules involving boundaries of blocks. We also submitted the initial draft for several sections to begin work on the specification document. We also refined the ASG schema and helped with the next set of changes for the AsciiDoc TCK. This work occurred in Q3 2023.
$5,000.00 USD
Total amount $5,000.00 USD
Additional Information
Paid to
OpenDevise@opendevise
payout method
Bank account
Details
********By Dan Allen
on Expense created
By Sarah White
on Expense approved
Collective balance
Expense policies
Expense policies
We process expenses twice a week after an admin of the Collective has approved them. We make payments via PayPal and Bank Transfer (using Wise) and can only make payouts to countries served by these payment processors. You are not required to upload an invoice document (the data you submit in the expense form is sufficient), but if you would like to include an uploaded invoice, please make it out to:
Collective Name, Open Source Collective, 440 N. Barranca Avenue #3939, Covina, CA 91723, USA
INFORMATION REQUIRED ON EXPENSES:
Please refer to the documentation here for payment processing requirements on reimbursements and invoices.
REFUNDS:
If you would like a refund, please email [email protected] with the transaction #, the collective you donated to, the date, and the amount of the transaction.
FAQ
How do I get paid from a Collective?
Submit an expense and provide your payment information.
How are expenses approved?
Collective admins are notified when an expense is submitted, and they can approve or reject it.
Is my private data made public?
No. Only the expense amount and description are public. Attachments, payment info, emails and addresses are only visible to you and the admins.
When will I get paid?
Payments are processed by the Collective's Fiscal Host, the organization that hold funds on their behalf. Many Fiscal Hosts pay expenses weekly, but each one is different.
Why do you need my legal name?
The display name is public and the legal name is private, appearing on receipts, invoices, and other official documentation used for tax and accounting purposes.
Collective balance
$17,592.92 USDFiscal Host:
Open Source Collective