From owner-freebsd-hackers@FreeBSD.ORG Wed May 21 16:16:49 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7D1A967 for ; Wed, 21 May 2014 16:16:49 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D15EC25B5 for ; Wed, 21 May 2014 16:16:49 +0000 (UTC) Received: from Alfreds-MacBook-Pro-2.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 2F2451A3C19; Wed, 21 May 2014 09:16:48 -0700 (PDT) Message-ID: <537CD1EE.2000708@mu.org> Date: Wed, 21 May 2014 09:18:54 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Erik Cederstrand Subject: Re: [GSoC] Machine readable output from userland utilities References: <49E9736E-AD14-4647-8B15-30603D01360C@mail.bg> <91FE2526-F21C-42AB-BECB-058DBA975A9E@cederstrand.dk> <537C2993.1060206@mu.org> <537C63DF.1090402@mu.org> <8DDBACB5-749B-4660-B1DE-F2EE51033D96@cederstrand.dk> In-Reply-To: <8DDBACB5-749B-4660-B1DE-F2EE51033D96@cederstrand.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , Royce Williams X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 16:16:50 -0000 On 5/21/14 2:49 AM, Erik Cederstrand wrote: > Den 21/05/2014 kl. 10.29 skrev Alfred Perlstein : >> This is a great idea. Having compat formats is very important. >> >> That said there are a few things here we can do to keep the scope of this project down to something doable by a student as well as very useful for FreeBSD. >> >> First off we can decide that without any additional specification that v1.0 is the default version, it then becomes up to the app to ask for v2.0, v2.1, etc at a later date. > To keep the scope even further down, why not just adopt the same policy regarding API stability and deprecation as the rest of the FreeBSD project? > That sounds reasonable. Is there a link to the specifics we can have? -Alfred