precisely zero technical knowledge and couldn't tell the difference between
a good application, a bad application, or a deceptive application.
-These problems only increase as NLNet grants get larger and more
-numerous. Consequently, it's quite a challenge for NLNet to ensure the
-money they've been given responsibility for reaches people who release
-actual free software to improve real-world infrastructure for the
-benefit of EU Citizens (and incidentally the rest of the world).
+These problems only increase as EU grants get larger and more numerous,
+and it's a serious systemic flaw with the whole EU Grant system when
+it comes to heavily-technical projects. Consequently, due to their high
+level of internal expertise and dedication, the EU is extremely happy that
+NLNet takes direct responsibility for ensuring that the money they've
+been given reaches people who release actual free software people to
+improve real-world infrastructure for the benefit of EU Citizens (and
+incidentally the rest of the world).
I had a brief chat with the person from the EU Commission. He was
-delighted to be able to see the sheer number of people involved and being
-sponsored by NLNet. I had an opportunity to ask him about the anti-trust
-aspects of the RISC-V Foundation's ongoing intransigent behaviour.
-He initially expressed puzzlement and some concern, because the EU is
-funding quite a lot of RISC-V projects, and none of them had any issues.
-I asked him a very simple question: "how many of those projects are
-simply *implementing* existing RISC-V Standards?," and he replied, "all
-of them." I then asked, "how many of those projects are *innovating*,
+delighted to be able to see the sheer number of people involved and
+being sponsored by NLNet. I had an opportunity to express some of my
+concerns about NLNet's relationship with the RISC-V Foundation. He
+initially expressed puzzlement, because the EU is funding quite a lot
+of RISC-V projects, and none of them had any issues. I asked him a
+very simple question: "how many of those projects are simply
+*implementing* existing RISC-V Standards?," and he replied, "all of
+them." I then asked, "how many of those projects are *innovating*,
developing alternative extensions to what is dictated by the RISC-V
-Foundation?" With the answer being "none," *that* was the point at which
-he understood the extent of the problem, and (with the systematic failure
-to respond to in-good-faith requests to participate in innovation),
-how the RISC-V Foundation - and its members, by way of them having
-"voting power" and thus having direct influence over how the RISC-V Foundation
-is run - are at risk of violating EU anti-trust legislation, particularly
-given that NLNet's funds for our project come *directly from an EU Horizon
-2020 Grant*.
+Foundation?" With the answer being "none," *that* was the point at
+which he understood the extent of the problem. I'll publish a more
+comprehensive update on this topic soon.
### Meeting Other LibreSOC People
members -- if you'd like to help, check out the [How can I
help?](http://libre-riscv.org/) section of the website.
-We now hoave four new people who are contributing: Cole, Veera, Yehowshua,
+We now have four new people who are contributing: Cole, Veera, Yehowshua,
and Michael. Veera is a sysadmin and I would be delighted to get some
help managing the server. In particular I would like to install `public-inbox`
but it requires `exim4` and `mailman` to be converted to `Maildir`. This is
-the kind of thing that would be great to hand over to another sysadmin.
+the kind of thing that would be great to hand over to
+[another sysadmin](http://bugs.libre-riscv.org/show_bug.cgi?id=181).
Cole just loves the idea of what we're doing and wants to learn, so
what I've asked him to do is simply to follow instructions and
projects / crowdsupply.git / blobdiff