From b8b3b86cb3a5733479852a05ee69080f41606d97 Mon Sep 17 00:00:00 2001 From: singh1114 Date: Tue, 28 Feb 2017 02:45:42 +0530 Subject: [PATCH] Fixes: Typos --- README.md | 31 ++++++++++++++++--------------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 9528920f..ffc90cd3 100644 --- a/README.md +++ b/README.md @@ -1,28 +1,29 @@ # aboutcode AboutCode is an umbrella project to uncover data ... about software code: - - - where does it come from? - - what is its license? - - is it secure, maintained, well coded? - All these are questions that are important to find answers to when there are million of free and open source software components available on the web. - + + - Where does it come from? + - What is its license? + - Is it secure, maintained, well coded? + +All these are questions that are important to find answers to when there are million of free and open source software components available on the web. + The main homepage lives at http://aboutcode.org -Interest in the Google Summer of Code 2017: AboutCode hass been accepted as a mentoring organization in 2017: https://summerofcode.withgoogle.com/organizations/ -See https://github.com/nexB/aboutcode/wiki/GSOC-2017 for details +Interest in the Google Summer of Code 2017: AboutCode has been accepted as a mentoring organization in 2017: https://summerofcode.withgoogle.com/organizations/ +See https://github.com/nexB/aboutcode/wiki/GSOC-2017 for details. Each AboutCode project has its own repository: -- ScanCode: this the scanner to detect the origin and license of code and its dependencies as a command line tool. https://github.com/nexB/scancode-toolkit . The lead maintainer is @pombredanne +- ScanCode: This is the scanner to detect the origin and license of code and its dependencies as a command line tool. https://github.com/nexB/scancode-toolkit . The lead maintainer is @pombredanne -- AboutCode Manager: this is a GUI-based, desktop application (based on Electron) to review the results of scans and help document conclusions. https://github.com/nexB/aboutcode-manager . The lead maintainer is @jdaguil +- AboutCode Manager: This is a GUI-based, desktop application (based on Electron) to review the results of scans and help document conclusions. https://github.com/nexB/aboutcode-manager . The lead maintainer is @jdaguil -- AtributeCode: this is a command line to document the provenance of code without changing it using a small yaml file. https://github.com/nexB/attributecode/ The lead maintainer @chinyeungli +- AttributeCode: This is a command line tool to document the provenance of code without changing it using a small yaml file. https://github.com/nexB/attributecode/ The lead maintainer @chinyeungli -- License Expression: this is a library to parse, analyze, compare and normalize SPDX and SPDX-like license expressions using a boolean logic expression engine. See https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60 to understand what an expression is. See https://github.com/nexB/license-expression for the code. The underlying boolea engine live at https://github.com/bastikr/boolean.py . Both are co-maintained by @pombredanne +- License Expression: this is a library to parse, analyze, compare and normalize SPDX and SPDX-like license expressions using a boolean logic expression engine. See https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60 to understand what an expression is. See https://github.com/nexB/license-expression for the code. The underlying boolea engine live at https://github.com/bastikr/boolean.py . Both are co-maintained by @pombredanne -- TraceCode-build: this is a tool to analyze the traced execution of a build, so you can learn which files are built into binaries and ultimately deployed in your distributed software. It uses strace https://github.com/strace/strace/ to which we contribute to trace system calls on Linux and reconstruct a build graph from syscalls to find which file is used to build a binary. Maintained by @pombredanne +- TraceCode-build: this is a tool to analyze the traced execution of a build, so you can learn which files are built into binaries and ultimately deployed in your distributed software. It uses strace https://github.com/strace/strace/ to which we contribute to trace system calls on Linux and reconstruct a build graph from syscalls to find which file is used to build a binary. Maintained by @pombredanne -- Conan: stands for "CONtainer ANalysis" and is a tool to analyze the straucture and provenance of software component in Docker images using static analysis. https://github.com/pombredanne/conan Maintained by @pombredanne +- Conan: stands for "CONtainer ANalysis" and is a tool to analyze the structure and provenance of software component in Docker images using static analysis. https://github.com/pombredanne/conan Maintained by @pombredanne -- ABCD: or AboutCode Data is a simple set of convention to define data structures that all the AboutCode tools can understand and use to exachnge data together. The upcoming specification will live in this repository. +- ABCD: or AboutCode Data is a simple set of convention to define data structures that all the AboutCode tools can understand and use to exchange data together. The upcoming specification will live in this repository.