linkchecker/doc/development.mdwn

144 lines
4.9 KiB
Text
Raw Normal View History

2011-04-15 06:28:21 +00:00
Developing LinkChecker
======================
The following steps describe how to compile LinkChecker from source
on various platforms.
Requirements
------------
2011-04-25 13:44:20 +00:00
On Mac OS X systems, using MacPorts, Fink or homebrew for software
installation is recommended.
2011-04-15 06:28:21 +00:00
2012-06-22 21:58:20 +00:00
- Install Python >= 2.7.2 from http://www.python.org/
2011-04-15 06:28:21 +00:00
- *On Windows only*, install the Windows SDK
http://msdn.microsoft.com/de-de/windows/bb980924
2011-04-15 06:28:21 +00:00
2011-04-25 13:44:20 +00:00
- *On Windows only*, download and install the Microsoft
Visual C++ 2008 runtime from
http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en
2011-04-15 06:28:21 +00:00
2011-04-25 13:44:20 +00:00
- *Optional, used for Virus checking:*
ClamAv for Unix from http://www.clamav.net/lang/en/download/
or for Windows from http://www.sosdg.org/clamav-win32/
2011-04-15 06:28:21 +00:00
2011-04-25 13:44:20 +00:00
- *Optional, for displaying country codes:*
Pygeoip from http://code.google.com/p/pygeoip/
2011-04-15 06:28:21 +00:00
Setup for Unix/Linux
--------------------
Execute ``make localbuild`` to compile a local version and execute
2016-01-23 12:28:15 +00:00
``./linkchecker``.
2011-04-15 06:28:21 +00:00
Execute ``make test`` to run the unittest suite.
Execute ``make dist`` to build a distributable source package.
Setup for Mac OS X
------------------
Execute ``make localbuild`` to compile a local version and execute
2016-01-23 12:28:15 +00:00
``./linkchecker``.
2011-04-15 06:28:21 +00:00
Execute ``make test`` to run the unittest suite.
2011-04-25 13:44:20 +00:00
Execute ``make app`` to build a distributable source package.
2011-04-15 06:28:21 +00:00
Setup for Windows
-----------------
2011-04-25 13:44:20 +00:00
Execute ``windows\build.bat`` to build a local version.
Execute ``windows\test.bat`` to run the unittest suite.
Execute ``windows\dist.bat`` to build a binary installer.
2017-01-31 17:25:57 +00:00
Release process
---------------
1. make sure tests pass
2. bump AppVersion in setup.py and commit changes
3. build wheel file (setup.py bdist_wheel) and upload to PyPI
4. tag release (vX.Y.Z)
5. push
6. write release notes on github
2017-02-09 22:52:44 +00:00
Contributor's guide
===================
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment
include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at [http://contributor-covenant.org/version/1/4][version]
[homepage]: http://contributor-covenant.org
[version]: http://contributor-covenant.org/version/1/4/