Relationship with helium-chromium?

[tifandotme]

https://github.com/imputnet/helium-chromium is a clone of this repo.

I am confused. What is the relationship between these two?

[dumbmoron]

It's a fork of ungoogled-chromium, I don't see what is exactly confusing about it.

[wukko]

we constantly contribute to ungoogled chromium, and this is a global template that’s visible on all of our repos. we also mention all sources and link back to original repos, and follow all licenses. i personally don’t think there’s anything wrong with making a fork of open source software while also contributing back to upstream

[PF4Public]

and follow all licenses

Are you allowed to re-license BSD into GPL? The BSD license you replaced had this clause:

1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.

IANAL, but this is something you should not be able to do, at least no so easily.

[dumbmoron]

Are you allowed to re-license BSD into GPL? The BSD license you replaced had this clause:

we don't re-license any ungoogled-chromium code, as mentioned in the README:

Any content imported from other projects retains its original license (for
example, any original unmodified code imported from ungoogled-chromium remains
licensed under their BSD 3-Clause license).

the GPL license only applies to patches and code that are specific to helium and don't really belong anywhere else -- otherwise we would have contributed them here.

[networkException]

Let me just chime in to say that I'm quite happy with the work that has landed here so far and that I hope that this can be a healthy relationship that benefits both projects

[PF4Public]

@dumbmoron Perhaps I wasn't made myself clear enough. That commit in particular makes the impression of the code being re-licensed, because there is no clear separation of GPL and BSD code. And as I mentioned you were supposed to preserve the whole license text, linking to a file at specific commit is not sufficient.

To be clear, I have no issues with that. I was just triggered by the statement we […] follow all licenses, sorry. You do not.