Re: Let's stop using CVS for debian.org website
Neil McGovern <[email protected]>
| Newsgroups | gmane.linux.debian.devel.www,gmane.linux.debian.devel.general |
|---|---|
| Message-ID | <[email protected]> |
Hi there, On Mon, Nov 21, 2016 at 04:17:27PM +0800, Boyuan Yang wrote: > 在 2016年11月20日星期日 SGT 下午12:08:04,您写道: > > For what it's worth, there's also git-cvsimport(1) and > > git-cvsexportcommit(1) that can be used if someone really wants to > > contribute and doesn't want to touch cvs itself. > > Sure. I tried git-cvsimport to convert the cvs repo into a git repo (with -r > option enabled and -A disabled). The whole process took ~60 hours and the final > git bare repo is ~260MiB large. > > I also found that the process is incremental after the initial import as long > as the history is not modified, which is a really good news for those who wants > to work on the transition. > Thanks for that, it's certainly useful data! > I think we can make a smooth transition through the following process: > > * open a git repository under the webwml alioth team, make an initial import. > * set up a crontab job somewhere (e.g., directly on alioth.d.o) and sync from > the cvs repository to git repository several times every day. Incremental > update is easy and can be finished within 10 minutes every time we sync them. > * gradually port all potential infrastructures (e.g., tools used to update > debian.org website) from cvs repository to git repository. This is the main issue - the actual tooling is fairly straightforward in terms of the get-from-git-and-compile system, but there's a large non-trivial amount of work for the translation systems. Laura Arjona Reina is currently looking at this, and the current thinking (AIUI) is that we need to: * Update the translation system to use Po4a::Wml * Deploy weblate for translations, or modify the process to use hashes rather than version numbers * Update large chunks of the site to use pofiles. Some files use it but not for all content, and there's a number of files that don't use it at all. Help with the above is welcome :) Neil
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEgheiBV5XBDsogwVOf1W7EqQPhi4FAlgzGEwACgkQf1W7EqQP hi56+BAAlnjyEpIvqe0Xf/ITuYc86LlubLdTWWj0Y6X9JZ4I0pYm3zhzvA0iU8eX QuTLwIlEfNDbg+3IsZn5ywJVBUW0Ls/MPMDp+CiCQANFaQcngO4447lpGo7t3BFU emFweiH8pHPJbK1Q+YDyFAk94OH7Q7Jcn+6wOEYGIQsYtq1vkPmEXs9NscmgGBry zSx347ZAivN6orbJPafKn0BuVDqPOCPjsUIGMFXuTtZGCP4YFwedQp5ki8ofby5v 0O6FqZw9qUT2iQVXUG0CnjuALb8OItdAKfqi2DAbjKhBlFwvy94/I+ofu9cBIoKd XDfEoVUSlyeTdN24D5qUGsdBOFXIese57aLijD0T4CF0jHTvIf89PEHiAEQVSvNi knbcJkkV86WUDwSh5+vTjoUiN9cxK2D5XSUsArf5YW2hwtdcQxfs8VUNE8wSZkfQ 7Ubv7PhORDxKfj3k636ou3BEthWoMWI1ijqcbsxwlYedHO/adtIaZktEkNkpZOb9 5YTu9P3SZibPGQ2snGjxhnrByAgx90b2iYBlWkmIHXoLuPG6g1f0dJXnb0dODzAB 1CaihZ2zgVgwZlXOrBlEq/hdwu9CKNFJi5vFh8KyfH+fbmzQziVYZqvd3XbPrkME 7vm47N6Tjk52zT6tceeVIeI/o/5/WtDuSs2LbTVBrOUV452o+OE= =4yfl -----END PGP SIGNATURE-----