NGI Zero Review

• Accessibility best practices and tooling for self-tests
• WCAG audit of project results

Inclusive design makes it possible for everyone to use technology. Many more people than you might assume suffer from small but blocking issues in using technology. These hamper their careers, education and — and often unnecessarily so. Small adjustments can make a world of difference, but how do you know which adjustments are needed so that color-blind people can use your app, people with a tremor can fill out a form or people with limited cognitive abilities can figure out what to do.

• Help build a more diverse developer community
• Receive wider input, more representative of the global and heterogeneous internet
• Gender Evaluation Methodoloy (GEM)

The internet is for everyone, not just for the lucky few. What do you know about global needs and constraints, and about best practises for open source projects to improve diversity? How to structure a project to avoid negative interactions within your community such as rudeness, name-calling and stereotyping? How to embed the perspective of the global South, where people do not all have the latest smartphone or 5G connectivity. We can help connect the projects to non-obvious communities, so you can directly interact with them.

• Best practices community building
• Strategic advice on developing project sustainability

The mentor organisations can help projects consider the phase after their grant runs out: setting up crowd funding, applying for additional grants, starting a company or building an ecosystem of partners that are interested in sustaining the project. The mentoring organisation have experience with each of these scenario's, and can assist with practical tips and contacts.

New projects are filled with energy and ambition, but sometimes you need some outside wisdom and experience. We offer support from two different mentor organisations, each with a strong reputation in building FOSS communities and versed in their structure, ethics, and values. Mentors offer a listening ear when you need it, and help make connections to other relevant efforts inside and outside of NGI. They offer practical lessons learned from rich experience with many other projects, and can help to solve communication problems and startup challenges. They help understand and cultivate the NGI Vision inside the projects, and act as bees cross-polinating new developments and best practices. Everything needed to make sure the project can target what it set out to accomplish.

• Best practices copyrights and license compliance
• Assist with tooling and creation of SPDX headers
• Legal strategy on emerging copyright issue

A lot of software starts off with existing source code, as there is plenty of that available on the internet — and it is not always clear whether there is a proper open source license attached. For developers under time pressure, eager to get results and functionality out the door sooner rather than later — and not everyone is aware of legal considerations when doing so. Copyright compliance management isn't glamorous work, but can save a lot of trouble later on. Using best current practices like Reuse.Software one can avoid the pitfalls of compliance.

• Best practices on localisation and internationalisation (i18n)
• Support with setting up translation infrastructure

Software may seem universal, but can actually be quite specific to linguistic and cultural influences. While many in the tech scene assume that everybody understands fluent English, lack of support for other languages can be a significant barrier to broad adoption. Even within Europe, in some countries 80% of the population has problems with understanding technical English. Moreover, for many users, their mother tongue represents more than the technicalities of language. Not only that, but the cultural dimensions of technology are different across cultures (in varying degrees of subtlety), and these differences are actually very meaningful to people. Europe is a continent of linguistic and cultural diversity, a continent of regions and of variety. So how can you design your technology in such a way that users from anywhere in the world feel at home and productive with it?

• Best practices on packaging and reproducible builds
• Reproducible packaging with Nix

It is important for a project that is meant to scale to gather traction as early as possible. There should be a convenient and easy to obtain development and testing environment, to ensure people that are interested have a low barrier of entry. We support the team to set up their technical infrastructure with Nix. Nix is a powerful vendor-agnostic package solution for Linux, Mac OS X and other Unix systems that makes package management reliable and reproducible. It provides atomic upgrades and rollbacks, side-by-side installation of multiple versions of a package, multi-user package management and easy setup of build environments. By using the unique capabilities of Nix, and associated projects like NixOps and NixOS, complex dependencies (such as services) can be managed. This way the project is able to have a cross-distro development and delivery system that is easy to integrate with continuous integration, and allows anyone to easily check in to the development process of the projects. It also creates full transparency: the entire setup is declarative and allows for reproducible builds, so every source origin and every patch is completely verifiable.

• Best practices on security
• Security audit

Every project needs to earn the trust of users over time, and long term trust depends on the trustworthiness of your output. Young and ambitious projects tend to overestimate their level of sophistication and understanding in terms of security. This can bring users into potentially dangerous situations.

Living up to high security standards is important, and so we offer a professional security audit. The results are sent confidentially to the team, and can be made public through a standard coordinated disclosure procedure.

• Best practices on standardisation
• Custom advice on standardisation strategy

Open standards are an essential component of the openness of the internet. Dealing with standards setting organisations as a relative outsider can be a good lesson in humility though. Standards bodies often have meritocratic characteristics, and processes with very specific timing, meaning that newcomers can be at a disadvantage. There are historical precedents and unwritten rules to be taken into account. The actual decision making turns out to be more complex and time-consuming than it seemed at first instance. And sometimes there is a clash of interests (the privacy or security feature you want may ruin someone's nefarious but working business model), which can be very frustrating. Long battles have been fought over insignificant issues as well as over fundamental chasms, and it is unfortunately not a given that the debate is always won by the right party or in a fair way.

Not every project may need to interface with a standards setting organisation, but for those that do we provide guidance and mentoring throughout the process, and can help introduce projects to relevant stakeholders to collaborate and build alliances. This does not deliver guarantees on successfully reaching a standard, but it can significantly increase their chances.

• Assessment of testing situation
• Advice and help on setting up and improving testing
• Usability testing

If software is not tested, users are likely to be dissappointed by the software and adoption will be low. The developer of the code will have a limited perspective on the usability of the code. A fresh outside perspective can highlight new issues with the code.

Projects can apply for help with testing. The testing setup of your project will be reviewed and advice can be given on how to improve or extend it.