Development strategy:
-We agreed that the way development would work is that everyone gets
their own personal repositories. If you want to publish your work, it
can be hosted on google code as a clone, or bundled and emailed to
Lucas (or someone else).
-If you are working on a project in collaboration, you may want to
share a repository. This could be done on google code or somewhere
private (maia01, for example, at NCSU).
-When you have finished something that you think others may be
interested, it's a good idea to publish the code in your clone and
send out a message on this list.
-If you want something someone has published, then you can pull it
immediately from them or wait for Lucas (again, or someone else you
trust) to integrate it in his branch and just keep up with him.
-The idea is to keep pretty flexible, but a small amount of
communication is important, so let's make sure to use this list.
-This list can also be used for questions about the code.
-Please invite others that are developing on QWalk to this list so
they can join the community.
We're currently thinking about making a QWalk version 1.0. To that
end, outstanding bugs and feature requests can be submitted to
http://code.google.com/p/qwalk/issues/ . Put in the V1.0 tag if you
think it should be there.
Cheers,
Lucas