From bpfk-list+bncCKnwz67vDhCRst3lBBoEAKIRbw@googlegroups.com Thu Oct 14 12:25:23 2010 Received: from mail-gy0-f189.google.com ([209.85.160.189]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1P6TQT-0003Gx-Kg; Thu, 14 Oct 2010 12:25:22 -0700 Received: by gyh3 with SMTP id 3sf4294265gyh.16 for ; Thu, 14 Oct 2010 12:25:11 -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=ZuirKpIIm0bFFpWiRzMJMcqJb20pq/0zOuSK3k8J4GM=; b=qtn2BVrks1+lswMkrRwZK6bdW8UPGRsAr4tx+ga9x/key2oS6gNsjaGv+oeBvJ67Md Ok3lWcz/vW6lwrldTr6Ai03m6vvyS2gVdquCZ1xeOPAvdfPkh11B8LcRIlASOne+zY5j 2uLAdnKue1HE06Qx/O1KZ36Yyr088lO4A3WVo= 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=JjWbugvcRWY+hab8FCl/2D6vsJ2fVQKaQkF7IE55pIE31lJZOExKBgjPcZBD+k/NaE 8muEnA605Rn197f0g2kcTOWYrOWMk7rJNrNIt+NiUwuPPLxRNEXWlRU3bGQHIlozQeZR E8ARx5gdJIEhpezZlpVtcqNPVAnwB8F+fIJes= Received: by 10.150.68.23 with SMTP id q23mr1016514yba.17.1287084306003; Thu, 14 Oct 2010 12:25:06 -0700 (PDT) X-BeenThere: bpfk-list@googlegroups.com Received: by 10.231.55.74 with SMTP id t10ls1809265ibg.3.p; Thu, 14 Oct 2010 12:25:04 -0700 (PDT) Received: by 10.42.244.197 with SMTP id lr5mr66169icb.99.1287084304736; Thu, 14 Oct 2010 12:25:04 -0700 (PDT) Received: by 10.42.244.197 with SMTP id lr5mr66168icb.99.1287084304699; Thu, 14 Oct 2010 12:25:04 -0700 (PDT) Received: from mail-iw0-f175.google.com (mail-iw0-f175.google.com [209.85.214.175]) by gmr-mx.google.com with ESMTP id b32si6732694ibq.1.2010.10.14.12.25.03; Thu, 14 Oct 2010 12:25:03 -0700 (PDT) Received-SPF: pass (google.com: domain of ted.reed@gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; Received: by iwn2 with SMTP id 2so4483125iwn.20 for ; Thu, 14 Oct 2010 12:25:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.154.75 with SMTP id n11mr8924258ibw.40.1287084303279; Thu, 14 Oct 2010 12:25:03 -0700 (PDT) Received: by 10.231.151.147 with HTTP; Thu, 14 Oct 2010 12:25:03 -0700 (PDT) In-Reply-To: <20101014184342.GY24066@digitalkingdom.org> References: <20101014071951.GU24066@digitalkingdom.org> <20101014184342.GY24066@digitalkingdom.org> Date: Thu, 14 Oct 2010 12:25:03 -0700 Message-ID: Subject: Re: [bpfk] What I'm going to do. From: Theodore Reed To: bpfk-list@googlegroups.com 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.175 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=005045015688b16605049298aa1b --005045015688b16605049298aa1b Content-Type: text/plain; charset=ISO-8859-1 On Thu, Oct 14, 2010 at 11:43, Robin Lee Powell wrote: > On Thu, Oct 14, 2010 at 11:38:47AM -0700, Theodore Reed wrote: > > On Thu, Oct 14, 2010 at 00:19, Robin Lee Powell < > rlpowell@digitalkingdom.org > > > 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? > > It's not just going to be CLL changes; it's going to be word list > stuff and commentary and so on. > > The ideal is having a jvs2 that can handle checkpoints/versioning, > and then the proposal just becomes "see git #### in CLL repo ; see > jvs2 checkpoint ### ; here's my justification for this proposal". > See http://www.lojban.org/tiki/tiki-index.php?page=Dictionary for > more commentary on the pipe dream that is jvs2. > > I suspect that checkpointing will be insufficient. You'll need the ability to actually branch or have mutually exclusive sets, rather than a point-to-point history. Maybe just tags or something. -- 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. --005045015688b16605049298aa1b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Oct 14, 2010 at 11:43, Robin Lee Powell = <rlpowe= ll@digitalkingdom.org> wrote:
On Thu, Oct 14, 2010 at 11:38:47AM -0700, Theodore Reed w= rote:
> On Thu, Oct 14, 2010 at 00:19, Robin Lee Powell <rlpowell@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 p= eople
> > 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 wha= t Bob
> > originally asked for, actually. =A0To wit:
> >
> > =A0- a series of numbered alternative proposals; there might be t= hree
> > =A0 =A0{ni} proposals, for example. =A0Somewhere (I'm thinkin= g in a setup
> > =A0 =A0like shap= ado.com, but suggestions *very* welcome here) is a
> > =A0 =A0repository of the proposals *and the justifications for ea= ch
> > =A0 =A0option*. =A0Each proposal is associated with CLL changes a= nd word
> > =A0 =A0definitons.
>
> We could do these as branches in git, maybe?

It's not just going to be CLL changes; it's going to be word = list
stuff and commentary and so on.

The ideal is having a jvs2 that can handle checkpoints/versioning,
and then the proposal just becomes "see git #### in CLL repo ; see
jvs2 checkpoint ### ; here's my justification for this proposal".<= br> See http://www.lojban.org/tiki/tiki-index.php?page=3DDiction= ary for
more commentary on the pipe dream that is jvs2.

I suspect that checkpointing will be insufficient. You'll = need the ability to actually branch or have mutually exclusive sets, rather= than a point-to-point history. Maybe just tags or something.=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.
--005045015688b16605049298aa1b--