public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: Damien Clochard <daamien-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Adding a `pandoc/extra` docker image
Date: Wed, 21 Dec 2022 20:03:16 +0100	[thread overview]
Message-ID: <87cz8b8xda.fsf@zeitkraut.de> (raw)
In-Reply-To: <63cc4f3e-e425-4db4-9179-cc94ca441f7bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Hi Damien!

"daa...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <daamien-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> My name's Damien Clochard and I'm here to talk about the pandoc
> docker images. I hope this is the right channel.

Thank you for reaching out, this is absolutely the right channel.
I'm one of three current pandoc Docker maintainers and also the one to
blame for most of the current code used to generate the images.

> I work for a French PostgreSQL company named 'DALIBO' where we
> produce **a lot** of documents with pandoc, and I'm the maintainer of
> the `dalibo/pandocker` image here:
>
> https://github.com/dalibo/pandocker

I'm a fan of those pandocker images (and contributed a small patch in
the past <https://github.com/dalibo/pandocker/pull/228>)

> [...]
>
> Would you like to add a new official docker image named `extra` built
> upon the `latex` image that would include useful filters and
> templates ?

That would be great! If you are ok with a little more responsibility,
I'd be happy to see you become a maintainer at the pandoc/dockerfiles
repository. That would make it easy for you to shape everything to your
needs.

Heads-up: The current build system works well, but is still in dire need
of a redesign. The attempt to reduce duplication backfired, and now we
have a lot of accidental complexity. I'll try to fix this and would be
happy to get help or input from an experienced maintainer.

Cheers,
Albert


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2022-12-21 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 15:21 daa...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
     [not found] ` <63cc4f3e-e425-4db4-9179-cc94ca441f7bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-21 19:03   ` Albert Krewinkel [this message]
     [not found]     ` <87cz8b8xda.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-01-24  6:44       ` daa...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

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=87cz8b8xda.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=daamien-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).