[ About | Licence | Contacts ]
Written by Oleksandr Gavenko (AKA gavenkoa), compiled on 2018-02-10 from rev 9e6ad6607a9e.

Development project files.

Additional reading.

Essential project files.

This files can have suffixes to represent formating syntax:

and optionally compressed - .gz.

README file.

Assumed that users first read this file before start using project.

ABOUT/OVERVIEW/SUMMARY file.

ABOUT-NLS file.

NOTES/NOTICE file.

FEATURES file.

MIRRORS/WHERE file.

PLATFORMS file.

AUTHORS/MAINTAINERS file.

AUTHOR  AUTHORS  MAINTAINERS

CONTRIBUTORS/THANKS/CREDITS file.

CONTRIBUTORS THANKS CREDITS ACKNOWLEDGEMENTS

DEDICATION file.

FEEDBACK file.

FORK file.

COMMANDS file.

PROGLIST file.

UPGRADE/UPGRADING/CONVERSION file.

SERVICE/SUPPORT file.

INSTALL/BUILD file.

CUSTOMIZE file.

License files.

Apache file.

Apache-1.0
Apache-1.1
Apache-2.0

PHP file.

PHP-3.0

MIT file.

MIT  LICENSE_MIT

BSD file.

BSD  LICENSE_BSD

GPL file.

GPL-2    GPL2
GPL-2.0
GPL-3.0  GPL3
LICENSE-GPL

LGPL file.

LGPL-2   LGPL-2.0  LGPL-2.1  LGPL-3.0  LICENSE_LGPL
COPYING.LESSER

Developer files.

HACKING/DEVELOPERS/PORTING file.

  • Notes for developers.

CONTENTS file.

  • Description which file for which comes.

CONTRIBUTE file.

  • Guidelines to contribute to the project.
CONTRIB
CONTRIBS
CONTRIBUTE
Contributing
HOW-TO-CONTRIBUTE

DEBUG/DEBUGGING file.

  • How debug sources, useful macros/function/tips.

TESTS/CHECK_NOTES file.

  • How run/add tests, requirements to run.
  • How and when test passed by which platform/configuration.

BINDINGS file.

  • Known bindings of library to different langs/frameworks.

Coding style files.

C++STYLE
CodeStyle

CODING file.

  • project policy and recommendation on coding

Project changes files.

Here goes news and descriptions of user visible changes:

ChangeLog file.

  • Changes made to program source files.
  • Explains how earlier versions were different from the current version.
  • Each directory can have its own change log.
  • Useful for RCS/CVS. Don't needed with modern VCS (SVN, Git, Mercurial, Bazaar).
changelog  Changelog  ChangeLog
CHANGELOG
ChangeLog-1996-1999   ChangeLog-2000
ChangeLogOld

COMPAT/COMPLIANCE file.

  • Compatibility with previous versions.

NEWS/OLDNEWS/ONEWS file.

  • User-visible changes.
  • In each new release, add items to the front of the file and identify the version they pertain to.
  • Don't discard old items.
  • NEWS file gets very long, move some of the older items into a file named ONEWS and put a note at the end referring the user to that file.

CHANGES/WHATSNEW file.

Changes  CHANGES  CHANGES-release
RELEASE_NOTES  ReleaseNotes  RELEASENOTES  RELEASE-NOTES
RELNOTES
SHORTLOG
WHATSNEW

Todo files.

Similar:

BACKLOG
CHECKLIST
TODO
PROJECTS

PROGRESS file.

Version info files.

VERSION file.

  • Package version.
  • Package name (optional).
  • Release naming schema and version number semantics (optional).
  • Release names and version relations (like starts, toys, animals, etc, optional).

ANNOUNCE file.

ANNOUNCE
ANNOUNCEMENT
  • Only current release changes and notes. No history. Same text was sent to mail lists as announce.

HISTORY file.

FUTURE file.

Documentation files.

Refcard files.

cheatsheet
refcard

FAQ files.

  • List of frequency asked questions with answers.

PROBLEMS/KNOWNBUG/WARNINGS file.

PROBLEMS
KNOWNBUG  KNOWN_BUGS  KNOWN-BUGS
WARNINGS

Bug report instructions.

BUGFORM
REPORTING-BUGS
BUG-REPORTING
BUG-REPORTS
BUGS

BINDINGS file.

Reference.

/usr/share/doc/common-licenses/*
From Cygwin 'base-files' package, list of licence files.

Unknown files.

AUDIT
DETAILS
FILE-FORMAT
Fixes
FIXES
FORMAT
MAIL
NEEDED
PGPKEYS
PKG-INFO - http://www.python.org/dev/peps/pep-0241/ http://www.python.org/dev/peps/pep-0314/
PLACES
ROADMAP
TRACING

Reference.