following the very successful launch of LiVES version 1.0.0, the project
is now seeking more developers to get involved with ongoing development.
To this end, I am making a couple of updates here. First of all, the LiVES
code repository will be migrated from CVS to subversion on sourceforge.
The 1.0.0 release will then become a branch on the tree, and only bugfixes
will be backported to it. This will allow for long term support of the
stable 1.0.0 release. The main branch will continue to be development as
we move towards LiVES 2.0.0
At the same time, the LiVES manual will be migrated to a wiki -
livesdoc.wetpaint.com. This version will be maintained and updated, and
there will be periodic releases from this.
If you want to get involved with either development and/or documentation,
here is how.
1) Development. First make sure you are a member of the lives-devel
mailing list. Secondly, you can either propose a new feature, or pick one
of the many existing feature requests from:
Send a message on the lives-devel mailing list about what you plan to do.
If you need technical help, you can schedule some time for a chat on IRC
You will be expected to produce some kind of spec to show that you know
what you are doing, a time limit will be agreed, and the feature will then
be assigned to you.
You will then be expected to produce a patch within the time limit agreed.
The patch will be reviewed, and after it has been accepted it will be
checked into the development branch.
2) Documentation. If you find an error or omission in the LiVES manual, or
want to document a new feature, create an account on wetpaint.com, and
then email me to request editor access. You can then update the working
version in the wiki.
Get latest updates about Open Source Projects, Conferences and News.