Florian Gilcher

icon indicating a website link https://ferrous-systems.com icon indicating an email [email protected]

icon company Ferrous Systems icon location Berlin icon location Managing Director @ferrous-systems. Heavily invested @rust-lang functional safety. Organiser @eurucamp/@jrubyconf/@rustfest/@oxidizeconf.

Results 89 comments of Florian Gilcher

RISC-V implementation contains likely GPL-3 code

Is this the only instance of this happening in RISC-V? @dvc94ch, can you confirm that this is the only instance of copied/ported gcc code?

RISC-V implementation contains likely GPL-3 code

Note: The copyright holder of this code is Embecosm.

Optimized implementations for supported architectures

Note, this has since moved to https://github.com/ARM-software/optimized-routines, and the license marks it as MIT. Given that the licensing here is currently in a sorry state, this must be clearly marked...

develop and mail out rustc licensing guidelines

@pnkfelix it is indeed coming out of a number of issues where we had practical and theoretical licensing problems.

Renaming the default branch

Feature was added, branch by branch: https://github.com/github/renaming#rename-existing

Clarify the Rust compiler's licensing status

I'd like to disown this. I would really like to work on this and it is an important topic, but my bandwidth is lacking. Above that, this blocks Josh and...

URL without www loads page, but has a CORS error for the data.

Similarly, navigating to the http site (http://rustaceans.org/findwork) will lead you somewhere else entirely. This breaks loading by bare domain. (rustaceans.org/findwork)

Set all connection detail info in the URL

That should be "before the port number and after the :", for example: https://kiwiirc.com/client/irc.mozilla.org:+6667/#novemb.rs,#rust-community Still, configuration through the widget editor would be great.

Feature request: Index filter and ignoring .-indices by default

Regexp would be fine by me and having the `.` excluded by default would go a long way. I'll see if I can take a stab at it myself as...

Tracking Issue for strict_provenance

I want to share a couple of observations and views on this discussion: 1) I think it's inappropriate to dismiss features like CHERI as "niche" for the sake of a...