From bpfk-list+bncCKnwz67vDhC5nN3lBBoEU0efMw@googlegroups.com Thu Oct 14 11:39:07 2010 Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P6Shi-0008Gm-NP; Thu, 14 Oct 2010 11:39:06 -0700 Received: by gyh3 with SMTP id 3sf4233665gyh.16 for ; Thu, 14 Oct 2010 11:38:56 -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: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=fjnrcFp8L+paM/Dk1yVIosUZSBhIMpmbCjzGpW09vrI=; b=GP/HATgahsZICW7jlaWqb/3eUFzyRqDn84ag0CHUzJHPmLnMF1vUUe9ldgSMV+r7AK zOXoScyGunpMUyey8W1WFBRE12L6oV57iI5W5sFWzEcrakcQ2Yn6ZY4vKELjUY/3iJWi piLgs9kMOUs6t/0Cj6VxMqAiA8gnDUMY0dKvk= 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=jZtAvmaqtUbCwZoy6T+zGtfMD4E/jTzFSYmdmDqDWOh9a4qOp7O6wmsCmoB56qC0pL lX6Ww8qyQamsMI8tGNn5jk2sfZtDOW1T1SAtxqh6amg4nBcStageMlDG8OiMlnzCrT5V 5W/1j0yEjKJGDwIQ4LKUQIRwVM//7ilzhdZ8w= Received: by 10.151.63.1 with SMTP id q1mr1005925ybk.60.1287081529338; Thu, 14 Oct 2010 11:38:49 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.231.112.41 with SMTP id u41ls1767734ibp.1.p; Thu, 14 Oct 2010 11:38:48 -0700 (PDT) Received: by 10.231.79.82 with SMTP id o18mr4077162ibk.15.1287081528730; Thu, 14 Oct 2010 11:38:48 -0700 (PDT) Received: by 10.231.79.82 with SMTP id o18mr4077159ibk.15.1287081528578; Thu, 14 Oct 2010 11:38:48 -0700 (PDT) Received: from mail-iw0-f181.google.com (mail-iw0-f181.google.com [209.85.214.181]) by gmr-mx.google.com with ESMTP id bm7si6951401ibb.2.2010.10.14.11.38.47; Thu, 14 Oct 2010 11:38:47 -0700 (PDT) Received-SPF: pass (google.com: domain of ted.reed@gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181; Received: by iwn39 with SMTP id 39so5978762iwn.26 for ; Thu, 14 Oct 2010 11:38:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.192.67 with SMTP id dp3mr8821027ibb.180.1287081527481; Thu, 14 Oct 2010 11:38:47 -0700 (PDT) Received: by 10.231.151.147 with HTTP; Thu, 14 Oct 2010 11:38:47 -0700 (PDT) In-Reply-To: <20101014071951.GU24066@digitalkingdom.org> References: <20101014071951.GU24066@digitalkingdom.org> Date: Thu, 14 Oct 2010 11:38:47 -0700 Message-ID: Subject: Re: [bpfk] What I'm going to do. From: Theodore Reed To: bpfk-list@googlegroups.com, bpfk@lojban.org X-Original-Sender: ted.reed@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ted.reed@gmail.com designates 209.85.214.181 as permitted sender) smtp.mail=ted.reed@gmail.com; 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: List-Post: , List-Help: , List-Archive: Sender: bpfk-list@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=0016363b8d5e3e16820492980558 --0016363b8d5e3e16820492980558 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Oct 14, 2010 at 00:19, Robin Lee Powell wrote: > > OK, so. The urge to just Go Fix Shit has been growing in me. I > think there's actually not all that much to do if I can get people > in a room for concentrated time to work on it. > > So, here's what's going to happen. > > 1. Lindar is working on examples, basic cleanup, and search of past > contention for everything. > > 2. I have diffs for the CLL; I will go through them, possibly with > others, and approve the result as the new CLL. > > 3. Possibly in parallel, somebody converts the current CLL in git > to docbook. > > 4. I, some other bay area Lojbanists, and a *very* few people via > voice chat, sit down for serious, concentrated sessions of Fixing > Shit. The results I want here look, in my head, a lot like what Bob > originally asked for, actually. To wit: > > - a series of numbered alternative proposals; there might be three > {ni} proposals, for example. Somewhere (I'm thinking in a setup > like shapado.com, but suggestions *very* welcome here) is a > repository of the proposals *and the justifications for each > option*. Each proposal is associated with CLL changes and word > definitons. > > We could do these as branches in git, maybe? > - a modified CLL that has colored paragraphs corresponding to > *every* proposal, so you can just go through and pick the ones > you like, basically > > - some proposals will contradict each other some won't > > - as long as a consistent set of proposals is selected, the > language will be as specified as we want it to be (including > those places where we explicitely say "this is a stylistic > choice") > > 5. We (where "we" means "a bunch of Lojbanists I respect") all vote > on the various proposals. (I have invited people to join the BPFK, > and the response has been underwhelming in general, so I'm going to > pick the people that I think have actually helped or whose voices > need to be heard and call them BPFK members.) This continues until > a consistent set is selected. The result becomes the CLL. The word > definitions become official. > > 6. I, some other bay area Lojbanists, and a *very* few people via > voice chat, sit down for serious, concentrated sessions of Making A > Dictionary, hopefully using the next generation of jbovlaste, which > someone has written in the meantime. We publish the resulting > dictionary. > > 7. Satisfied with the result, some of us vow to only speak in > Lojban when discussing Lojban, and in public Lojbanic fora. If > something's seriously broken, that should root it out. > > There are votes for the LLG and the BPFK in there at various points, > but I expect if xorxes and Arnt and I all agree on something, the > rest of you will toe the line. :) > Pretty much. -- 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. --0016363b8d5e3e16820492980558 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Oct 14, 2010 at 00:19, Robin Lee Powell = <rlpowe= ll@digitalkingdom.org> wrote:

OK, so. =A0The urge to just Go Fix Shit has been growing in me. =A0I
think there's actually not all that much to do if I can get people
in a room for concentrated time to work on it.

So, here's what's going to happen.

1. =A0Lindar is working on examples, basic cleanup, and search of past
contention for everything.

2. =A0I have diffs for the CLL; I will go through them, possibly with
others, and approve the result as the new CLL.

3. =A0Possibly in parallel, somebody converts the current CLL in git
to docbook.

4. =A0I, some other bay area Lojbanists, and a *very* few people via
voice chat, sit down for serious, concentrated sessions of Fixing
Shit. =A0The results I want here look, in my head, a lot like what Bob
originally asked for, actually. =A0To wit:

=A0- a series of numbered alternative proposals; there might be three
=A0 =A0{ni} proposals, for example. =A0Somewhere (I'm thinking in a se= tup
=A0 =A0like shapado.com, but suggestions *very* welcome here) is a
=A0 =A0repository of the proposals *and the justifications for each
=A0 =A0option*. =A0Each proposal is associated with CLL changes and word =A0 =A0definitons.



=A0- a modified CLL that has colored paragraphs corresponding to
=A0 =A0*every* proposal, so you can just go through and pick the ones
=A0 =A0you like, basically

=A0- some proposals will contradict each other some won't

=A0- as long as a consistent set of proposals is selected, the
=A0 =A0language will be as specified as we want it to be (including
=A0 =A0those places where we explicitely say "this is a stylistic
=A0 =A0choice")

5. =A0We (where "we" means "a bunch of Lojbanists I respect&= quot;) all vote
on the various proposals. =A0(I have invited people to join the BPFK,
and the response has been underwhelming in general, so I'm going to
pick the people that I think have actually helped or whose voices
need to be heard and call them BPFK members.) =A0This continues until
a consistent set is selected. =A0The result becomes the CLL. =A0The word definitions become official.

6. =A0I, some other bay area Lojbanists, and a *very* few people via
voice chat, sit down for serious, concentrated sessions of Making A
Dictionary, hopefully using the next generation of jbovlaste, which
someone has written in the meantime. =A0We publish the resulting
dictionary.

7. =A0Satisfied with the result, some of us vow to only speak in
Lojban when discussing Lojban, and in public Lojbanic fora. =A0If
something's seriously broken, that should root it out.

There are votes for the LLG and the BPFK in there at various points,
but I expect if xorxes and Arnt and I all agree on something, the
rest of you will toe the line. =A0:)

--
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.
--0016363b8d5e3e16820492980558--