microML

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

This is exactly the way we plan to proceed. There is no interim version at the moment since this is a brand new project.

Repository on GitHub, which uses git. git is distributed.

This is exactly the way we plan to proceed. There is no version numbering at the moment since this is a brand new project.

This is exactly the way we plan to proceed. We use GitHub for that purpose.

This is exactly the way we plan to proceed. There are no release notes at the moment since this is a brand new project.

No publicly vulnerabilities are known at the moment since this is a quite young project.

We do have a process to submit bug reports. It is documented in https://github.com/microML/microML/blob/main/CONTRIBUTING.md

We use the GitHub issue tracker.

This is how we plan to proceed. There are no bug reports for now because the repository is new.

This is how we plan to proceed. We will always do our best to submit the majority of enhancement requests made by the community. We want to make sure that we follow the insights/suggestions of the whole community.

https://github.com/microML/microML

For details, please see https://github.com/microML/microML/blob/main/SUPPORT.md and https://github.com/microML/microML/blob/main/SECURITY.md

We plan to be an open and transparent community. There are no info treated in this project which might be private since this is library about mathematics and machine learning.

This is how we plan to proceed. We don't have any vulnerability report yet because the repository is new.

Non-trivial build file in repository: https://github.com/microML/microML/blob/main/Makefile.

Non-trivial build file in repository: https://github.com/microML/microML/blob/main/Makefile.

The project utilizes only "gcc" and "avr-gcc" to be compiled. Both are FLOSS tools. No external dependencies are planed.

Please, find the documentation at https://github.com/microML/microML/blob/main/README.md and https://github.com/microML/microML/blob/main/CONTRIBUTING.md

We provide a Makefile for that purpose.

We plan to proceed in this way but there are no branches at the moment in the repository.

We use GitHub entirely for that purpose.

We provide information about the general policy in the files "CONTRIBUTING", "README" and "CODE_OF_CONDUCT". The main guiding principle is that a test suite must be in place so that the main branch of the repository is never compromised.

We do not have a complete test policy since the project is too young for that. Obviously, once the project becomes bigger there will be a test policy.

The warning flags are included in the Makefile of the project.

We are a team of people who have experience in scientific and industrial software. Some of us are definitely qualified to design secure software. Some of us also have past experience with developing open/free software.

We are a team of people who have experience in scientific and industrial software. Please, see the previous comment.

We plan to use GitHub for that purpose.

This is exactly how we plan to proceed.

The repository does not and never will contain any information of that type.

We cannot apply such tools since the software produced in this library is intended for microcontrollers only.

Please, see previous comment.

Please, see previous comment. In any case, we plan to fix every vulnerability found as soon as possible.

The code needs to be thoroughly analized at every commit since this code has to run on microcontrollers. No code that is not tested on actual hardware will be committed.

Please, comments above. This is a library for microcontrollers.

We plan to do this for sure but with different tools since this is a library for microcontrollers.