Received: from mail-gh0-f183.google.com ([209.85.160.183]:46711) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1Tp30i-0004oN-Sb; Sat, 29 Dec 2012 12:28:10 -0800 Received: by mail-gh0-f183.google.com with SMTP id z12sf5334701ghb.0 for ; Sat, 29 Dec 2012 12:27:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=x-received:x-beenthere:x-received:x-received: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:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=wImveDSavys4QaTlaeND28c88N4d9oJIraOzMQT2lL8=; b=zCuvp7yhEVMMfIE6EEwlqkQsWdj1KzxmgBJzDLoVQ+VbAuXWf496OFwbC5ei09fWUX 18zdZ3nevv8H4q0/Kd/cp1NIZzWA2FyXFnByCG6Byv79cIIIZjCau6KzwldGoGJOZrXl nh0meFOPyCrW5noqM8jjMD9AGvax1ULn7/BFbUBEcdejqYNY0GMvxBmD8P2lV5DwXpmV gI+Wxku9eWLN1wczcAWZhcT0fEY4rK+zd5IE1D8z2PzQkfD0pEm66i/Vx+OxNu1qi7dr N2+Hz+xqCIBQaTkN6IzYPq8ouLgE/QnN9zj8DoUeFrZzEki5y9K+g0ji9nVbfS2QUKlP 08jg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:x-beenthere:x-received:x-received: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:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type; bh=wImveDSavys4QaTlaeND28c88N4d9oJIraOzMQT2lL8=; b=Nhk3iYbkBiy7HxkO224xuXmvZqy3BkBIHN57fr6cU3/ppw/de/Kl81SIyBu0cWFwb6 y1I752fAUFrM1jL/MNiRlGmAnTjH/xj3om79kxXzlaiCwaTlQAZS7QCpy4Dw3qO4C8TL pYgVx2EFOik0uSh1ZezgR+MUG5hJqlfn//nuzGcLnDL3eDuoifN0/vKkb93kAfrhwySh wO0iTwN33UuxI3R188VILpT3eh+qc1bJ7jasENbXN0+fBF5FqymvrH3c3A8eFSE81ET+ LeIBQ2EW+O04QV3I96y3bfy3z/ajsLf8zz5XftuEK76QEHjHlDAn9g+HNLtDC2J1GFYv 8H7A== X-Received: by 10.50.108.137 with SMTP id hk9mr9439697igb.15.1356812874256; Sat, 29 Dec 2012 12:27:54 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.50.37.141 with SMTP id y13ls11360941igj.4.canary; Sat, 29 Dec 2012 12:27:53 -0800 (PST) X-Received: by 10.42.212.209 with SMTP id gt17mr27519399icb.31.1356812873703; Sat, 29 Dec 2012 12:27:53 -0800 (PST) X-Received: by 10.42.212.209 with SMTP id gt17mr27519398icb.31.1356812873677; Sat, 29 Dec 2012 12:27:53 -0800 (PST) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by gmr-mx.google.com with ESMTPS id hw1si3231160igc.3.2012.12.29.12.27.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 29 Dec 2012 12:27:53 -0800 (PST) Received-SPF: pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.172 as permitted sender) client-ip=209.85.214.172; Received: by mail-ob0-f172.google.com with SMTP id za17so10686090obc.31 for ; Sat, 29 Dec 2012 12:27:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.172.229 with SMTP id bf5mr18387118oec.81.1356812873329; Sat, 29 Dec 2012 12:27:53 -0800 (PST) Received: by 10.60.178.237 with HTTP; Sat, 29 Dec 2012 12:27:53 -0800 (PST) In-Reply-To: <50DEF2D2.6080309@lojban.org> References: <20121227222129.GN7855@samsa.fritz.box> <20121227222753.GG18038@stodi.digitalkingdom.org> <20121227231105.GO7855@samsa.fritz.box> <20121227232206.GI18038@stodi.digitalkingdom.org> <20121227232732.GP7855@samsa.fritz.box> <20121227233537.GJ18038@stodi.digitalkingdom.org> <20121227235946.GQ7855@samsa.fritz.box> <20121228000348.GL18038@stodi.digitalkingdom.org> <20121228185329.GO18038@stodi.digitalkingdom.org> <20121228215107.GR7855@samsa.fritz.box> <50DEF2D2.6080309@lojban.org> Date: Sat, 29 Dec 2012 13:27:53 -0700 Message-ID: Subject: Re: [lojban] CLL 1.1/ CLL 2.0. What is your opinion in the current situation? From: Jonathan Jones To: lojban@googlegroups.com X-Original-Sender: eyeonus@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of eyeonus@gmail.com designates 209.85.214.172 as permitted sender) smtp.mail=eyeonus@gmail.com; dkim=pass header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=bcaec54ee86c576b1e04d2039d71 X-Spam-Score: -0.1 (/) X-Spam_score: -0.1 X-Spam_score_int: 0 X-Spam_bar: / --bcaec54ee86c576b1e04d2039d71 Content-Type: text/plain; charset=ISO-8859-1 On Sat, Dec 29, 2012 at 6:40 AM, Bob LeChevalier, President and Founder - LLG wrote: > v4hn wrote: > >> What's up with http://www.lojban.org/tiki/**BPFK+Procedureand the checkpoints? >> I know it says "obsolete" there, but still it is well thought out >> and looks like a good infrastracture to get going again. >> > > It WAS a good infrastructure, when we had a dozen or more people actively > working on it. But that didn't last. Everyone was doing their own thing, > because that is how this community has always worked. As a result, any > topic that was well-settled got little attention (and continued > undocumented), and things that were contentious turned into endless > discussion that distracted people from doing productive stuff that would > actually move the process along. The bottom line is that no one had enough > time (consistently over the long haul) to make the thing work. Nick > Nicolas, the original jatna, became burned out and frustrated with the lack > of progress, because even his skills weren't enough to herd cats. Robin > took over, in the absence of other volunteers, and had only limited success. > > > I know the BPFK is not dead, I recognize a lot of names on the member >> list, >> and I haven't been around for too long. >> > > It isn't dead. It just has nothing to do as a GROUP, because there > haven't enough individuals actually doing the individual things that need > to get done, which are mostly boring and time-consuming, (or requiring > specialized knowledge). > > > > But it looks like that to me > >> because there weren't /any/ "official" announcements concerning decisions >> > > That is because there have been no such decisions, and there won't be any > until after CLL 1.1 is done. We have to document the status quo before we > consider changes, or people won't know what is being proposed to change. > > Even then, changes will be very limited. Only what is actually broken > should be fixed prescriptively. > > The language design era is supposedly done. Future change should evolve > out of usage, with changes merely serving as documentation of what actual > Lojbanists are doing with the language. > > > or even new official proposals >> > > There have never been ANY official proposals since byfy started. > > > or any other progress within the last year. >> > > The progress, such that it is, is whatever Robin says that it is. He was > granted essentially dictatorial powers until (at least) such time as CLL is > updated. > > > I only heard of a couple of draft-proposals by people who explicitly state >> that they are _not_ members of the BPFK >> > > No one is in a position to evaluate a draft proposal. And a proposal to > be considered will have to include the proposed changes to CLL among other > things. I doubt that anyone in recent years has ever written up a proposed > change with anywhere near the detail that will be expected. > > > and some complains about >> infrastructure/tools which need fixing (jbovlaste, autoposting of texts, >> TeX-problems, ...). This is no development, it's maintenance as far as I >> can see. >> > > It is enabling Robin to get his job done, with as little possible demands > on his limited time. > > The main job right now is editorial, and we haven't come up with a way to > farm out editorial tasks. (Perhaps if the original byfy structure had been > organized around CLL chapters rather than selma'o, we might have learned > how, but the original focus was on making decisions, not on documenting > things to any consistent standard, and the documentation never got done.) > As such, we are stuck with having one editor attempting to get things done > in his limited spare time. > Perhaps crowd-sourcing? I had some success with that when I wanted to get human audio for all the gismu. I had started out with the intention of doing that work myself, but after about 180 gismu, I got sick of it, so I parsed it into chunks and sent an announcement on the group saying, basically, "I don't want to do this anymore! You guys do this now!". As of today, all but ~100 gismu have been done, and 50 of them are my fault. Possibly something similar could be done in this scenario? It takes a bit of setting up the "chunks", but I can tell you, the chunk setup is much, much, MUCH less work than doing the work on your own. > lojbab > > -- > Bob LeChevalier lojbab@lojban.org www.lojban.org > President and Founder, The Logical Language Group, Inc. -- mu'o mi'e .aionys. .i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk. mi patfu do zo'o (Come to the Dot Side! Luke, I am your father. :D ) -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --bcaec54ee86c576b1e04d2039d71 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sat, Dec 29, 2012 at 6:40 AM, Bob LeChevalier= , President and Founder - LLG <lojbab@lojban.org> wrote:
=
v4hn wrote:
What's up with http://www.lojban.org/tiki/BPFK+Procedure and th= e checkpoints?
I know it says "obsolete" there, but still it is well thought out=
and looks like a good infrastracture to get going again.

It WAS a good infrastructure, when we had a dozen or more people actively w= orking on it. =A0But that didn't last. =A0Everyone was doing their own = thing, because that is how this community has always worked. =A0As a result= , any topic that was well-settled got little attention (and continued undoc= umented), and things that were contentious turned into endless discussion t= hat distracted people from doing productive stuff that would actually move = the process along. =A0The bottom line is that no one had enough time (consi= stently over the long haul) to make the thing work. =A0Nick Nicolas, the or= iginal jatna, became burned out and frustrated with the lack of progress, b= ecause even his skills weren't enough to herd cats. =A0Robin took over,= in the absence of other volunteers, and had only limited success.


I know the BPFK is not dead, I recognize a lot of names on the member list,=
and I haven't been around for too long.

It isn't dead. =A0It just has nothing to do as a GROUP, because there h= aven't enough individuals actually doing the individual things that nee= d to get done, which are mostly boring and time-consuming, (or requiring sp= ecialized knowledge).


> But it looks like that to me
because there weren't /any/ "official" announcements concerni= ng decisions

That is because there have been no such decisions, and there won't be a= ny until after CLL 1.1 is done. =A0We have to document the status quo befor= e we consider changes, or people won't know what is being proposed to c= hange.

Even then, changes will be very limited. Only what is actually broken shoul= d be fixed prescriptively.

The language design era is supposedly done. =A0Future change should evolve = out of usage, with changes merely serving as documentation of what actual L= ojbanists are doing with the language.


or even new official proposals

There have never been ANY official proposals since byfy started.


or any other progress within the last year.

The progress, such that it is, is whatever Robin says that it is. =A0He was= granted essentially dictatorial powers until (at least) such time as CLL i= s updated.


I only heard of a couple of draft-proposals by people who explicitly state<= br> that they are _not_ members of the BPFK

No one is in a position to evaluate a draft proposal. =A0And a proposal to = be considered will have to include the proposed changes to CLL among other = things. =A0I doubt that anyone in recent years has ever written up a propos= ed change with anywhere near the detail that will be expected.


and some complains about
infrastructure/tools which need fixing (jbovlaste, autoposting of texts, TeX-problems, ...). This is no development, it's maintenance as far as = I can see.

It is enabling Robin to get his job done, with as little possible demands o= n his limited time.

The main job right now is editorial, and we haven't come up with a way = to farm out editorial tasks. =A0(Perhaps if the original byfy structure had= been organized around CLL chapters rather than selma'o, we might have = learned how, but the original focus was on making decisions, not on documen= ting things to any consistent standard, and the documentation never got don= e.) =A0As such, we are stuck with having one editor attempting to get thing= s done in his limited spare time.

Perhaps crowd-sourcing? I had some success with that = when I wanted to get human audio for all the gismu. I had started out with = the intention of doing that work myself, but after about 180 gismu, I got s= ick of it, so I parsed it into chunks and sent an announcement on the group= saying, basically, "I don't want to do this anymore! You guys do = this now!". As of today, all but ~100 gismu have been done, and 50 of = them are my fault.

Possibly something similar could be done in this scenario? It takes a b= it of setting up the "chunks", but I can tell you, the chunk setu= p is much, much, MUCH less work than doing the work on your own.
=A0
lojbab

--
Bob LeChevalier =A0 =A0lojbab@lojban.org =A0 =A0www.lojban.org
President and Founder, The Logical Language Group, Inc.



--
mu'o mi'e .aionys.
.i.e'ucai ko cmima lo pilno be denpa bu .i doi.luk. mi patfu do zo= 'o
(Come to the Dot Side! Luke, I am your father. :D )

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--bcaec54ee86c576b1e04d2039d71--