A decentralized development model

MlView is developed by a small team of benevolent volunteers. The sources of the projects is primarily managed using GNU ARCH. The content of the MlView GNU ARCH repository is regularly mirrored in the GNOME CVS. This eases the job of GNOME translators who work primarily with the sources that are in the GNOME CVS.

Working with GNU ARCH allows MlView developers to interact in pretty much the same way as the Linux kernel developers interact. Each developer has got his own private source tree. There is also a source tree identified as the project official source tree. A given developer commits patches in his own private source tree as he wants without requesting any write access to any central code repository. We don't have any central code repository everybody commits code to. When the developer is happy with his codebase, he advertises his patches on the developers mailing list. The MlView main maintainer can then pull the advertised patches seemlessly and merge them in the official tree. This pull and merge machinery is made simple by the power of GNU ARCH. At any time, developers can synchronize their private tree with the changes that happened in the official tree. Here again, GNU ARCH helps with the process of merging patches from a tree to another.

That being said, if you want to hack on MlView, we strongly advise you to check out the sources from the GNU ARCH archive. See instructions below. If you are scared by GNU ARCH, you still can check out the sources from the GNOME CVS and send your patches to the mailing list or attach them in bugzilla .