From owner-freebsd-doc@FreeBSD.ORG Tue Aug 21 19:57:23 2012 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 61745106566C; Tue, 21 Aug 2012 19:57:23 +0000 (UTC) (envelope-from simon@FreeBSD.org) Received: from emx.nitro.dk (leto.nitro.dk [178.63.52.6]) by mx1.freebsd.org (Postfix) with ESMTP id 181038FC1E; Tue, 21 Aug 2012 19:57:22 +0000 (UTC) Received: from mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) by emx.nitro.dk (Postfix) with ESMTP id E45F52B75A5; Tue, 21 Aug 2012 19:57:21 +0000 (UTC) Received: from emx.nitro.dk ([127.0.1.2]) by mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) (amavisd-new, port 10024) with LMTP id 2F1IebfEMDV7; Tue, 21 Aug 2012 19:57:19 +0000 (UTC) Received: from [192.168.4.24] (unknown [89.100.2.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by emx.nitro.dk (Postfix) with ESMTPSA id 53A6B2B759F; Tue, 21 Aug 2012 19:57:19 +0000 (UTC) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) From: "Simon L. B. Nielsen" In-Reply-To: <50326A70.5020009@FreeBSD.org> Date: Tue, 21 Aug 2012 20:57:17 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <50326A70.5020009@FreeBSD.org> To: Gabor Kovesdan X-Mailer: Apple Mail (2.1485) Cc: doceng@FreeBSD.org, doc@FreeBSD.org, www@FreeBSD.org Subject: Re: doceng... X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 19:57:23 -0000 On 20 Aug 2012, at 17:48, Gabor Kovesdan wrote: > I'm glad to announce that the first milestone of the XML migration is > available for review in the projects/sgml2xml branch. To check it out, > run the following: [cut] > Regards, > Gabor > (On behalf of doceng@) [separate mail to not confuse different topics] Does that mean that the role of doceng has changed? In the past doceng = has not really been involved in stuff like this (as in, it was much more = limited what doceng did for doc compared to what portmgr does for = ports). If so, the charter should be updated. (and yes, my implicit hint = is that I don't see a point in doceng taking on this new role.) --=20 Simon L. B. Nielsen