Contribute
|
|
|
|
Contents |
Packaging
Packages should be versioned in the following way. Here, $VERSION refers to the version specified in configure.ac or setup.py. rN refers to the bzr revision number of the source being packaged, if not packaged from a release, and $BUILDID is the build string (aka. "package version", typically of the form 0ubuntu1 for packages in Ubuntu, for build strings for PPA builds, see https://help.launchpad.net/Packaging/PPA ), which may include the PPA index, and SERIES index as applicable for building in a PPA, or repository which is not the official distribution package repository.
- Released tarball versions: $VERSION-$BUILDID
- Snapshot from bzr (nightlies): $VERSION+rN-$BUILDID
Bugs
Ubuntu One bug work flow shows the typical flow of a bug from the time it is reported until it is worked on by a developer. Start here if you want to understand how to triage bugs for Ubuntu One.
Bug tips & tricks gives common problems, useful troubleshooting information, standard bug responses, and more. Use this page to help triage bugs.
Testing
Run the latest version of the client to help test the latest code before it's even released. This can be useful if you know there is a fix waiting to be released.
User Defined Folder (UDF) integration tests lists integration tests that exist for this new Ubuntu One files feature for Lucid.
Windows building & Testing gives information of how to build and test the windows client.
Code and Licensing
Location |
Licence |
Contributing |
Forking |
Hidden re-use |
Desktop |
GPLv3 |
Yes |
Yes |
|
Both |
AGPLv3 |
Contributor agreement |
Yes |
No |
Server |
Proprietary |
Canonical employees |
No |
No |
For contributions to be accepted back and integrated into the tree, copyright on the changes must be assigned to Canonical.
UbuntuOne/Contribute (last edited 2010-07-23 14:15:39 by mandel)



