Development

Status

The NASPRO project officially started on the 24th of February 2007, the whole thing is still in first implementation phase and there has been only a first release.

This is because I'm working on it only in my spare time and also because I actually wrote some thousands of lines of code, but then had to refactory the core library API several times in order to add some functionality or to make it behave better.

As of now, development is proceeding, even if at a slow rate.

Places of discussion

This website

This website, apart from "advertising the product", is intended to give interested people an easy and fast way to comment, give feedback, send opinions, share ideas, etc., or, to say better, to create an active community around this project.

So this is definitively intended to be the place for discussion among interested people.

The NASPRO wiki

Our wiki is not properly a place of discussion, but a place where it is possible to collect information in an organized way, share information and expose ideas in detail without the typical dispersion characterizing other kinds of collective spaces. Everyone is allowed to use and modify it.

Mailing lists

We have two mailing lists. One is the NASPRO-news mailing list, which is a very low traffic newsletter useful to people who just want to know what's going on.

The other is the NASPRO-devel mailing list which is, instead, the place where developers can discuss more technically about NASPRO development.

This doesn't mean that it's an exclusive club (everyone can subscribe and the list is not moderated), but that it is the place where development is coordinated and things happening in there are probably of low interest for end users.

IRC channel

Our official IRC channel is #naspro on irc.atheme-project.org. Feel free to join!

Contacts

If you need to privately contact someone working on the project, you can take a look at the People page.

Code and releases

atheme.org

This project is part of the atheme.org community and uses the community facilities for managing and distributing code.

Mercurial repository

This project usees Mercurial as its source code management system. The code repository contains the code on which developers are currently working, which means that it is not supposed to be stable, tested, well-behaving, supported and/or documented, it is only suitable for development and testing purposes.

If you choose to give it try, you do it at your own risk (legally speaking, it works this way with releases too, but in practice these should be much more tested and less likely to destroy your hard drive or to hurt your feelings).

You can grab a copy of the repository performing the following command:

$ hg clone http://hg.atheme.org/naspro naspro

Roadmap

There is no official roadmap yet.

Release version numbers

On each full NASPRO release, all components of NASPRO will have the same release version number. The version number assignment for each release goes like this:

• major version number will be increased for drastical changes and/or accomplishment of big tasks;
• odd minor version numbers (eg. x.1.z, x.3.z, etc.) indicate unstable development releases, while even ones are for stable releases (eg. x.0.z, x.2.z, etc.);
• releases with different revision numbers will differ only by bugfixes and little impovements.

Apart from the official versioning scheme, NASPRO libraries follow the Libtool's policy for interface versions.