definitely. Only Paul can close down the sourceforge cvs, but it does have some historical value as I started the charon repository at LMCE 0704, while the sourceforge cvs contains LMCE 1.0
There are two trees to pay attention to in the charomedia repo. The trunk obviously, and the vendor/pluto-lmce-branch.
The trunk branch is the one that will compile on an LMCE 0704 system, while the pluto branch contains syncs from pluto's private branch (with a few NDAed and irrelevant pluto specific components removed.)
For bugs in the pluto branch (the one the beta's are based off of) use Mercurial to report any bugs. For bugs specific to the charonmedia trunk use the trac bug tracker at svn.charonmedia.org.
Those resources are all valuable. But their value would be much easier to exploit if they were all available at the same server, and through the same Mantis GUI. That kind of integration is what makes LMCE so powerful, but its fragmentation currently makes adding new developers (including myself) hard, and probably slows down existing developers. It's an important limit to scaling the LMCE developer community that we should target eliminating.
In the meantime, do you think you could update the "Building From Source
" article (which currently contradictorily points at all of SourceForge/SVN, Charon Media, and the Mirrors page for source, each of which is a different version)? And maybe the "LMCE Mirrors page
, which lists only 0704. Once the Building page is updated, I can update the basic Source Code article.
PS My plan is to move the charonmedia.org svn to svn.linuxmce.org to avoid any confusion, but Paul still controls the domain name and the current linuxmce.org server isn't equipped to handle the strain of an svn server in addition to it's current duties.
I've got an extra hosted server (P4/4.2GHz, dedicated root, up to 1.2TB:mo bandwidth) that I could offer to host a SVN website, if it's sufficient.