Joining the Docbookrx project?

Hi all (and especially Dan!),

I'm interested in becoming one of the committers for the Docbookrx project -- I've already created a number of fixes in the last week, and I expect that to continue in the coming months.

( See https://github.com/opendevise/docbookrx/network )

Any advice? Question? Comments? :)

Thanks,
Marco

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Joining-the-Docbookrx-project-tp4695.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Hi Dan,

Great! Indeed, I absolutely agree with:

* tests for each PR (or commit from a maintainer :) )
* supporting and strictly conforming to the standard.

I do have a quick question about the standard: I assume we're talking about the asciidoctorj spec, not the asciidoc spec?  (There's a little bit of difference between them).

Thanks,
Marco

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Joining-the-Docbookrx-project-tp4695p4700.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

Marco,

I have moved the docbookrx project to the Asciidoctor organization and invited you to be a committer. You can accept the invitation at https://github.com/asciidoctor/

 I do have a quick question about the standard: I assume we're talking about the asciidoctorj spec

 

We are talking about the AsciiDoc that Asciidoctor parses (AsciidoctorJ is just an interface to Asciidoctor), which in my mind is the official AsciiDoc. We consider the AsciiDoc that AsciiDoc Python parses to be legacy AsciiDoc.

Though not an exhaustive list, here a a few of those best practices:

* single-line section titles

* no quotes around values in a block attribute list unless required

* delimiter lines around blocks should be 4 characters long (obviously 2 for open block)

* .adoc for the file extension

* one table cell per line

* block image unless it is on the same line as other text

(I may be forgetting some)

There's a document where we are aggregating these practices, but it's still a work in progress.

http://asciidoctor.org/docs/asciidoc-recommended-practices/

We really want this converter to produce AsciiDoc that doesn't need a lot of fixing. When you make AsciiDoc using pandoc, it needs *a lot* of fixing.

Thanks again for joining the project!

Cheers,

-Dan

On Fri, May 20, 2016 at 5:26 AM, mrietveld [via Asciidoctor :: Discussion] <[hidden email]> wrote:

Hi Dan,

Great! Indeed, I absolutely agree with:

* tests for each PR (or commit from a maintainer :) )
* supporting and strictly conforming to the standard.

I do have a quick question about the standard: I assume we're talking about the asciidoctorj spec, not the asciidoc spec?  (There's a little bit of difference between them).

Thanks,
Marco

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Joining-the-Docbookrx-project-tp4695p4700.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML

--

Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen