public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Contributing
Date: Fri, 9 Dec 2022 15:24:12 -0800	[thread overview]
Message-ID: <56C1D138-581C-4B54-95B5-24AE18D441AD@gmail.com> (raw)
In-Reply-To: <CAMXDC9Ky3CfOCpy=SbCsaDzZyk=DcMCx51wNp+oML-9pOcrrYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Great! In this case, I think commenting on the GitHub issue might make more sense, since we’d have the context of the previous discussion.

And yes, you can put “fixes #whatever” in your commit message.


> On Dec 9, 2022, at 12:57 PM, Erik Rask <lifeunleaded-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hello,
> I'd like to start contributing more. Based on the Readme, a discussion here first is recommended. The DocBook issues are perhaps my best place to start. In chronological order, that starts me at issue 1402 as far as I can tell.
> 
> I would say that is best solved by adding role="unnumbered" to the section. Section labelling (i.e. numbering) is controlled by the XSLT stylesheets in DocBook, so not numbering an individual section (rather than stop at a certain depth) would be implemented in a stylesheet customization. But marking the relevant sections would at least allow a custom stylesheet to match precisely.
> 
> If I recall correctly from the PR for this, that would just require putting ("role","unnumbered") in Header.Attr.attributes and it would come out as the role attribute in DocBook.
> 
> Protocol questions for the maintainers: 
> 	• Would this comment have been better on the GitHub issue?
> 	• Do you want issue references GitHub-style in commits to issues (e.g. "fixes #1234") from contributors, or do you prefer handling them separately?
> Take care.
> 
> -- 
> Hurrying will get you nowhere faster.
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CAMXDC9Ky3CfOCpy%3DSbCsaDzZyk%3DDcMCx51wNp%2BoML-9pOcrrYw%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/56C1D138-581C-4B54-95B5-24AE18D441AD%40gmail.com.


      parent reply	other threads:[~2022-12-09 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 20:57 Contributing Erik Rask
     [not found] ` <CAMXDC9Ky3CfOCpy=SbCsaDzZyk=DcMCx51wNp+oML-9pOcrrYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-12-09 23:24   ` John MacFarlane [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C1D138-581C-4B54-95B5-24AE18D441AD@gmail.com \
    --to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).