Received: from mail-pv0-f189.google.com ([74.125.83.189])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <bpfk-list+bncCJ2UzZHuDRDsqtzlBBoE9ANgHQ@googlegroups.com>)
	id 1P6Ov9-0000L6-VD; Thu, 14 Oct 2010 07:36:49 -0700
Received: by pvc22 with SMTP id 22sf1731504pvc.16
        for <multiple recipients>; Thu, 14 Oct 2010 07:36:34 -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:received:received:mime-version
         :received:received:in-reply-to:references:date:message-id:subject
         :from:to: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;
        bh=UKCMD8rp5RoFNF0jtxz3MfWbhgioOeVg9qKur8CS/SM=;
        b=K0NJYg3sfW1zkBTwdjsVS2Kx8HFntLCWCMQbmOE7OvGciwiiWgiHrSKbVTh5jSkcOH
         dsiUa1kyQpKvJxUiVTcU4mlQj/wdKt5EDACqxSxaeTzVfkRgAKCLwR/BJER9TFpn5PHQ
         CkAx5+TkNx4hjzU5J3Z5LtwE+xEaJ39DBwlWQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlegroups.com; s=beta;
        h=x-beenthere:received-spf:mime-version:in-reply-to:references:date
         :message-id:subject:from:to: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;
        b=0p+7/tKYhgri066aZfjsS1zWciNw7aC96F7RbOjbFOlFLWoreP6uGkpVRfxwhiy4Hh
         qUraMA0jxa0folCvGaDgvQUUxIWhJQKPy6X+ql3yQozyldBoOhiClZknV9SzQcS8ijyr
         KU5/V/3M1Aniz7PaRkgFyPA0YiyNMENODysQo=
Received: by 10.142.65.4 with SMTP id n4mr515585wfa.54.1287066988337;
        Thu, 14 Oct 2010 07:36:28 -0700 (PDT)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.142.70.10 with SMTP id s10ls1060230wfa.1.p; Thu, 14 Oct 2010
 07:36:26 -0700 (PDT)
Received: by 10.142.133.15 with SMTP id g15mr3539650wfd.26.1287066985171;
        Thu, 14 Oct 2010 07:36:25 -0700 (PDT)
Received: by 10.142.133.15 with SMTP id g15mr3539649wfd.26.1287066985148;
        Thu, 14 Oct 2010 07:36:25 -0700 (PDT)
Received: from chain.digitalkingdom.org (digitalkingdom.org [173.13.139.234])
        by gmr-mx.google.com with ESMTP id p40si14811911wfc.6.2010.10.14.07.36.24;
        Thu, 14 Oct 2010 07:36:24 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of nobody@digitalkingdom.org designates 173.13.139.234 as permitted sender) client-ip=173.13.139.234;
Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72)
	(envelope-from <nobody@digitalkingdom.org>)
	id 1P6Out-0000An-22
	for bpfk-list@googlegroups.com; Thu, 14 Oct 2010 07:36:23 -0700
Received: from mail-ww0-f53.google.com ([74.125.82.53])
	by chain.digitalkingdom.org with esmtp (Exim 4.72)
	(envelope-from <jjllambias@gmail.com>)
	id 1P6Oup-0008VA-Bq
	for bpfk@lojban.org; Thu, 14 Oct 2010 07:36:22 -0700
Received: by wwc33 with SMTP id 33so6600689wwc.10
        for <bpfk@lojban.org>; Thu, 14 Oct 2010 07:36:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.135.203 with SMTP id o11mr10350034wbt.162.1287066512758;
 Thu, 14 Oct 2010 07:28:32 -0700 (PDT)
Received: by 10.227.145.130 with HTTP; Thu, 14 Oct 2010 07:28:32 -0700 (PDT)
In-Reply-To: <20101014071951.GU24066@digitalkingdom.org>
References: <20101014071951.GU24066@digitalkingdom.org>
Date: Thu, 14 Oct 2010 11:28:32 -0300
Message-ID: <AANLkTi=ci5z2JjBMteEQDJPHz1ZTLvTja1RnDP=hF19S@mail.gmail.com>
Subject: Re: [bpfk] What I'm going to do.
From: =?ISO-8859-1?Q?Jorge_Llamb=EDas?= <jjllambias@gmail.com>
To: bpfk-list@googlegroups.com, bpfk@lojban.org
X-Original-Sender: jjllambias@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com:
 best guess record for domain of nobody@digitalkingdom.org designates
 173.13.139.234 as permitted sender) smtp.mail=nobody@digitalkingdom.org;
 dkim=pass (test mode) header.i=@gmail.com
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
List-ID: <bpfk-list.googlegroups.com>
List-Post: <http://groups.google.com/group/bpfk-list/post?hl=en_US>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list?hl=en_US>
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe?hl=en_US>,
 <mailto:bpfk-list+unsubscribe@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Length: 3163

On Thu, Oct 14, 2010 at 4:19 AM, Robin Lee Powell
<rlpowell@digitalkingdom.org> wrote:
>
> So, here's what's going to happen.

Excellent. Let's do it!


If I may, I would like propose we also do the following:

Every January 1st. the BPFK publishes a very concise "State of the
Language" report, that looks something like this:

-------------------------------
*************************
The State of the Lojban Language as of January 1st, 2011

The Official documentation of Lojban as recognized by the BPFK is:

- CLL-2011 (this is the current CLL with whatever paragraph changes
have been approved by January 1st 2011)  (with link)
- gismu-list-2011 (probably no changes this year)  (with link)
- cmavo-list-2011 (maybe two or three changes, maybe not)  (with link)
- whatever else we consider strictly official  (with link)

BPFK recommendations:

- The BPFK recommends that people use the definitions found in
"jbovlaste" for words not defined in the official documents (link to
jbovlaste).
- The BPFK recommends people pay attention to document xxxx (link) on
"denpa bu", as we expect that a change along those lines will be made
official at some point in the near future.
- The BPFK recommends people pay attention to document yyyy (link) on
(whatever), as we expect that a change along those lines will be made
official at some point in the future.
- The BPFK recommends people don't waste too much time on the official
specification of (whatever, MEX?), as we expect some relevant changes
may be made official in the near future.
- The BPFK recommends .... (whatever else we may want to recommend).


********************************
-----------------------------------------

That should be published in some prominent BPFK site, where each
year's new "State of the Language" report is added.

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).

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.

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.

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.

What do you think?

mu'o mi'e xorxes

-- 
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@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bpfk-list?hl=en.