Received: from mail-wi0-f187.google.com ([209.85.212.187]:56042) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from ) id 1XTIas-0002wu-5R for lojban-list-archive@lojban.org; Sun, 14 Sep 2014 15:48:33 -0700 Received: by mail-wi0-f187.google.com with SMTP id d1sf236752wiv.4 for ; Sun, 14 Sep 2014 15:48:23 -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=Wc8ClNm5qA0OlTCZ04ng6btCgh+KQ6YqxIlJoifI/V8=; b=Ryf/3I72GmbeHGGfPTTTZ6bjLEfFji1L34E9QUqm81J+aQL8IKG5eH6tTpvnIbhtTS fSjhaTtQ8GdEEYCFazwtu/aishd8HsE/MsUdtVJm8ZcCQ+sqbFY17w2lxgThARpoi/E6 wthUvGemYS7fwwMn1pvgJr3cTzGdKpyETIYBMV566Yg7BpyvVT6HhEshGE5W8LZstRIB f1rQswq0uRrg22BYHh9kKHBc0pR5sK44deeQxl88K8P4pkAaLgcbMLYOuoIbpED/otu7 H72VMWyZRKJ5vn46vK6Qr3775ThzPOPOaUdbOteuU7F+WQSilgr94RzWL8N9qq9n5KTG uhSg== X-Received: by 10.152.7.226 with SMTP id m2mr327927laa.0.1410734903223; Sun, 14 Sep 2014 15:48:23 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.120.100 with SMTP id lb4ls312737lab.82.gmail; Sun, 14 Sep 2014 15:48:21 -0700 (PDT) X-Received: by 10.112.132.37 with SMTP id or5mr1718477lbb.2.1410734901778; Sun, 14 Sep 2014 15:48:21 -0700 (PDT) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [2a00:1450:4010:c04::22a]) by gmr-mx.google.com with ESMTPS id b6si1707353lbd.1.2014.09.14.15.48.21 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 14 Sep 2014 15:48:21 -0700 (PDT) Received-SPF: pass (google.com: domain of dlacewell@gmail.com designates 2a00:1450:4010:c04::22a as permitted sender) client-ip=2a00:1450:4010:c04::22a; Received: by mail-lb0-f170.google.com with SMTP id c11so3537881lbj.1 for ; Sun, 14 Sep 2014 15:48:21 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.135.137 with SMTP id ps9mr22931783lbb.24.1410734901658; Sun, 14 Sep 2014 15:48:21 -0700 (PDT) Received: by 10.25.168.75 with HTTP; Sun, 14 Sep 2014 15:48:21 -0700 (PDT) In-Reply-To: <1410733473.23327.YahooMailNeo@web181101.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> <1410733473.23327.YahooMailNeo@web181101.mail.ne1.yahoo.com> Date: Sun, 14 Sep 2014 15:48:21 -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::22a 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=089e011604e8af883605030e50ad X-Spam-Score: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --089e011604e8af883605030e50ad Content-Type: text/plain; charset=UTF-8 John Well that doesn't seem to be disagreeable at all. I mean a large implied fallacy in the thread has seemed to be that selpahi doesn't also want the best for lojban and for it to reflect its foundations in first order predicate logic, be monoparsable, be completely described, be useful as a spoken language and so on. I mean, I can say he really does but it is pretty clear from talking to him for 5 minutes if one were to ask him. That goes the same with all the jbocre in the IRC community like durka and tsani and xalbo and others. I think you know that's true, as you've been around during lots of their debates. They're hardly casuals, right John? I think that's a quality of the community that people outside it are missing. That its not like the thoughts surrounding how we go about this or the changes are inspiring the need for an actually workable system of governance are not well thought out and dragged through several on-going reoccurring internal debates. I'm not saying 'we have the best community'. I'm saying look, we have a non-trivial community with, sure call it a dialect, as the result of lots of usage and consideration and there is no non-ethereal mechanism for actually moving such evolutions in usage back to the wider community. That isn't 'we have something's we'd like to force everyone else to do'. We objectively went out of our way to prompt a community that is otherwise *not* providing a realistic (and in my opinon not patently absurd) mechanism and process for doing that. One that you at least seem to view as passable if not potentially advantageous. Seriously, everyone else, when you remove the pretext fetish of making us out to want to destroy the language and insulting holders of CLLs and somehow undoing the very fabric of the community, what is so bad about what was -actually- proposed? I guess its a rhetorical question and I'm not actually expressing hope that we can some how actually move forward. Hope was lost long ago. If certain people can stop insulting and trivializing my friends with a smile of implied virtue, then I wont have to keep defending them (though I'm sure they wish I'd stop anyway). On Sun, Sep 14, 2014 at 3:24 PM, 'John E Clifford' via lojban < lojban@googlegroups.com> wrote: > > To the initial question the answer is "Not at all", though with the > proviso that whoever takes on the task shares the goal of producing a > monoparsing grammar. I admit I am not convinced that this is among David's > agenda, but then I am not convinced it really plays that much of a role in > other people's agenda either. The process you propose is a normalization > of the de facto process that Lojban has used for a couple decades just now > being recognized and made effective. No objection to that, again with the > proviso that the discussion keeps monoparsing ever in view and that changes > that disrupt this feature are either automatically rejected or are farmed > out for a thorough-going fix to bring them into the fold. If it does away > with bureaucratic inertia, better yet. (Having been around this particular > project for nearly forty years, I can reasonably predict ways that this > will crash and burn, but that doesn't seem a reason to not do it, since the > crashing and burning of another sort is already rather far advanced and > this may slow that down at least for my lifetime.) > > > > On Sunday, September 14, 2014 4:51 PM, Dustin Lacewell < > dlacewell@gmail.com> wrote: > > > 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. > > > -- > 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. --089e011604e8af883605030e50ad Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
John

Well that doesn't seem to be d= isagreeable at all. I mean a large implied fallacy in the thread has seemed= to be that selpahi doesn't also want the best for lojban and for it to= reflect its foundations in first order predicate logic, be monoparsable, b= e completely described, be useful as a spoken language and so on. I mean, I= can say he really does but it is pretty clear from talking to him for 5 mi= nutes if one were to ask him. That goes the same with all the jbocre in the= IRC community like durka and tsani and xalbo and others. I think you know = that's true, as you've been around during lots of their debates. Th= ey're hardly casuals, right John?

I think that= 's a quality of the community that people outside it are missing. That = its not like the thoughts surrounding how we go about this or the changes a= re inspiring the need for an actually workable system of governance are not= well thought out and dragged through several on-going reoccurring internal= debates. I'm not saying 'we have the best community'. I'm = saying look, we have a non-trivial community with, sure call it a dialect, = as the result of lots of usage and consideration and there is no non-ethere= al mechanism for actually moving such evolutions in usage back to the wider= community. That isn't 'we have something's we'd like to fo= rce everyone else to do'. We objectively went out of our way to prompt = a community that is otherwise *not* providing a realistic (and in my opinon= not patently absurd) mechanism and process for doing that. One that you at= least seem to view as passable if not potentially advantageous. Seriously,= everyone else, when you remove the pretext fetish of making us out to want= to destroy the language and insulting holders of CLLs and somehow undoing = the very fabric of the community, what is so bad about what was -actually- = proposed?

I guess its a rhetorical question and I'm not actually= expressing hope that we can some how actually move forward. Hope was lost = long ago. If certain people can stop insulting and trivializing my friends = with a smile =C2=A0of implied virtue, then I wont have to keep defending th= em (though I'm sure they wish I'd stop anyway).



On Sun, Sep 14, 2014 at 3:24 PM, 'John E Clifford' via lojban = <lojban@googlegroups.com> wrote:

= To the initial question =C2=A0the answer is "Not at all", though = with the proviso that whoever takes on the task shares the goal of producin= g a monoparsing grammar. =C2=A0I admit I am not convinced that this is amon= g David's agenda, but then I am not convinced it really plays that much= of a role in other people's agenda either. =C2=A0The process you propo= se is a normalization of the de facto process that Lojban has used for a co= uple decades just now being recognized and made effective. =C2=A0No objecti= on to that, again with the proviso that the discussion keeps monoparsing ev= er in view and that changes that disrupt this feature are either automatically rejected o= r are farmed out for a thorough-going fix to bring them into the fold. =C2= =A0If it does away with bureaucratic inertia, better yet. =C2=A0(Having bee= n around this particular project for nearly forty years, I can reasonably p= redict ways that this will crash and burn, but that doesn't seem a reas= on to not do it, since the crashing and burning of another sort is already = rather far advanced and this may slow that down at least for my lifetime.)<= /div>
<= br>


On Sunday,= September 14, 2014 4:51 PM, Dustin Lacewell <dlacewell@gmail.com> wrote:


John,

No doubt you're able to point out this or that that ne= eds to be done. I bet others can reference in their own words what they sup= pose is missing from some baseline or whatever. Great. How is the idea of m= oving all of that description into version control and giving selpahi the c= ontrol of merging changes into that repository somehow in conflict with mis= sing cmavo definitions?

There are e= ssentially two things this thread was originally about.=C2=A0
=C2=A0 1) Moving the process for maintaining the language from a mailing-list/wiki mixed with crudely (and often intern= ally inconsistent) processes and by-laws enforced by elected participants w= ho may or may not even still be interested in Lojban by the next time a mee= ting requiring their attention and expertise is called... =C2=A0to an open-= source version controlled 'consider-the-change-on-the-merits-of-the-cha= nge' system where anyone can submit any change against the repository w= hich can then be considered for what it is by the community at large (or mo= re importantly individuals who are actually motivated to participate in tha= t 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 cohesivenes= s and regularity. We proposed to do this review using the process above. Wh= ere anyone can comment on any of the completely open and explicit individua= l proposed mutations to any particular word, make their own proposals and ar= gue 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 constr= ucted to invoke fear of some fantasized destruction of the language. Neithe= r of these proposed motions of actions reduce an existing description eithe= r. There is literally no substantiated argument against what we proposed (a= n open democratic process for explicit management of the language as data t= hrough version control and open-source policies for review and integration)= other than 'waa, I don't actually like losing what sense of contro= l I presume to have over the language'.

It amazing going back over the thread just how irrelevant and orthogo= nal the supposed rebuking of this motion turned out to be.=C2=A0

The current system for organizing and funneling the flu= ttering 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 betwe= en completely irregular periods of active governance and pure silence mixed= with the demonstrable difficulty of actually being in-tune to how the lang= uage 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 k= eep the language completely described and actually does a better job than t= he 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 n= obody 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 us= age doesn'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 thoroughly described human language because it has= to keep a check on its monoparsing. =C2=A0All usage has be be integrated i= nto the grammar that makes that possible. =C2=A0Right now the problem is (p= urportedly) that we don't know enough about some old things (though the= monoparsing claim continues) nor anything at all about some new things. = =C2=A0As 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. =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).


On Sunday, September 14, 2014 2:47 PM, Dustin Lacewell <dlacewell@gmail.com> wrote:
<= /div>

"The selpa'i group..."

For what its worth, I d= on't really 'represent' 'selpahi's group' anymore. = I don't even know why this thread has continued so long. I just couldn&= #39;t stand having our community referred to as language destroying tinkere= r'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 destroy= ing the language, but that's what they were made out to be. We never in= tended 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.google.com/d/topic/lojban/_juGorRhWtI/unsubsc= ribe.
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/o= ptout.

--
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.
--089e011604e8af883605030e50ad--