Collaboration for Bromite development

[romain-hunault]

@uazo I reach you via a GitHub issue, as I was not able to find any email address.

I'm Romain Hunault, working at Murena to develop /e/OS (https://e.foundation/). Bromite is our default web browser, and we would like to discuss with you the possibility to combine our efforts on this topic. Feel free to reach me on Telegram (@rhunault) or by mail (romain.hunault@murena.com) to discuss the possibilities. Thank you in advance!

[uazo]

ciao romain,

I was not able to find any email address.

is correct, no email and no social, you can find me here.

I am glad, really, i would like to deal with other developers working on chromium.

let me understand what you mean by your efforts, I don't know e.foundation and I don't remember any feedback from you about carl's work (or mine) during the life of bromite.
because there are many things to be done and I would like to understand what possibilities you are talking about.

[romain-hunault]

@uazo thank you for the answer. As a big picture, we would like to help to maintain Bromite up-to-date on a regular basis. The help could be provided by dedicating some development bandwidth, sharing some build servers, support the project... there are many possibilities. It would be easier for me to discuss that in a call, in order to understand what is your vision of the project, and find the best way to work together.

[uazo]

It would be easier for me to discuss that in a call

no thanks, I prefer to use this tool

in order to understand what is your vision of the project

my vision, don't you have a simpler question :) ?

although I've been collaborating for years, I don't think I have a lot of experience on opensource projects, but I have to tell you I'm a little disappointed, I expected more collaboration between the various actors.
So, if you will, this is my vision: to write good patches that can be useful, for anyone who needs them, maybe discussing goals since carl said that (maybe :) I have a distorted view of what privacy is.

omg, if I really have to venture a goal, well, then my vision is that the future of this project can only be decided when it reaches a maturity where it can flow into something else bigger, today, however, it is science fiction utopia.

instead, please go ahead, I'm all ears. what is your goal?

and find the best way to work together.

I'd say let's get to know each other.
there are many issues still open, choose one or make a new proposal, if you want I can show you what my priorities are after I finish uazo/bromite-buildtools#193 that I am working on now.

[uazo]

@romain-hunault help me on this question: why should a user trust this browser?

[romain-hunault]

@uazo our goal is to offer a user-friendly web browser, respecting users privacy. It should offer the best compatibility with web technologies. It should receive regular (security) updates.

Regarding trust, our position is that an open source project is the best way to get it from users.

[romain-hunault]

@uazo let me introduce you @TheScarastic and @althafvly, the 2 Murena team members working on our Browser (based on Bromite). We will align how we can help this project to receive regular updates.

[uazo]

I was having a look at your repo and was wondering if the reason for removing the webgl patch, Block-gateway-attacks-via-websockets and navigation connectioinfo was due to some bug of mine or simply because it was incompatible with apps using webview.

Also, I was wondering if you put these patches in because you detected some issue that we missed

• https://gitlab.e.foundation/e/os/browser/-/blob/master/build/patches/0022-disable-seed-based-field-trials.patch
• https://gitlab.e.foundation/e/os/browser/-/blob/master/build/patches/0023-disable-fetching-variations.patch

thanks in advance for the response!

[romain-hunault]

@uazo Please find below the reasons:

• webgl patch: it was breaking some applications relying on WebGL, such as Windy (issue)
• Block-gateway-attacks-via-websockets: it was done a long ago, at a stage we were not linking properly merge requests and issues, but I feel it was because of unexpected behavior on some applications (issue)
• navigation connectioinfo: I'm not sure which one you are speaking about, maybe this merge request (issue)?
• 0022-disable-seed-based-field-trials.patch: imported from GrapheneOS, to avoid some pings on Google servers (Vanadium System WebView tries to access clientservices.googleapis.com in the background GrapheneOS/Vanadium#89)
• 0023-disable-fetching-variations.patch: imported from GrapheneOS, to avoid some pings on Google servers (Vanadium System WebView tries to access clientservices.googleapis.com in the background GrapheneOS/Vanadium#89)

[uazo]

thank you very much, I thought they were related to the webview.
unfortunately you will find that it will probably be impossible for you to build it in this version, at least I have never tried.
And most importantly, I would not be able to actively test it.

navigation connectioinfo

I mean https://gitlab.e.foundation/e/os/browser/-/blob/master/build/patches/0033-Revert-Remove-navigator.connection-info.patch

[mbestavros]

@uazo @romain-hunault Are there any updates on this potential collaboration? I think it would be awesome for multiple developers to be involved with/maintaining Cromite, especially those coming from what seems to be a large and well-respected OS project like /e/.

I do see that /e/ Browser does seem to be based on Cromite, which is awesome. What is the process for reviewing/pulling in new patches? Is there potential to extend that review process upstream to the Cromite project?

[uazo]

My fault, little time, especially in the last quarter of the year, because of my job, will be like this until the end of the year.

@romain-hunault I am always interested, sorry for not getting back to you.

[romain-hunault]

@mbestavros

Are there any updates on this potential collaboration?

Sadly not.

What is the process for reviewing/pulling in new patches?

For now, we use the patches from Bromite that have been updated by Cromite project. We add our own set of patches on top of this.

Is there potential to extend that review process upstream to the Cromite project?

We do not plan to publish upstream our modifications, as they are about branding or default settings we want to apply. Also, we need to build the Webview, which is not a priority for Cromite.

I am always interested, sorry for not getting back to you.

@uazo no issue! You know how to reach me (Telegram or email), when you will have more time to dedicate to the project.

[basilgello]

#600 helping with server infra is one thing /e/ could consider @romain-hunault

[uazo]

@basilgello thank you for your concern, but it's my fault.
I am lazy and did not contact them privately as they had already requested.

[quyleanh]

Sorry for off-topic.
I just wow since I saw the TheScarastic name for a long time, a real talent in Android development. Still remember the day when mido is the first device received fully bootable and functions when the new Android released.

Btw, I'm looking forward to see more collaboration between you guys. Thank you very much for such amazing work.

[mbestavros]

I'm going to once again poke this thread for an update.

@uazo, if you haven't already, I would strongly encourage you to reach out to @romain-hunault and discuss how the /e/ OS project can help out, and soon. Doing so could confer tons of benefits for both the project and you:

• More people actively contributing would mean more bandwidth to make improvements, including those not directly related to the functionality of the browser - such as documentation.
• It would also mean less burden on you, as a sole maintainer, reducing the risk of burnout.
• More people involved gives greater confidence to potential users of the browser that it will stick around longer-term.

It's important for the health of Cromite as a project for multiple developers to be familiar with the codebase and release process, and you have a perfect opportunity for that right here. Frankly, you're squandering it by not engaging.

I hope to see that change. For the sake of the project and the incredible work you've done, @uazo. I think I speak for every Cromite user when I say we don't want a repeat of what happened with Bromite.

If it helps, I've gone ahead and created a Matrix/Element channel for informal project discussion: https://matrix.to/#/#cromite:matrix.org

[uazo]

Frankly, you're squandering it by not engaging.

first, I ask those who read and those who will read this thread to stop forcing their hand.
for those who don't remember (or don't understand?), this project is a hobby and therefore has the dedicated time for a hobby activity.

Second, don't ask me to turn this project into something more serious as if it were a business. Being a technical coordinator for a mid-level company, I know what a serious commitment needed in terms of investment of time and money means.
I am quite reluctant to list what my desires might be, precisely because I know what means the investment I would require, and, my greatest fear, is that they might not lead to concrete results, which is not exactly what I want.

I think I speak for every Cromite user when I say we don't want a repeat of what happened with Bromite.

this has nothing to do with working with /e/OS or CalyxOS or anyone else.
the goal I set for myself is not to make sure that what happened to bromite does not happen again, but rather to create a new model to apply to cromite. which one, is all to be understood. I don't have a clear idea and that's why I haven't said anything yet.

Doing so could confer tons of benefits for both the project and you:

issues to make are there, and to date there are 135, and they are there, anyone can read them and decide how and to what extent to contribute, if they want to, I will never force anyone.
For now, I am just starting a possible collaboration from the individual issues of each issue: if it then becomes a broader collaboration, we will see.
Personally, I can't wait for it to happen.

[mbestavros]

@uazo Fair points. I want to be clear - I think you do amazing work, and I'm grateful for you volunteering your time to make Cromite happen. My frustration came from a place of care about the project, and I apologize if it came off as antagonistic. That wasn't my intention, if you can believe that.

the goal I set for myself is not to make sure that what happened to bromite does not happen again, but rather to create a new model to apply to cromite.

I'm very happy to hear this is a goal! I do think the best way to safeguard against a Bromite situation is to have multiple maintainers involved, but as you say Cromite is your project and I'll trust your judgment on how to get there.