I have no experience with this type of thing and am just thinking out loud so please forgive me if this idea is insulting to even consider. I know the plugin developer’s time is also valuable and they deserve control over the potential benefits of their creations.
I am just looking to see what people’s reaction to this hypothetical is. Basically, is there any chance it wouldn’t be an undue distraction for something like this to happen where a plugin creator might be willing to continue to create plugin as third party but hand over complete control over current version so that it can be core and therefore more useful and widespread, supporting Obsidian and the community.
I know it is likely the distraction that @Klaas mentioned 99% of the time, but maybe there are special cases that wouldn’t require the plugins be really up-kept, and they aren’t overly complicated. Like, I guess if the creator of a plugin that served a much sought after need was willing to just hand their work over no strings attached and the developers, with the creator’s input if they wanted, could over time more quickly approve and maybe implement as part of the core. There definitely would likely be no promises made by the developers since this would be completely voluntary on the plugin creator’s part. And, it wouldn’t be updated and could risk being broken as Obsidian changes and consequently removed from the core. As I type all of this, I know how bad it sounds, but still am optimistic.
I think, possibly even with all the what ifs and sacrifices, as Obsidian grows, the potential for this scenario to give the plugin a much larger chance to be a hit and necessity in the platform may make it worth it. And also, potentially more importantly, the third party version can still grow with new additional features and a more widespread user base as the original version gains popularity. At that point it may be at the community’s request or in the interest of the developers to work with the plugin developer to make that plugin really work in the changing core and likely benefit this person in some way. At the very least they would be heavily lauded and hopefully rewarded by the community at the very least which basically brings me back to the current setup.
Sorry for the ramble. I just didn’t want to discount this idea so quickly because I definitely can relate to users who may feel very conflicted about making a plugin a too big part of their workflow.