"Sponsored" Plugin PRs about governance-and-guidance HOT 11 CLOSED

The plugins were developed under a sponsorship collaboration between CN and Impierce Technologies. Basically we made a deal that made it possible to give back those plugins to the community instead of having them closed source. I should've started this discussion before opening that PR, sorry about that. I feel I should've also used my CN account to push that PR to make it clearer.

I like the idea of moving the scanner plugin to a community maintained workspace repository as it's a more specific use case, though the deep link plugin is definitely vital for Tauri core.

from governance-and-guidance.

I like what they're doing with this contribution, and I think we should figure out how to encourage this without creating a confusing precedent. Plus, the plugins themselves seem very useful and valuable to the community.

Perhaps "sponsored" is the wrong term, since it sounds like we expect to own maintaining them. Sponsorship implies ongoing support to me, this is more like a one time donation. How about acknowledging them as "contributed by," instead?

Maybe instead of or in addition to the note in the README which ends up embedded in the project repo, how about making a blog post highlighting the new functionality and thanking the contributors for their generosity? That way they get a PR boost and recognition without the implication of ongoing support, and the organization doesn't establish a tricky sponsorship backdoor.

from governance-and-guidance.

https://github.com/tauri-apps/plugins-workspace/blob/deep-link/plugins/deep-link/README.md#contributed-by
https://github.com/lucasfernog/plugins-workspace/blob/feat/scanner/plugins/barcode-scanner/README.md#contributed-by

It even looks better tbh :D

from governance-and-guidance.

Thanks @lucasfernog 💜 Are there any details on future expectations for maintenance that could be shared to give a bit more context?

from governance-and-guidance.

The deep link plugin is one of the most requested Tauri features, so I feel it should be maintained by Tauri. As far as I know only this first iteration was sponsored.
As the scanner plugin is more specific, either we move it to a community repository or mark it as feature complete, that's the way I see it. Any other insight @nothingismagick ?

from governance-and-guidance.

Hey @jbolda @wravery @zackarychapple sorry to urge you but there is urgency 😆

Repeating from Lorenzo:

1. Could a non-CrabNebula board member please weight in on if the current state of the PRs linked above would be appropriate to merge into the Tauri codebase.
2. What future conversations (if any) do we need to discuss in order to more properly define this type of arrangement in hopes of similar opportunities coming up in the future?

Especially 1. is a blocker right now, so I would love to hear from at least one person a clear cut:
Can we proceed? / Do we request changes?

from governance-and-guidance.

Thank you @wravery!

@nothingismagick @lucasfernog does that look like a suitable alternative that can be adopted as-is?
Emphasis on the latter, because if we're all happy with that, it seems like the quickest path forward.

(Please ping additional decision makers for me if I'm skipping anyone.)

from governance-and-guidance.

I love this idea, I think it's a good compromise for Tauri and "sponsors".

from governance-and-guidance.

Great idea @wravery 🎉 It feels to be the best compromise to me!

from governance-and-guidance.

Repeating for extra visibility:
tauri-apps/plugins-workspace#536 (comment)
tauri-apps/plugins-workspace#536 (comment)

Replies from https://github.com/JelleMillenaar CEO of Impierce Technologies.

from governance-and-guidance.

I think we've resolved the questions. To summarize:

Have both CrabNebula and Impierce Technologies given the thumbs-up on this?

• CrabNebula, since they're PR authors and from multiple chats.
• Impierce Technologies, in this comment:
  tauri-apps/plugins-workspace#536 (comment)

Was there a discussion in Tauri around how the logos would be placed and formatted?

• Not beforehand, but we have now in this thread.
• And confirmation the placement is non-conditional, so there is room to revisit later.

What would a different company have to do to get the same treatment of getting their plugin adopted by @tauri-apps as an "official" plugin with sponsor callouts and everything?

• The excellent 🚀 suggestion to use "contributed by" I think helps to make this more accessible in the future.
• Though there is room to think about and clarify contributions and sponsorships generally.
  I think that can be for a later discussion though and I think isn't a blocker here.

Who is responsible for future maintenance, etc. of the plugin?

• In principle, Tauri maintains the plugins.
• And explaining whether we should

Could a non-CrabNebula board member please weight in on if the current state of the PRs linked above would be appropriate to merge into the Tauri codebase

• Done! #42 (comment)
  And with modifications could be merged.

What future conversations (if any) do we need to discuss in order to more properly define this type of arrangement in hopes of similar opportunities coming up in the future?

• This remains open. The main topic raised I believe is: "how could another contributor achieve the same"?
• About the suggested possible blogpost: #42 (comment)

The open points I think fit best in an overall sponsorships / contributions discussion.
So with that I'll close this issue as resolved! 💯
Thanks all for your help.

from governance-and-guidance.