Future directions

[OliverBalfour]

Basic plan: @OliverBalfour and @simonmaris will do some short-term cleanup

• Update the build system and docs if necessary
• Include fixes from forks and PR's
• Fix the most critical bugs
• Push out a new release

We're still figuring out:

• Where will this repo go long term? Hopefully we transfer it to the obsidian-community GitHub org (as long as the community-plugins.json is updated too)
• Who will maintain the repo long term? We're thinking a small group sharing responsibility

[OliverBalfour]

• Patches I've just added:
  • Relative image path support (not yet sure if this is a full fix, but it doesn't break anything)
  • Release CI workflow
    • Dev instructions are in development.md
  • Use ESBuild instead of Rollup
• Patches worth reviewing:
  • https://github.com/obsidian-community/obsidian-pandoc/compare/master...PeteMichaud:obsidian-pandoc:master?expand=1 (adds a mode to increment filenames instead of overwriting them)
  • https://github.com/OliverBalfour/obsidian-pandoc/compare/master...phillipjohnston:obsidian-pandoc:master?expand=1 (fixes admonitions and some types of embeds)
  • https://github.com/OliverBalfour/obsidian-pandoc/compare/master...ryuzee:obsidian-pandoc:master?expand=1 (relative path resolution for output file and CLI args - I think there's a more general way to do this?)
  • frogkind@4a751c9 (fixes SVG export with non-ASCII characters)
  • Alternative relative image path fixes:
    • https://github.com/dirkroorda/obsidian-pandoc/commit/b053a7c45939760bd74819a382632537275ff441
    • JDMcE@4eb7e64
  • https://github.com/OliverBalfour/obsidian-pandoc/compare/master...BumbrT:obsidian-html-export:master?expand=1 (big refactor, something to do with div's and an export all feature? unsure if we want to merge, but maybe there's useful edits here to cherry pick)
• Also see Embed syntax with block references doesn't work #23 (comment)

[evolve2k]

I can see the issues are stacking up and also that this is a really valuable and critical obsidian plugin.

Are you open to adding more maintainers?
Maybe we could add a new issue called something like "Call for Maintainers" with a few questions to help people introduce themselves and establish their credibility and then give it a week or two, and add a few folk in that have a bunch of likes?

Just an idea. Would be good to have more maintainers on this project.