web-view
web-view copied to clipboard
Boscop
An org for web-view
There is a real interest in making sure that web-view continues to get top-shelf support for the near future. Everyone using it should be concerned about its sustainability, and this is the reason why it seems that it could better be managed by an organization.
This topic has been brought up several times already, for example in #64 & #97 - and a number of people have talked about it: @erlend-sh, @zxey, @green-s, @Boscop, @freemasen, @Freaky, @tensor-programming, @lucasfernog and myself (amongst others probably).
At Tauri, we have spent a lot of time crafting a transparent, sustainable and accountable FLOSS organisation with governance instead of dictators and a community-oriented decision making process. Soon, we will also be distributing donations amongst the contributors to core repositories.
To this end, we would like to invite Boscop/web-view to officially become a tauri-org managed repository, where @Boscop and @zxey both maintain owner privileges and where we can all work together in order to ensure a long-lived and healthy environment for web-view.
(Sorry for my long absence, I was very busy..)
Yes, let's turn this into an org project.
What makes more sense, creating a web-view org for this, or transferring ownership to the tauri-apps org? What does everyone think? :)
As I’ve said in the past, I’m in favor of moving it to the Tauri org. They’re very established and are deeply dependent on web-view.
If web-view was to have an org of its own it’d be a single-repo org which is also a tad awkward.
Let’s go with a new org then? That seems to be the option with the smallest amount of friction.
Well, my two cents here is that an org isn't just making a github organization, transferring the repo and its done. I think there needs to be some serious thought put into its creation and management and communication channels. Here is a great resource about creating sustainable communities:
https://sfosc.org
Please see the issue that @zserge linked above. I think that a webview org as an umbrella would be much better than a collection of disparate orgs.
I am torn between finishing porting to Rust (done for GTK - gtk-rust branch, in progress for Windows mshtml-rust branch) and just using this new v1.0.0 webview. What does everyone think? Maybe we could just live under common webview organization even if this repository would be a port and not bindings.
@zxey I personally see nothing wrong with having pure Rust webview in the same org with pure C++ webview next to it, as long as the goals match and the APIs/functionality is kept close (to not confuse the developers).
Fantastic! This seems like the best solution. I think it's good that you would be able to find all the bidings/ports under one organization. We should let others comment on this and @Boscop is the one with final decision and authority over this repo.
At the risk of repeating myself, I love this idea - and here are a couple thoughts about how the org could be structured:
- At the top a "governance" layer, which makes sure that the org is healthy and follows its own rules etc.
- An API working-group where functionality is discussed so that - like @zserge said - developers aren't confused and knowledge / approach can be shared across ports/bindings projects.
- Individual "ports/bindings" with their own internal governance and decision making authority.
- A documentation working group. Seriously. This is really, really important.
@nothingismagick I would love to meet someone from the documentation working group! My new branch even lacks a readme so far. But jokes aside, at the current scale of things it would be nice to at least join the efforts of the existing collaborators, without much of a structure. The structure will probably show itself some time later, if things start to grow.
Well, I think with a little bit of an organizational push at the beginning - with minimal structure, shared vision and openness for growth - a lot of my personal concerns about transparency, accountability and responsibility can be assuaged. I really recommend you check out the https://sfosc.org site for some insights into ways to make projects like this one sustainable.
And one of the things that I've been doing a lot of work on lately is documentation, which feels at times like an uphill battle, but its not one I'll be giving up anytime soon. And considering the fact that much of what we at tauri are doing is built upon the shoulders of other giants, I would be glad to lend a helping hand in the "webview-org docs". :)
Just a little taste of things to come: https://tauri.studio/en/book