Request: Submit to the official community plugin list

[tobloef]

What: Submit this plugin to the official community plugin list.

Why: Easier installation. Sync across devices with Obsidian Sync. Better discoverability of the plugin.

How: See this guide. Seems like we're two-thirds of the way there already. It could technically be done by anyone, but I thought it would be more appropriate if it was done by the author.

[modality]

I appreciate this. I have submitted plugins before so I am familiar with the process.

The main issue is that I don't own the art used in this plugin. The author of the original Text Mapper commented in this PR about the license on the Gnomeyland icons:

The original Text Mapper uses the AGPL, not CC BY SA 4.0. Only the Gnomeyland icons use CC BY SA 4.0.

Since the Gnomeyland icons use CC BY SA, all images generated with them are subject to these terms:

Attribution — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.

If I'm going to actively publicize this plugin, I don't want to release my code under CC BY SA 4.0. Instead, I want to give the plugin away and allow for unlimited reuse of its art without attribution to me. I don't want non-technical, well-meaning Obsidian users who stumble this plugin to run afoul of this ShareAlike license. If they were going to use the plugin to generate a hex map for their zine or whatever, they should be able to sell the zine without having to navigate licensing issues for the maps. I think it is my responsibility not to lay a trap for people.

I have thought about commissioning art -- that takes money and precious time. If you have followed this repo for any length of time you may have noticed that updates come in short bursts and very much after the fact. I appreciate the interest, and the endorsement.

[daren-thomas]

What if the Icons were an optional setting that's disabled by default and a big box explaining how the use of these icons includes certain responsibilites? By separating out the code for the icons, it would be easier to include a separate set of icons with a license that's easier to handle. And also allow people who want to publish their hex maps to add in their own icons and style.

Actually, looking at the source (main.ts), it seems the gnomeyland and apocalypse code is in "text mapper" language and just appended to the user's code as a sort of static pasted-in-library. A little work might move those to optional settings.

Would you welcome some help with this? Is it even something you'd want?

[maxZ-2020]

Since I needed include to work, I added this PR: #25

This would allow users to download the include files into their vault and the example would just find it. Building upon that a published version of the plugin could just have a very minimal custom library for default and a hint in the example that you should drop a real library into your vault.