By Joey Hess, LinuxWorld.com
[[template id=note text="""
-First published on [LinuxWorld.com](http:://www.linuxworld.com/), a
-publication of Network World Inc., 118 Turnpike Rd., Southboro, MA 01772.
+[First published](http://www.linuxworld.com/news/2007/040607-integrated-issue-tracking-ikiwiki.html)
+on [LinuxWorld.com](http:://www.linuxworld.com/), a publication of Network
+World Inc., 118 Turnpike Rd., Southboro, MA 01772.
"""]]
Wikis are not just for encyclopedias and websites anymore. You can use
because of concurrent edits to the same part of a
page, regular commit conflict markers are shown in
the file to let you resolve the conflict, as you
-would for conflicting edit in source code.
+would for conflicting edits in source code.
Ikiwiki is a full-featured wiki that you can use
for a variety of purposes, from traditional wikis
into revision control as part of the software project,
and tie it into the build system using the Makefile.
-Ikiwiki can also be tied into the `post-commit` hook of your revision
+Ikiwiki can also be tied into the [[post-commit]] hook of your revision
control system, so that whenever a developer commits a change to a wiki
page in revision control, the project's web site is automatically updated.
The [[ikiwiki_tutorial|setup]] explains in
grouping, tags are better for categorizing issues
as bugs, wishlist items, security issues, patches,
or whatever other categories are useful. Bugs can
-be tagged "moreinfo", "done" "unreproducible",
-or "moreinfo", etc, to document different stages of
+be tagged "moreinfo", "done", "unreproducible",
+etc, to document different stages of
their lifecycle. A developer can take ownership of a
bug by tagging it with something like "owner/Joey".