Omni_Source

This is amazing, thank you so much for developing this!

Sounds good, so it basically has to be powered by community development at this point?

Looping in @88250 and @Vanessa for these questions about SiYuan

@88250 Thanks for your input!

I just think it'll definitely up the note taking experiences with SiYuan (Since Obsidian doesn't have the block based editing like SiYuan does) and it will be less friction for Obsidian power users like me to fully transition to SiYuan

Also another thing is the Vim mode (that Obsidian supports) and down the road a Vim editor for coding etc.

Not sure if I'm using SiYuan right but, I see it with lots of potential in the coding space down the road (developers managing code snippets and project files)

@WanChen - Thank you WanChen! Will check it out

Sounds good D,

Is there a detailed documentation/guide anywhere for developing plugins from A to Z in SiYuan?

I'll definitely look into it 😄

@88250 - On this database feature feature (which I assume it's first going to look like Notion/Appflowy), is there any plans to integrate open-source AirTable alternatives (APITable, Grist, NocoDB) as part of the database feature so that the databases can be like Excel 2.0 on steriods

Most of the open-source AirTable alternatives are AGPL-3.0 license though, not sure if that'll have any impacts if SiYuan decides to integrate it

Sounds good, thank you for the input!!

Sounds good thank you for confirming D!!

@88250 - Hi D, thank you very much for putting all of this together. I just have a few questions below regarding the plugin development

1. Regarding licensing:
   Does SiYuan require all plugins to be licensed under MIT, or are other open source licenses (such as Apache License 2.0 or APL 3.0) also acceptable as long as it's open source?
2. About monetization:
   What is SiYuan's policy for plugin monetization? For example, if a plugin generates revenue, do you take any commission or require a revenue share?
3. Concerning derivative work:
   If we develop a plugin by building upon other open source repositories licensed under, for instance, APL 3.0 (Ex. NocoDb, https://github.com/nocodb/nocodb), does that mean our plugin must be relicensed under the same license, or is there a requirement for a different licensing structure to abide with SiYuan's requirement?