You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the nfc-tools wiki has pages for each project, containing various information about obtaining, building, using and debugging the software. Some of these instructions are also present in the project repository (e.g. build instructions) and the duplicated information trend to be inaccurate (nfc-tools/libnfc#294).
Because GitHub's README.md is an ubiquitous primary source of information for most hackers (those I know at least), it makes sense to have the build instructions of each project in it's README.md file, and removed them from other places.
The nfc-tools website page for each project can become an "advertising" page highlighting key features of the project and linking to the GitHub repository.
Pages about "advanced" hacking (e.g. with patches, that is pages which contain code that can be broken in the future with the evolution of the tools) need to be timestamped and can therefore be moved in some kind of blog.
Finally, general information can be linked from each project's README.md regarding:
Debugging
Reporting bugs
Support
Any though are welcome !
The text was updated successfully, but these errors were encountered:
Currently, the nfc-tools wiki has pages for each project, containing various information about obtaining, building, using and debugging the software. Some of these instructions are also present in the project repository (e.g. build instructions) and the duplicated information trend to be inaccurate (nfc-tools/libnfc#294).
Because GitHub's
README.md
is an ubiquitous primary source of information for most hackers (those I know at least), it makes sense to have the build instructions of each project in it'sREADME.md
file, and removed them from other places.The nfc-tools website page for each project can become an "advertising" page highlighting key features of the project and linking to the GitHub repository.
Pages about "advanced" hacking (e.g. with patches, that is pages which contain code that can be broken in the future with the evolution of the tools) need to be timestamped and can therefore be moved in some kind of blog.
Finally, general information can be linked from each project's
README.md
regarding:Any though are welcome !
The text was updated successfully, but these errors were encountered: