Received: from mail-wi0-f183.google.com ([209.85.212.183]:63629) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XTHhS-0002lE-Et for lojban-list-archive@lojban.org; Sun, 14 Sep 2014 14:51:16 -0700 Received: by mail-wi0-f183.google.com with SMTP id q5sf78298wiv.20 for ; Sun, 14 Sep 2014 14:51:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=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; bh=rxv6sz7YEwWtb8uzO17qGDoi3Y/mlIiGMOEgFmG4YX8=; b=d3T8Nr1cNYBkevn8WXvElfAbYexFk2GZKn2ZjKAapQHshEEY/Oih9xJH7p5v0lUvu6 f/eJSlNoDKGmd8CmW1pjVB+V4EmOOqQv+5qfzxcSF+PjNUQlXU4Y2vSxOmml12adL6Me 4mwBkHtmiFbxVC6V2dkjvuq8XnC6VqebVoBk8UBmCk1VsIpK8payIEJZccdkcANTv+vO d0khcYxBOnEr1w7jY4TXlypV2+Zf7Qqrv5HreRBZL68M7bgVptoBkgTUCa3tyw1qDBZd uaxDPI1dhJtrxfmjt5NQ3M4y9NaMIOf64vpTdGIHht3OXAFGVCCm7keQU4yljogtsd0W REIg== X-Received: by 10.152.43.43 with SMTP id t11mr323611lal.4.1410731467545; Sun, 14 Sep 2014 14:51:07 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.26.73 with SMTP id j9ls328741lag.29.gmail; Sun, 14 Sep 2014 14:51:06 -0700 (PDT) X-Received: by 10.112.184.197 with SMTP id ew5mr6271359lbc.0.1410731466413; Sun, 14 Sep 2014 14:51:06 -0700 (PDT) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [2a00:1450:4010:c04::235]) by gmr-mx.google.com with ESMTPS id b6si1694674lbd.1.2014.09.14.14.51.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 14 Sep 2014 14:51:06 -0700 (PDT) Received-SPF: pass (google.com: domain of dlacewell@gmail.com designates 2a00:1450:4010:c04::235 as permitted sender) client-ip=2a00:1450:4010:c04::235; Received: by mail-lb0-x235.google.com with SMTP id z11so3428247lbi.40 for ; Sun, 14 Sep 2014 14:51:06 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.114.227 with SMTP id jj3mr22510290lbb.39.1410731466290; Sun, 14 Sep 2014 14:51:06 -0700 (PDT) Received: by 10.25.168.75 with HTTP; Sun, 14 Sep 2014 14:51:06 -0700 (PDT) In-Reply-To: <1410728470.91224.YahooMailNeo@web181106.mail.ne1.yahoo.com> References: <25B055499F67420FA34794323F9A95AB@gmail.com> <540B374A.9040409@lojban.org> <540B8D1B.8050807@gmail.com> <540F391F.5050002@lojban.org> <540F6802.3070709@gmail.com> <5410B7BF.9030005@lojban.org> <5411FCE9.3090907@lojban.org> <5414B97E.8050502@lojban.org> <1410728470.91224.YahooMailNeo@web181106.mail.ne1.yahoo.com> Date: Sun, 14 Sep 2014 14:51:06 -0700 Message-ID: Subject: Re: [lojban] the future of Lojban's leadership From: Dustin Lacewell To: lojban@googlegroups.com X-Original-Sender: DLacewell@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of dlacewell@gmail.com designates 2a00:1450:4010:c04::235 as permitted sender) smtp.mail=dlacewell@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=001a1135ed58ebfbb005030d83ad X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --001a1135ed58ebfbb005030d83ad Content-Type: text/plain; charset=UTF-8 John, No doubt you're able to point out this or that that needs to be done. I bet others can reference in their own words what they suppose is missing from some baseline or whatever. Great. How is the idea of moving all of that description into version control and giving selpahi the control of merging changes into that repository somehow in conflict with missing cmavo definitions? There are essentially two things this thread was originally about. 1) Moving the process for maintaining the language from a mailing-list/wiki mixed with crudely (and often internally inconsistent) processes and by-laws enforced by elected participants who may or may not even still be interested in Lojban by the next time a meeting requiring their attention and expertise is called... to an open-source version controlled 'consider-the-change-on-the-merits-of-the-change' system where anyone can submit any change against the repository which can then be considered for what it is by the community at large (or more importantly individuals who are actually motivated to participate in that process). Everybody can contribute and changes can be openly, and safely merged or not merged in a very controlled and systematic manner. 2) Reviewing the gimste for cohesiveness and regularity. We proposed to do this review using the process above. Where anyone can comment on any of the completely open and explicit individual proposed mutations to any particular word, make their own proposals and argue against those they disagree with. Neither of these things actually conflict with the needs in other areas, like finishing the cmavo definitions or any other arbitrarily prioritized agenda. All the arguments about relearning, CLL's, are arguments constructed to invoke fear of some fantasized destruction of the language. Neither of these proposed motions of actions reduce an existing description either. There is literally no substantiated argument against what we proposed (an open democratic process for explicit management of the language as data through version control and open-source policies for review and integration) other than 'waa, I don't actually like losing what sense of control I presume to have over the language'. It amazing going back over the thread just how irrelevant and orthogonal the supposed rebuking of this motion turned out to be. The current system for organizing and funneling the fluttering and whimsical productivity of Lojbanists for managing the language is bad. It assumes long-term commitment by a few select individuals to stay completely informed of a largish body of bylaws arbitrarily enforced between completely irregular periods of active governance and pure silence mixed with the demonstrable difficulty of actually being in-tune to how the language is changing in its utilization in various communities. It accumulates and forces processing of that work in larger batches instead of continuous review and integration consideration. Nothing about the proposed system violates anything about the needs to keep the language completely described and actually does a better job than the system that's being (quite terribly) defended in this thread. On Sun, Sep 14, 2014 at 2:01 PM, 'John E Clifford' via lojban < lojban@googlegroups.com> wrote: > Just because nobody want to do it, doesn't mean it doesn't need to be > done. Similarly, just because somebody(/ies) want to change things based > on usage doesn't mean that they (or somebody) doesn't need to write up > explicit and detailed reports of what these usages are. Lojban is the most > thoroughly described human language because it has to keep a check on its > monoparsing. All usage has be be integrated into the grammar that makes > that possible. Right now the problem is (purportedly) that we don't know > enough about some old things (though the monoparsing claim continues) nor > anything at all about some new things. As for the claim about the old > things, I have been trying to find out what is lacking but cannot find a > clear statement in the morass of items under BPFK., cmavo, and related > topics starting from the homepage. I am sure all the material there > somewhere but, after a dozen years any organized list has been lost or > dissipated. It is not even clear whether the problem is that there are > cmavo that have no definition (a likelihood, since at one time there seemed > to be a new cmavo every week, most of which then disappeared without a > trace -- a good fate for cmavo generally, by the way), in which case it is > not clear in what sense they exist at all, or, more likely, there are > camavo whose definitions are somehow (how?) incomplete (again raising the > question in what sense they actually exist. Toki pona listed a word for > several years and people speculated what it meant until finally it was > defined and turned out to be nothing needed or wanted in the language). > So, maybe if the list of needed fixes from the old language were collected > again (or resurrected -- it may actually be there somewhere) and the irc > group (and other innovators, of course) came up with a list of their usages > (which may, of course, turn out not to be new at all, given the state of > lack of information about what is real), we can agree to finish off a > description of the language (possibly contradictory for the nonce) and sort > back a satisfactory description ("satisfactory" being the operant weasel > here). > > > On Sunday, September 14, 2014 2:47 PM, Dustin Lacewell < > dlacewell@gmail.com> wrote: > > > "The selpa'i group..." > > For what its worth, I don't really 'represent' 'selpahi's group' anymore. > I don't even know why this thread has continued so long. I just couldn't > stand having our community referred to as language destroying tinkerer's > any longer. > > No one even wants to do the original thing anymore since no one who was > offering to participate in what was originally proposed could possibly > desire to be seen as destroying the language, but that's what they were > made out to be. We never intended for a coup, because a coup implies there > is an existing structure in place. We were simply trying fill what is > actually a huge glaring lack of one. But I guess the decayed ephemeral > existence of one is enough for this language. > > > -- > You received this message because you are subscribed to the Google Groups > "lojban" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to lojban+unsubscribe@googlegroups.com. > To post to this group, send email to lojban@googlegroups.com. > Visit this group at http://groups.google.com/group/lojban. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "lojban" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/lojban/_juGorRhWtI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > lojban+unsubscribe@googlegroups.com. > To post to this group, send email to lojban@googlegroups.com. > Visit this group at http://groups.google.com/group/lojban. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --001a1135ed58ebfbb005030d83ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
John,

No doubt you're able to point= out this or that that needs to be done. I bet others can reference in thei= r own words what they suppose is missing from some baseline or whatever. Gr= eat. How is the idea of moving all of that description into version control= and giving selpahi the control of merging changes into that repository som= ehow in conflict with missing cmavo definitions?

T= here are essentially two things this thread was originally about.=C2=A0

=C2=A0 1) Moving the process for maintaining the lang= uage from a mailing-list/wiki mixed with crudely (and often internally inco= nsistent) processes and by-laws enforced by elected participants who may or= may not even still be interested in Lojban by the next time a meeting requ= iring their attention and expertise is called... =C2=A0to an open-source ve= rsion controlled 'consider-the-change-on-the-merits-of-the-change' = system where anyone can submit any change against the repository which can = then be considered for what it is by the community at large (or more import= antly individuals who are actually motivated to participate in that process= ). Everybody can contribute and changes can be openly, and safely merged or= not merged in a very controlled and systematic manner.

=C2=A02) Reviewing the gimste for cohesiveness and regularity. We pro= posed to do this review using the process above. Where anyone can comment o= n any of the completely open and explicit individual proposed mutations to = any particular word, make their own proposals and argue against those they = disagree with.

Neither of these things actually co= nflict with the needs in other areas, like finishing the cmavo definitions = or any other arbitrarily prioritized agenda. All the arguments about relear= ning, CLL's, are arguments constructed to invoke fear of some fantasize= d destruction of the language. Neither of these proposed motions of actions= reduce an existing description either. There is literally no substantiated= argument against what we proposed (an open democratic process for explicit= management of the language as data through version control and open-source= policies for review and integration) other than 'waa, I don't actu= ally like losing what sense of control I presume to have over the language&= #39;.

It amazing going back over the thread just how irrelevant and = orthogonal the supposed rebuking of this motion turned out to be.=C2=A0
=
The current system for organizing and funneling the fluttering and whim= sical productivity of Lojbanists for managing the language is bad. It assum= es long-term commitment by a few select individuals to stay completely info= rmed of a largish body of bylaws arbitrarily enforced between completely ir= regular periods of active governance and pure silence mixed with the demons= trable difficulty of actually being in-tune to how the language is changing= in its utilization in various communities. It accumulates and forces proce= ssing of that work in larger batches instead of continuous review and integ= ration consideration.

Nothing about the proposed s= ystem violates anything about the needs to keep the language completely des= cribed and actually does a better job than the system that's being (qui= te terribly) defended in this thread.

On Sun, Sep 14, 2014 at 2:01 PM, 'John = E Clifford' via lojban <lojban@googlegroups.com> w= rote:
Just because nobody want= to do it, doesn't mean it doesn't need to be done. =C2=A0Similarly= , just because somebody(/ies) want to change things based on usage doesn= 9;t mean that they (or somebody) doesn't need to write up explicit and = detailed reports of what these usages are. =C2=A0Lojban is the most thoroug= hly described human language because it has to keep a check on its monopars= ing. =C2=A0All usage has be be integrated into the grammar that makes that = possible. =C2=A0Right now the problem is (purportedly) that we don't kn= ow enough about some old things (though the monoparsing claim continues) no= r anything at all about some new things. =C2=A0As for the claim about the o= ld things, I have been trying to find out what is lacking but cannot find a= clear statement in the morass of items under BPFK., cmavo, and related topics starting from the homepage. =C2=A0I= am sure all the material there somewhere but, after a dozen years any orga= nized list has been lost or dissipated. =C2=A0It is not even clear whether = the problem is that there are cmavo that have no definition (a likelihood, = since at one time there seemed to be a new cmavo every week, most of which = then disappeared without a trace -- a good fate for cmavo generally, by the= way), in which case it is not clear in what sense they exist at all, or, m= ore likely, there are camavo whose definitions are somehow (how?) =C2=A0inc= omplete (again raising the question in what sense they actually exist. =C2= =A0Toki pona listed a word for several years and people speculated what it = meant until finally it was defined and turned out to be nothing needed or w= anted in the language). =C2=A0So, maybe if the list of needed fixes from th= e old language were collected again (or resurrected -- it may actually be there somewhere) and the irc group (and other innovators, of c= ourse) came up with a list of their usages (which may, of course, turn out = not to be new at all, given the state of lack of information about what is = real), we can agree to finish off a description of the language (possibly c= ontradictory for the nonce) and sort back a satisfactory description ("= ;satisfactory" being the operant weasel here).

<= br>
On Sund= ay, September 14, 2014 2:47 PM, Dustin Lacewell <dlacewell@gmail.com> wrote:


"The selpa'i group..."

For what its worth, I don't r= eally 'represent' 'selpahi's group' anymore. I don'= t even know why this thread has continued so long. I just couldn't stan= d having our community referred to as language destroying tinkerer's an= y longer.

No one even wants to do the ori= ginal thing anymore since no one who was offering to participate in what wa= s originally proposed could possibly desire to be seen as destroying the la= nguage, but that's what they were made out to be. We never intended for= a coup, because a coup implies there is an existing structure in place. We= were simply trying fill what is actually a huge glaring lack of one. But I= guess the decayed ephemeral existence of one is enough for this language.<= /div>


--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to
lojban@googlegroups.= com.
Visit this group at http://groups.google.com/group= /lojban.
For more options, visit https://groups.google.com/d/o= ptout.


--
You received this message because you are subscribed to a topic in the Goog= le Groups "lojban" group.
To unsubscribe from this topic, visit https://groups.go= ogle.com/d/topic/lojban/_juGorRhWtI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to lojban+un= subscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--001a1135ed58ebfbb005030d83ad--