Joining the Docbookrx project?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Joining the Docbookrx project?

mrietveld
Hi all (and especially Dan!),

I'm interested in becoming one of the maintainers 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
Reply | Threaded
Open this post in threaded view
|

Re: Joining the Docbookrx project?

mojavelinux
Administrator
Marco,

Super duper! I'd love to have your support as a committer on the project. Thanks for stepping forward!

I really want to see DocBookRx move ahead. Lately, I've been having a tough time finding time to review pull requests, as you've probably noticed. I find I do much better when I work with a team. The flurry of activity on the Atom packages for AsciiDoc have proved that theory.

I have two straightforward requirements for DocBookRx, of which I'm sure you'll endorse.

* Each change should have one or more tests that can verify it
* We should generate clean, consistent AsciiDoc, following the recommendations in the Asciidoctor User Manual

I'll get you setup when I'm back online tomorrow afternoon.

Thanks again for stepping forward, Marco!

Cheers,

-Dan

On Fri, May 20, 2016 at 3:25 AM, mrietveld [via Asciidoctor :: Discussion] <[hidden email]> wrote:
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



--
Dan Allen | @mojavelinux | http://google.com/profiles/dan.j.allen
Reply | Threaded
Open this post in threaded view
|

Re: Joining the Docbookrx project?

mrietveld
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
Reply | Threaded
Open this post in threaded view
|

Re: Joining the Docbookrx project?

mojavelinux
Administrator
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.


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
Reply | Threaded
Open this post in threaded view
|

Re: Joining the Docbookrx project?

mojavelinux
Administrator
In reply to this post by mrietveld
Oh, and of course, the modern AsciiDoc mentioned in the migration guide:


-Dan

On Sun, May 22, 2016 at 4:29 PM, Dan Allen <[hidden email]> wrote:
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.


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



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