Date: Mon, 12 Mar 2001 21:38:31 +0000 From: Nik Clayton <nik@freebsd.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Nik Clayton <nik@FreeBSD.org>, doc@FreeBSD.org, Udo Erdelhoff <ue@nathan.ruhr.de>, Chris Costello <chris@calldei.com> Subject: Re: Translators: Need feedback on FAQ reorganization Message-ID: <20010312213831.A74204@canyon.nothing-going-on.org> In-Reply-To: <XFMail.010312112136.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Mon, Mar 12, 2001 at 11:21:36AM -0800 References: <20010312093551.A3114@canyon.nothing-going-on.org> <XFMail.010312112136.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 12, 2001 at 11:21:36AM -0800, John Baldwin wrote: > > I like the idea of a branch in the FAQ, because then no one has to do > > anything different to get it -- supfiles will still work, and so on. >=20 > A branch is painful. =20 Why? I've used CVS branches before (outside FreeBSD) for just this purpose. > Since the FAQ shouldn't be broken, there's no reason to > not just do this on HEAD. =20 Not so much broken, but I expect there will be periods where it's very=20 confusing to readers as the content migrates all over the place. > The DocBook -> LinuxDoc was a bit different, as in > some of your steps it didn't build, IIRC. If that was not the case, then= it > should've been done in the tree with a checkin at each milestone as it we= re. It was done in the tree. We were able to do the Handbook in the tree because the conversion coincided with moving the Handbook from one directory in the tree to another. I just did all the work in the new directory, and the handbook's old directory wasn't touched until the conversion was over. Since we're not planning on moving the FAQ's location in the repo this option isn't available to us. > > When the work is finished, and committed to HEAD, it might be possible = to=20 > > excise this branch from the repo if it's considered bloat. Otherwise we > > can live with it. >=20 > See, we don't need this extra headache. =20 Then we don't have to do this step. I suggested it to pre-empt anyone who might want to bring up repo-bloat as a reason for not doing it. > Also, the merge to HEAD will be > painful if other changes are committed to the FAQ during the move. =20 Possibly I've got the wrong impression here, but I wasn't expecting this to be an overnight job. I've assumed it will probably take a few days, or a week, and that it's entirely possible Chris might go AWOL for a few weeks due to real life (no slight on Chris intended, I've had to do exactly the same myself). If this happens, the current FAQ needs to remain accessible and understandable. My assumption was that the people doing the work on FAQng would be periodically pulling changes from the HEAD back on to their branch. We might have a flag day in which the FAQ is frozen except to the FAQng team to give them breathing space to do any last merges before replacing HEAD, but that's about it. If that's not the case, and we're talking about a mad flurry of individual commits in the space of a night, then that's different. > Instead, > commits during the move will be separate events that the translators can = just > treat as autonomous little events. =20 If the commits leave the FAQ buildable (which I assume they will) and if (and this is much more important) the individual commits leave the FAQ usable to its audience. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjqtQdYACgkQk6gHZCw343U76gCgkJF9e1nTxvBTF+FkjX178Zaw vikAn3VxQ4uwXdRH0TjiXnXgz2FV1X5E =bzbg -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010312213831.A74204>