This doesn't actually involve any code changes as such. Updating/adding comments, describing the operation of complex areas of the code. cleaning up the use of variable/function names to make sure that they are all consistent/meaningful. Possibly try to incorporate some Doxygen based automatic developer documentation generation. Big job, boring, ideally should be taken on by multiple developers to reduce the boredom.

Update the code comments to both provide Doxygen documentation functionality, and to improve the functional documentation within the code to enable newcomers to better understand the inner workings.

For the sake of creating a special speed-orientated binary quickly (for presentation/demo use) any 'Quick-n-Dirty' hacks, though not ideal, would be useful - Even if it means sacrificing some of AQSIS' capabilities (for this binary only).

Make the current features work at a speed that is at least comparable with other solutions. The big boys (PRman, 3Delight, RenderDotC, Air etc.) outperform us by quite some margin at the moment. Even JRMan and Pixie are faster in many cases. This needs as an absolute priority to be addressed for us to be considered a contender.

RC 1 represents the 'Basic' (no shader management) iteration of NEQSUS, a GUI for the AQSIS suite of tools. Leon: Found some help in the form of Bobby Parker, of which I would like to take the opportunity of welcoming him to the Aqsis community.

First official release represents the addition of shader/material management within NEQSUS.

Release 1.1 represents the the dynamic/realtime capabilities of NEQSUS, by collaborating with external projects like CGKit (http://cgkit.sf.net).

The great hunt for the 'Support' co-ordinator begins. This role will involve either working alone or collaborating with a team to achieve their goals. Note: The most important pre-requisite here is free-time, with experience being second. Leon: I would like to take this opportunity to welcome David Keegan, our new 'Support' lead, to the Aqsis community.

Sadly lacking, as always, the documentation needs to be beefed-up considerably.

Sadly lacking, as always, the documentation needs to be beefed-up considerably.

As much for end-users as developers, we should aim to keep comparitive information up-to-date.

We really need to encourage more people to produce more content. At the moment, our portfolio of content is, at best, embarassing. I don't want to disrespect the work of those who have contributed to the gallery, but it is just not in the same league as others. This really needs to be addressed, I feel 100% confident that people are daily put off the idea of Aqsis purely on the strength (weakness) of the gallery content.

We need to somehow encourage more developers to come to the project and contribute real work. We've had a number of people pop in and out, and submit snippets, but we need more dedicated developers. People we can trust to be allocated a new task, and just get on with it, and more importantly, take it to completion.

Distributable marketing-material. Leon: I have already started work on this, mainly on the 'Branding' side, but are hanging-fire until the 'Gallery' gets some new content.

A 'Focused' campaign, posted at the usual places, cementing AQSIS in the minds of the creative community - Both OSS and commercial.

The aim here is to find a commercial (wide-audience) project that AQSIS can be used in - 'Proof-is-in-the-Pudding' style.

Using exisiting tutoial(s) as a basis, create a magazine-quality tutorial (PDF format).

There is already history between both K-3D and AQSIS, but better feature-set co-ordination between projects could prove beneficial. Paul: Spoken to Tim, and he seems very interested in doing something/co-ordinating our efforts.

About 12-18 months ago, Nevercenter contacted Paul in regards to doing something with AQSIS in regards to Silo. Leon: After speaking to Nevercenter, they're not interested in integrating a renderer, but maybe there's still something we can do here. Leon: Dead-end, not really interested in doing anything with us.

The goal here is to show the Blender community to the power of RenderMan (via AQSIS), in an attempt to raise awareness and attract interest. Leon: At present I am waiting for Ton (Rosendaal) to get back to me on this. Leon: Ton has now confirmed this so we can now progress to the next stage.

CGKit is a great way to automate a RenderMan-based renderer such as AQSIS. Closer co-ordination between features could be of benefit. Paul: Matthias seems interested in doing something together, but don't know if it will be *just* a joint binary.

Donations, commercial backing (via tools/integration), OSS funding, etc.

To help provide users with a better experience, separate the AQSIS site so that downloads remain of SourceForge while the site itself is housed at a different (preferably fast) host. Cost will be an issue here, which is why we should first attempt some form of 'Free' service from friendly hosting companies. The sooner this is done the better !!! ;-) Leon: Arragned 'Free' (v)hosting with OSL, which also provide services/expertise to Mozilla, Apache and Drupal. This has greatly improved the whole Aqsis experience, so a BIG shout-out goes to you guys - Thanks !!! :-)

The university of Gloucestershire (UK) are planning to introduce a 'Game Design' course in September 2006. They seem interested in the idea of using AQSIS on their course, but will require higher-level tools (like NEQSUS/3DMax plugin) as the students will doubtfully be from a technical background. Leon: Been speaking to one of the guys there, and keeping in touch every so often to get their current status.

This is the number one requested feature, a requirement to be taken seriously in the Renderman arena these days.

While standards are important, offering something unique can also encourage new people to take notice. For example features such as layered shaders as imlpemented

Currently to access some of the important features in Aqsis requires a great deal of effort on the part of the artist. For example, shadowmapped occlusion can produce some very impressive results, but needs a lot of effort. Anything that can automate this process will make Aqsis appeal more to the POV type of user, who just want shadows, and don't care about the technicalities of shadowmaps and bias.

Currently an ideas-factory, but looking ahead to technology trends such as Dual-Core CPU's and programmable/scalable GPU's. Also looking ahead to useful features, like 'Geometry' shaders (ala Angel).