Outdated documentation

This page is out of date. Please use the main navigation to find the latest documentation.

Freedom Verification Team home

Note

A detailed explanation about how to proceed with KFV work can be found here

Starting

Before starting to check the kernel you have to download it and follow the instruction to unpack it. After that, you can choose one of the 'orphan package' listed at the main kfv page. For this purpose edit the wiki page putting your username in the 'Owner' column for the choosed package. If all sections are already adopted you can take subsections from one of any unfinished sections. In this case the best way to avoid double checking is mailing both the section's owner and the mailing list).

At this stage you have to read any file located in your adopted sections and check if software freedom is in line with the license; this step includes verifying the license (if you have a doubt about the various licences, this page is very useful), check for binary blobs, undocumented hex table, obfuscated code and any stuff like that which de-facto denies customizations.

When you have finished your check you can write a report page in your wiki's package subsection; if you got an issue with some files you must notify the mailing list and, if confirmed, raise a bug in the bug's page.

Some scripts have been developed to make package file formatting easier: pitof made a Bash script; crap0101 wrote a Python script to create tables and another to upload wiki pages; finally bt made this interactive program to check files, create tables and upload it within Emacs.
Note: if you don't use any of the above programs to generate the wiki page, please be sure to follow the KFV structure and formatting rules.

If you have any doubts or need clarifications regarding the KFV process, feel free to contact the gNewSense community using IRC or the users mailing list.


CategoryOutdated

Kernel/KfvBriefIntroduction (last edited 2013-08-25 19:19:25 by FelipeLopez)