Broad community discussion

Akara mailing list.

Developer discussion

Akara developer mailing list.

Issue tracker

http://trac.xml3k.org/

Akara/Dev/Getting started as an Amara/Akara developer

Current work docket

The current emphasis for Amara and Akara is to meet the "Safe Harbor" milestone (planned to coincide with Amara 2.0a2 and Akara 2.0a1). This broadly means: enhanced Amara 2.x test suite, an Akara 2.x test suite, some key bug fixes and better release process. Some of the more granular tasks:

• Enhance test framework
• Improve test coverage

• Review the system for XPath/XSLT extensions (see: Amara2/XSLT_Extensions)

• Targeted defects are basically everything for the "safe harbor" milestone: http://trac.xml3k.org/report/10

• Akara Pipelines/Web Triggering: Akara/Manual#Pipelines

• Amara 2.0a2 release ( http://wiki.xml3k.org/Amara2/Developer_notes#Nextrelease.282.0a2.29 )

• Akara 2.0a1 release

Future milestones

Beyond "Safe Harbor", here are some expected tasks.

• 4Suite minor release
• Richer mount points

Profiling

• Profiling notes for Django

Other possible tools & techniques

• repoze.who, for auth

• paste.lint, for testing

Remain mindful of

• W3C's "Common HTTP Implementation Problems"

• "Best way to serve wsgi with multiple processes "

i18n

• Babel

Other projects with heavy overlap with Akara

• Atomisator

See also

• Akara/Configuration

• Akara/Architecture

Origins

Akara is a new synthesis of the following older projects:

• 4Suite repository
• WSGI.xml
• xsltemplates
• Akara 1.0

There was an abortive Akara 1.0 branch, which is abandoned for Akara 2.0 plans.