Commit 3691cb97 by Alex Shure

minor editing

parent 4a01a7de
Pipeline #14 failed with stage
in 0 seconds
......@@ -3,21 +3,21 @@ layout: post
title: Booting up the Open Integrity Index
---
If you've been following the Open Integrity, you will have noticed that after [our initial efforts in 2013](https://wiki.openintegrity.org/doku.php?id=workplan), the project has been on hold. During this first phase, we developed the foundations for [our criteria](https://wiki.openintegrity.org/doku.php?id=criteria_subcriteria_claim) and setup [a beta platform](https://openintegrity.org/v1) but it took us a few years to interest funders to develop the next step of the project with us.
If you've been following the Open Integrity, you will have noticed that after [our initial efforts in 2013](https://wiki.openintegrity.org/doku.php?id=workplan), the project has been on hold. During this first phase, we developed the foundations for [our criteria](https://wiki.openintegrity.org/doku.php?id=criteria_subcriteria_claim) and setup [a beta platform](https://openintegrity.org/v1). We now advance with new funders to develop the next step of the project with us.
<!--more-->
In this initial phase we have set the tone of the initiative.
In this phase we set the tone of the initiative.
- **We care about the impact of technology on all users** and particularly those who depend on it to enjoy their fundamental rights.
- **We take a holistic approach to understanding the impact of technology** which includes the technical features tools make available, but also their usability and the governance and policies of the tool makers.
- **We believe that security by transparency** is the way to go, yet we know that there are also best practices to follow with closed source software that make a difference for users.
**Open Integrity Initiative** has also assembled a list of a hundred possible metrics related to various aspects of software development, including governance, systems, architecture, build and user experience. In this [new phase](../../about#funding) we will shift our focus towards the **gathering of measurement and claims** and the **development of a knowledge framework** about the adoption of best practices that support the security and privacy of software.
**Open Integrity Initiative** has assembled a list of a hundred possible metrics related to various aspects of software development, including governance, systems, architecture, build and user experience. In this [new phase](../../about#funding) we will shift our focus towards the **gathering of measurement and claims** and the **development of a knowledge framework** about the adoption of best practices that support the security and privacy of software.
Data about the adoption of security and privacy best practices are often difficult to find and rarely easy for users to understand. How can the adoption of these practices be measured, and what is the most useful structure for such a broad range of measurements? How can we answer **reliably and consistently** questions such as:
- Which tools are **open-source**?
- Which tools provide **end-to-end encryption**, implement **forward secrecy** or support **two-factor authentication**?
- Which have security features that are **usable without prior expertise or training**?
- Which can be **downloaded securely and verified** to be authentic?
Data about the adoption of security and privacy best practices are often difficult to find and rarely easy for users to understand. How can the adoption of these practices be measured, and what is the most useful structure for such a broad range of measurements? How can we answer **reliably and consistently** questions such as:
- Which tools are **open-source**?
- Which tools provide **end-to-end encryption**, implement **forward secrecy** or support **two-factor authentication**?
- Which have security features that are **usable without prior expertise or training**?
- Which can be **downloaded securely and verified** to be authentic?
This is what we're setting out to answer. In the next 6 months we'll focus on [developing partnership](../../partners#measurement) in order to **develop metrics and collect data** that will be available for an audience of professionals (software engineers, trainers, advocacy organisations) and will help provide answers about best practices adoption.
This is what we're setting out to answer. In the next 6 months we'll focus on [developing partnerships](../../partners#measurement) in order to **define metrics and collect data** that will be available for an audience of professionals (software engineers, trainers, advocacy organizations) and will help provide answers about best practices adoption.
......@@ -6,12 +6,12 @@ footer: recent_blogs
##### The Open Integrity Initiative is [booting up](blog/booting-up).
We aim to provide **reliable, consistent and evidence based** answers to questions such as:
- Which tools are open-source?
- Which provide end-to-end encryption?
- Which implement forward secrecy
- Which support two-factor authentication?
- Which can be downloaded securely and verified to be authentic?
The platform aims to provide **reliable and evidence based** answers to questions such as:
- Which tools are open source?
- Which provide end-to-end encryption?
- Which implement forward secrecy?
- Which support two factor authentication?
- Which can be downloaded securely and verified to be authentic?
You can read more [about the project](about).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment