The KForge Project

KForge v0.16 is now nearly done and has been deployed as a release candidate on http://knowledgeforge.net/ and http://demo.kforgeproject.com/.

This release includes:

• Clean-up of authentication system
• This eliminates svn 1.5 bug (svn add did not work under svn 1.5)
• Deployment under virtualenv for sandboxed installations
• Increase compatibility across external libs (e.g. django 1.0)
• Variety of other minor but important fixes as we prepare for the release of v1.0

KForge 0.15 is out. Get it via the download page:

http://www.kforgeproject.com/download/

Changes

• KForge plugin discovery via setuptools entry points
• Mercurial plugin providing support of mercurial/hg repositories
• (Partial) move to nosetests for testing
• Improved documentation
• Debian package version

About KForge

KForge is an open-source (GPL) system for managing software and knowledge projects. It re-uses existing best-of-breed tools such as a versioned storage (subversion), a tracker (trac), and wiki (trac or moinmoin), integrating them with the system’s own facilities (projects, users, permissions etc). KForge also provides a complete web interface for project administration as well a fully-developed plugin system so that new services and features can be easily added.

For more information see the about page: http://www.kforgeproject.com/about/

KForge v0.15 has been pretty much ready to go in subversion for the last 6 months. However, even with heavy unit testing plus daily builds and deployments we don’t like to release until we’ve run for a few weeks on our live systems to check everything is working perfectly. Due to our busyness with other things this last and final stage of checking has only started in the last few weeks. So far everything looks good and therefore KForge is like to be out the door right after the new year.

We’ve been making a lot of progress on trunk since our last stable release (KForge 0.11). The main focus has been on focusing out core code into a separate package named DomainModel (python package: dm). This refactoring has become increasingly necessary as the core KForge code has started to be reused in other projects such as CKAN (Comprehensive Knowledge Archive Network). With this refactoring complete it is now much easier to reuse core components and the clean separation of code is also making testing easier.

The KForge command line interface has been extensively overahauled and centralized into a single script: kforge-admin (the other remaining scripts are only used for development).

Not only does kforge-admin centralize all the old commands in one handy place it also provides interactive support and makes it easier to move between different KForge installations (something also assisted by the move to a default of site-wide installation of the KForge system when you run python setup.py install). You can find more about exactly what it will do by just running: $ kforge-admin

Quite a bit of effort has been put into improving the help and making this slicker but I’m sure rough edges remain. If you encounter one please let me know (or post a trac ticket).

KForge 0.9 is now done and dusted but we’ve decided to hold off the formal release until the new year. We’ve done this for two reasons. First off, this will give us some time to ‘eat our own dog food’ (i.e. install it on our servers) so as to catch any last minute items. Second, and more important, it will mean that rather than being caught up in the last minute rush before Christmas it will instead be rolled fresh and clean in the New Year when everyone (including ourselves) will have proper time to digest.

A new release of KForge (0.9) will be available any day soon with a release date set for late next week or early the week after — whatever happens it will be before christmas .

Welcome to the KForge Project site. The KForge project is about producing software to support open knowledge production and distribution. Work on the software has been ongoing for about a year but as we’re nearing our first full-on ‘release’ we thought it was time to get a ‘proper’ website ….