From bpfk-list+bncCK30vq5WEP3R5-UEGgS6-XeU@googlegroups.com Sat Oct 16 11:03:56 2010 Received: from mail-pv0-f189.google.com ([74.125.83.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P7B6n-000890-9Q; Sat, 16 Oct 2010 11:03:56 -0700 Received: by pvc22 with SMTP id 22sf1126617pvc.16 for ; Sat, 16 Oct 2010 11:03:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:received:received :received:received-spf:received:date:from:to:subject:message-id :mail-followup-to:references:mime-version:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type :content-disposition:content-transfer-encoding; bh=kbrf8VECDqU/p0GhRz4qXksWI3GS1aPgSfjXajzxxoI=; b=AnlYbMb7Xq+PnN4fGgk6B44jfyE4C+sQQdEho0RstaziuVSUaAcq6YNVwzyQH/nrvI eLLx+6r4O3LxJpiYe9Rg3yxiHeGLTJYxRqoc5yXje8BsApUe6tbRWwjQwC+nVY8rYwFL pQCKU3DX7edLZNG7KOqdj1SzetkTjcPEGQiXs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:date:from:to:subject:message-id :mail-followup-to:references:mime-version:in-reply-to:user-agent :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe:content-type :content-disposition:content-transfer-encoding; b=PRYrILbSs0J6SzHLAwhUBxxwNUHyXFuGHw6p16mqNQxUJEeMk/tsRUaGWVvpmpudHf ryQo5TTfV/cdgE1RbGJhYvyQUXILODltJyL+WYofgU71bL3HxDyPcY3xETJ1suUypbde FyNoSdRjdza4AuDio+wtaN1nUYLltaTl/nxJw= Received: by 10.143.20.28 with SMTP id x28mr57468wfi.61.1287252221852; Sat, 16 Oct 2010 11:03:41 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.142.2.41 with SMTP id 41ls3029101wfb.0.p; Sat, 16 Oct 2010 11:03:41 -0700 (PDT) Received: by 10.142.52.17 with SMTP id z17mr1173521wfz.61.1287252221407; Sat, 16 Oct 2010 11:03:41 -0700 (PDT) Received: by 10.142.52.17 with SMTP id z17mr1173518wfz.61.1287252220895; Sat, 16 Oct 2010 11:03:40 -0700 (PDT) Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234]) by gmr-mx.google.com with ESMTP id n6si13538557wfl.3.2010.10.16.11.03.40; Sat, 16 Oct 2010 11:03:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of rlpowell@digitalkingdom.org designates 173.13.139.234 as permitted sender) client-ip=173.13.139.234; Received: from rlpowell by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1P7B6Z-00088c-I0 for bpfk-list@googlegroups.com; Sat, 16 Oct 2010 11:03:39 -0700 Date: Sat, 16 Oct 2010 11:03:39 -0700 From: Robin Lee Powell To: bpfk-list@googlegroups.com Subject: Re: [bpfk] What I'm going to do. Message-ID: <20101016180339.GG25393@digitalkingdom.org> Mail-Followup-To: bpfk-list@googlegroups.com References: <20101014071951.GU24066@digitalkingdom.org> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Original-Sender: rlpowell@digitalkingdom.org X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of rlpowell@digitalkingdom.org designates 173.13.139.234 as permitted sender) smtp.mail=rlpowell@digitalkingdom.org Reply-To: bpfk-list@googlegroups.com Precedence: list Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 14, 2010 at 11:28:32AM -0300, Jorge Llamb=EDas wrote: >=20 > Every January 1st. the BPFK publishes a very concise "State of the > Language" report, that looks something like this: >=20 [snip] >=20 > That should be published in some prominent BPFK site, where each > year's new "State of the Language" report is added. >=20 > BPFK recommendations are just what their name suggests, but they > give the community a sense of what the BPFK is doing (and also > helps us keep track of what we are failing to do). >=20 > The CLL-2011 document will most likely contain some internal > inconsistenies, and there may be a few inconsistencies between it > and cmavo-2011, but it doesn't matter, we publish it all the same, > CLL-2012 and cmavo-2012 will fix some of them, and CLL-2013 and > cmavo-2013 will fix some others, and so on. Something imperfect is > better than nothing. I like that. > In the meantime, we can keep working, but we are committed to > present a State of the Language Report every January 1st, no > matter how little has been resolved the previous year, and no > matter that we know that there are outstanding issues. >=20 > The LLG may, in turn, if it so wishes, in its June or whenever > meeting, give its blessing to what the BPFK has presented on > January 1st, suggest to the BPFK that it look deeper into this or > that language issue, and so on. >=20 > What do you think? Works for me. You gonna tell them about your other idea? :D -Robin --=20 http://singinst.org/ : Our last, best hope for a fantastic future. Lojban (http://www.lojban.org/): The language in which "this parrot is dead" is "ti poi spitaki cu morsi", but "this sentence is false" is "na nei". My personal page: http://www.digitalkingdom.org/rlp/ --=20 You received this message because you are subscribed to the Google Groups "= BPFK" group. To post to this group, send email to bpfk-list@googlegroups.com. To unsubscribe from this group, send email to bpfk-list+unsubscribe@googleg= roups.com. For more options, visit this group at http://groups.google.com/group/bpfk-l= ist?hl=3Den.