This is where announcements of new releases, features, and other news are posted. IkiWikiUsers are recommended to subscribe to this page's RSS feed.

News for ikiwiki 3.13:

The ikiwiki-transition deduplinks command introduced in the last release was buggy. If you followed the NEWS file instructions and ran it, you should run ikiwiki -setup to rebuild your wiki to fix the problem.

ikiwiki 3.13 released with these changes

  • ikiwiki-transition: If passed a nonexistant srcdir, or one not containing .ikiwiki, abort with an error rather than creating it.
  • Allow underlaydir to be overridden without messing up inclusion of other underlays via add_underlay.
  • More friendly display of markdown, textile in edit form selector (jmtd)
  • Allow curly braces to be used in pagespecs, and avoid a whole class of potential security problems, by avoiding performing any string interpolation on user-supplied data when translating pagespecs.
  • ikiwiki-transition: Allow setup files to be passed to all subcommands that need a srcdir.
  • ikiwiki-transition: deduplinks was broken and threw away all metadata stored by plugins in the index. Fix this bug.
  • listdirectives: Avoid listing _comment directives and generally assume any directive starting with _ is likewise internal.
Posted Sat Jun 6 04:03:27 2009

Ikiwiki in svn now has support for using OpenID, a decentralized authentication mechanism that allows you to have one login that you can use on a growing number of websites.

Traditional password-based logins are still supported, but I'm considering switching at least ikiwiki.info over to using only OpenID logins. That would mean blowing away all the currently registered users and their preferences. If you're active on this wiki, I suggest you log out and log back in, try out the OpenID signup process if you don't already have an OpenID, and see how OpenID works for you. And let me know your feelings about making such a switch. --Joey

[[!poll 62 "Accept only OpenID for logins" 19 "Accept only password logins" 36 "Accept both"]]

Posted Sat Jun 6 04:03:27 2009

ikiwiki 3.11 released with these changes

  • Avoid using python-support. Closes: #525086
  • websetup: Display stderr in browser if ikiwiki setup fails.
  • blogspam: Load RPC::XML library in checkconfig, so that an error can be printed at that point if it's not available, allowing the admin to see it during wiki setup. Closes: #520015
  • websetup: If setup fails, restore old setup file.
  • relativedate: Deal with clock skew.
  • Add IkiWiki::ErrorReason objects, and modify pagespecs to return them in cases where they fail to match due to a configuration or syntax error.
  • pagespec_match_list: New API function, matches pages in a list and throws an error if the pagespec is bad.
  • inline, brokenlinks, calendar, linkmap, map, orphans, pagecount, pagestate, postsparkline: Display a handy error message if the pagespec is erronious.
  • comments: Add link to comment post form to allow user to sign in if they wish to, if the configuration makes signin optional for commenting.
  • Updated Danish translation from Jonas Smedegaard. Closes: #525751
  • translation.mdwn: Typo fixes. Closes: #525753
Posted Sat Jun 6 04:03:27 2009

You may want to run ikiwiki-transition deduplinks my.setup after upgrading to this version of ikiwiki. This command will optimise your wiki's saved state, removing duplicate information that can slow ikiwiki down.

ikiwiki 3.12 released with these changes

  • Re-enable python-support and add python:Depends to control file.
  • ikiwiki-makerepo: Avoid using abs_path, as it apparently fails on nonexistant directories with some broken perl versions.
  • inline: Minor optimisation.
  • add_link: New function, which plugins should use rather than modifying %links directly, to avoid it accumulating duplicates.
  • ikiwiki-transition: Add a deduplinks action, that can be used to remove duplicate links and optimise a wiki w/o rebuilding it.
  • external: Fix pagespec_match and pagespec_match_list. Closes: #527281
Posted Sat Jun 6 04:03:27 2009

ikiwiki 3.14 released with these changes

  • highlight: New plugin supporting syntax highlighting of pretty much anything.
  • debian/control: Add suggests for libhighlight-perl, although that package is not yet created by Debian's highlight source package. (See #529869)
  • format: Provide a htmlizefallback hook that other plugins can use to handle formats that are not suitable for general-purpose htmlize hooks. Used by highlight.
  • Fix test suite to not rely on an installed copy of ikiwiki after underlaydir change. Closes: #530502
  • Danish translation update. Closes: #530877
Posted Sat Jun 6 04:03:27 2009

Some people may consider ikiwiki's default look to be a bit plain. Someone on slashdot even suggested perhaps it uses html 1.0. (Yes, an ikiwiki site has survived its first slashdotting. With static html, that's not very hard..) While the default style is indeed plain, there's more fine-tuning going on than you might think, and it's actually all done with xhtml and style sheets.

Stefano Zacchiroli came up with the idea of adding a css market page where IkiWikiUsers can share style sheets that you've come up with for ikiwiki. This is a great idea and I encourage those of you who have customised stylesheets to post them.

I'm also always looking for minimalistic yet refined additions to the default style sheet, and always appreciate suggestions for it.

--Joey

Posted Thu May 28 05:32:36 2009

Quick poll: Do you feel that ikiwiki is fast enough on this server, or should I move it to my much beefier auxiliary server?

[[!poll open=no 40 "It's fast enough" 6 "It's too slow!" 4 "No opinion"]]

If you have specifics on performance issues, you might mention them on the discussion page.

The current server is a single processor 2.8 ghz Sepron machine shared among 4 other xen instances, and often heavily loaded by extraneous stuff like spamassassin and compiles. The auxiliary server is a dual processor, dual core 2 ghz Opteron shared with other xen instances (exact number not available from provider), but with little other load.

Posted Thu May 28 05:32:36 2009

ikiwiki.info has upgraded to the not yet released ikiwiki 2.30. This version of ikiwiki drops support for subscribing to commit mail notifications for pages. The idea is that you can subscribe to the new RecentChanges feed instead. (Or create your own custom feed of only the changes you're interested in, and subscribe to that.)

So if you were subscribed to mail notifications on here, you'll need to change how you keep track of changes. Please let me know if there are any missing features in the RecentChanges feeds.

Statically building the RecentChanges also has performance implications, I'll keep an eye on server speed..

--Joey

Posted Thu May 28 05:32:36 2009
Ikiwiki has its own domain now, ikiwiki.info. Update your links.
Posted Thu May 28 05:32:36 2009

I was asked a good question today: How can a company find someone to work on ikiwiki? To help answer this question, I've set up a consultants page. If you might be interested in being paid to work on ikiwiki, please add your information to the page. --Joey

And here's the first company looking for an ikiwiki developer that I am aware of:

The TOVA Company, a small medical software and hardware company in Portland, Oregon, is looking for developers to add functionality to ikiwiki. We're looking for developers who are already familiar with ikiwiki development, including plugins, and who would be willing to work on a part-time, non-employee, project-based basis for each of the small features that we want. The features we're interested in would obviously be GPL'd, and released to the community (if they'll have them :) ). Please contact Andrew Greenberg (andrew@thetovacompany) if you're interested. Thanks!

Posted Thu May 28 05:32:36 2009

I've started using git as ikiwiki's main repository. See download for repository locations.

Note that all the sha1sums have changed from those in previously published git repositories. Blame git-svnimport.

I hope that this will make it easier to maintain and submit patches for ikiwiki.

--Joey

Posted Thu May 28 05:32:36 2009

Now you can use git to clone this wiki, and push your changes back, thanks to ikiwiki's new support for untrusted git push. Enjoy working on the wiki while offline! --Joey

Posted Thu May 28 05:32:36 2009

Ikiwiki now has an IRC channel: #ikiwiki on irc.oftc.net

The channel features live commit messages for CIA for changes to both ikiwiki's code and this wiki. Plus occasional talk about ikiwiki.

Thanks to JoshTriplett for making this happen.

Posted Thu May 28 05:32:36 2009

Google has accepted ikiwiki as a mentoring organization for Summer of Code 2007.

See our Summer of Code page for projects.

--JoshTriplett

Posted Thu May 28 05:32:36 2009
cia

Commits to ikiwiki's source code are now fed into CIA, and can be browsed, subscribed to etc on its project page. Note that changes to the documentation wiki are currently excluded.

Posted Thu May 28 05:32:36 2009

I've put together a short screencast that covers approximatly the first half of the setup document, and includes a demo of setting up a blog using ikiwiki.

http://kitenet.net/~joey/screencasts/ikiwiki_blog/

.. And now I've added a second screencast. Note that this uses a script that is only available in the as yet unreleased ikiwiki version 2.15.

http://kitenet.net/~joey/screencasts/ikiwiki_cgi_and_git/

--Joey

Posted Thu May 28 05:32:36 2009

I've produced a code_swarm visualization of the first 2+ years of ikiwiki's commit history.

screenshot

PS, while I'm posting links to videos, here's a video of a lightning talk about ikiwiki.

--Joey

notes

Interesting things to watch for:

  • Initial development of ikiwiki to the point it was getting web edits. (First 2 seconds of video!)
  • Introduction to plugin support, and later, plugin changes dominating code changes.
  • Introduction of openid support and the resulting swarm of openid commenters.
  • Switch to git, my name in the logs changes from "joey" to "Joey Hess", and there are more code commits directly from others.

Getting the commit log was tricky because every web commit is in there too, so it has to deal with things like IPs and openids. The code swarm log.pl script will munge the log to handle these, and it was configured with code swarm.config.

Video editing by kino, ffmpeg, ffmpeg2theora, and too many hours of pain.

Audio by the Punch Brothers.

Posted Thu May 28 05:32:36 2009
Integrated issue tracking with Ikiwiki by Joey Hess is now available on LinuxWorld.com. (LinuxWorld's author contract also allows this article to become part of the project's documentation.) Learn how to use Ikiwiki inlining and PageSpecs for lightweight workflow. Joey also explains how having the BTS and docs in the project's revision control system can help users of distributed revision control systems keep bug tracking info in sync with code changes.
Posted Thu May 28 05:32:36 2009
After looking up and noticing that another 8 hours had passed, replying to people and hacking, I've added a TipJar page, in case anyone feels like tossing me a few bucks for ikiwiki. TIA! --Joey
Posted Thu May 28 05:32:36 2009

Ikiwiki has reached version 3.0 and entered a new phase in its development cycle.

The 3.0 release of ikiwiki changes several defaults and finishes some transitions. You will need to modify your wikis to work with ikiwiki 3.0. A document explaining the process is available in upgrade to 3.0.

The highlights of the changes in version 3.0 include:

Thanks to the many contributors to ikiwiki 3.0, including:

Jelmer Vernooij, Recai Oktaş, William Uther, Simon McVittie, Axel Beckert, Bernd Zeimetz, Gabriel McManus, Paweł Tęcza, Peter Simons, Manoj Srivastava, Patrick Winnertz, Jeremie Koenig, Josh Triplett, thm, Michael Gold, Jason Blevins, Alexandre Dupas, Henrik Brix Andersen, Thomas Keller, Enrico Zini, intrigeri, Scott Bronson, Brian May, Adeodato Simó, Brian Downing, Nis Martensen. (And anyone I missed.)

Also, thanks to the users, bug submitters, and documentation wiki editors. Without you, ikiwiki would just be a little thing I use for my home page.

--Joey

Posted Thu May 28 05:32:36 2009

I've gone ahead and moved ikiwiki.info to the faster box mentioned on server speed. Most poll respondants felt the old box was fast enough, but it's getting a bit overloaded with other stuff.

If you can see this, you're seeing the new server. If not, your DNS server hasn't caught up yet. I'll keep the old server up for a while too and merge any changes across since git makes that bog-easy.

Please report any problems..

Posted Thu May 28 05:32:36 2009

Ikiwiki has reached version 2.0 and entered a new phase in its development cycle.

With the 2.0 release of ikiwiki, some major changes have been made to the default configuration:

  • The usedirs setting is enabled by default. This will break all URLs to wikis that did not have usedirs turned on before, unless you follow the procedure described at switching to usedirs or edit your setup file to turn usedirs off: usedirs => 0,
  • OpenID logins are now enabled by default, if the Net::OpenID::Consumer perl module is available. Password logins are also still enabled by default. If you like, you can turn either OpenID or password logins off via the disable_plugins setting.

An overview of changes in the year since the 1.0 release:

  • New improved URLs to pages via usedirs.
  • OpenID support, enabled by default.
  • Plugin interface added, with some 60 plugins available, greatly expanding the capabilities of ikiwiki.
  • Tags, atom feeds, and generally full-fledged blogging support.
  • Fully working utf8.
  • Optimisations, approximately 3.5 times as fast as version 1.0.
  • Improved scalability to large numbers of pages.
  • Improved scalable logo.
  • Support for additional revision control systems besides svn: git, tla, mercurial.
  • Some support for other markup languages than markdown: rst, textile.
  • Unit test suite, with more than 300 tests.
Posted Mon Apr 30 13:51:57 2007

By the way, some other pages with RSS feeds about ikiwiki include plugins, TODO and bugs.