-
Currently we use the GitHub v4 GraphQL API to get project metadata. This API requires an authenticated client (authenticated as user, that is). We generally have the necessary tokens for all users who…
-
In addition to a basic smoke test (#106), the CI should also exercise building, simulation, and synthesis.
To avoid the orpsoc-cores repo breaking these tests, a dummy test repo should be created. Ju…
-
---
OS: Fedora 29
---
**Description**
I faced a couple of problems while setting up the development environment using `vagrant up`. Many of them were system dependent which were fixed by simple ma…
-
The various tools can produce a lot of messages about the design. Extract them and report in a useful common format.
-
**Goal:** inform users about events happening on the page, e.g. invitations to new organizations, outstanding requests of any kind, etc.
Don't send out only emails, but also display notifications o…
-
I had to disable the email address confirmation at registration due to spammers registering accounts with email addresses they don't own.
Not sure about a solution, potentially we need a captcha.
-
Despite everyone likes some silence in their Inbox, we probably need some mailing. For example a welcome message, once a project is added, any action related to orgs, etc.
-
The OpenRISC specification requires that the EEAR register be accessible from the supervisor mode but the mor1kx implementation does not have the option to write to EEAR with the mtspr instruction ev…
-
Currently we use the same green for links and headlines, and provide no other indication for links (e.g. underlining). This is confusing, as it makes it unclear when something can be clicked on, and w…
-
Currently `ci-fusesoc-action` uses container based action (https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action) to run `fusesoc` which makes easy to pull in fusesoc …