| Yes, I am aware of the repository. > Have you already asked them to add a reference to Bromite somewhere in the about screen? I have not; I was expecting it, given the amount of modifications from Bromite patches (which is zero, as far as I understood). > I think /e/ is different from MS or Google in that it's possible to swap out most of the integrations with your own servers (it's all a bunch of glued-together open source services, after all). It's that "most" that corrupts the intent. > Without cloud integration, I doubt /e/ would reach any sort of mainstream or non-technical cult status at all. Sorry, I will avoid discussing this, it has all the clues to become an endless and inconclusive talk :) In short: yes, I agree with you, and still do not care about "mainstream or non-technical cult status" at all. |
I won't lie, I would have expected the same if I were in your shoes. Thinking positively though, it's possible that the /e/ people don't care much about the attribution they themselves receive and don't realize what it means to others to be recognized for their personal hard work. Asking nicely might show them that other people in the open source community do care. The worst that can happen is that the people behind the project do indeed not care about you and are rude about it, but in that case nothing really changes anyway. Things can only improve from here, I'd say!
Based on the changes I've seen, they basically replaced all instances of "Bromite" and "Chrome" in the source code with "Browser". I don't see much /e/-specific code in there at all, aside from a project description and some links in the documentation. They did add a reference to the original project to the AUTHORS file, so I'd like to believe in a variation of Hanlon's razor: Never attribute to malice that which is adequately explained by laziness.
> Sorry, I will avoid discussing this, it has all the clues to become an endless and inconclusive talk :) I completely agree :)